XSF Discussion - 2017-09-18

Zash: no

at least not in countries who sort trash

oh, we do a lot of software listing here: https://xmpp.org/about/technology-overview.html. Wasn't aware of that.

Not sure if this works well with the software listing we do under the 'software' menu

also not sure if we should change it, and if so, how.

we can do more magic like I did for the team pages, but I feel a bit bad about what I did there already

Guus, can you take a look from where https://xmpp.org/extensions/xmpp.css comes and make sure it comes from within the container? (or delegate to someone who knows how to in iteam)

not sure if we should do that here, but why did you feel bad about the tema stuff?

Guus, because I did a | replace(...) on markup

jonasw: any reason to think that the xmpp.css does not compe from the extensions container?

can't immediately find rewrite rules that would cause it to serve from anywhere else

it has been updated in the docker

cf. https://github.com/xsf/xeps/pull/511

dockerhub seems to have been triggered

perhaps it didn't deploy, let me check

hmm, it's set up to deploy automatically

are you sure we don’t need explicit rewrite rules to get stuff from *inside* the container?

I think I had to interact with iteam to get xeplist.xml to be visible outside the container

I'm quite new to this, so I'm not sure about anything :)

I just forced another update, which didn't seem to affect the output

so the issue does not appear to be caused by the github->dockerhub->server update mechanism.

the container config is here, by the way: https://github.com/xsf/xep-docker-base

most likely, there's a rewrite rule that I didn't find on my first check

(which was a simple grep)

let me check further

oh, /extensions/ isn't mapped to that repo for every resource that's under that address

location ~ ^/extensions/((xep-[0-9]*|xeps|rss|atom|prettify)\.(html|pdf|xml|js|css)|xep\.(ent|xsl|dtd)|xeplist.xml|inbox.+)$

"just" for that

right :)

adding a |xmpp\.css sounds reasonable

(after inbox.+)

that's what I just did :)

how's that?

yay \o/

take a look yourself: https://xmpp.org/extensions/xep-0001.html

this does suggest that we have a duplicate for that css file somewhere

indeed

we should remove one of them

kill it with fire

confused. https://github.com/xsf/xmpp.org/blob/102415da28cad2dac9a2bb4c651d95932fec5f86/buildCompleteWebsite.sh#L64

don’t think about that too much

especially not about that sed line a bit below

Unsure wher the duplicate file is

I'm likely missing something obvious

but can't spend to much more time now.

the duplicate file is most likely copied by that script

perhaps that copy can be removed from the script then?

I think so

done

Anybody knows is there's more than xmpp.jp in Japan?

Guus, did I come across as if I was surprised / critizising the discussion?

no, just the venue :)

yes, that was a bit my intention

when you wrote to members@, I was surprised that you invited people to github actually

Well, that's where the various screenshots where. as well as a pre-existing discussion.

not that I've put a lot of thought behind it.

in retrospect, perhaps I shouldn't have assumed that everyone has a github account

yah, I woudl have suggested to suggest to read on github and continue discussion on members@ for inclusivity

every member is on members@, but not every member is on github

(on the other hand, nobody complained)

I'll do that next time. To be honest, I didn't expect much discussion in the first place.

I did (after I read the discussion on the old logo in the archives, I was confident that people will have strong opinions)

I suspect that most people don't care to much - it's a pretty small change.

(which is why I suggested to notify members@ in the first place, at least I recall to have done so, but maybe I only planned and then you did on your own, dunno)

someone did, might've been you :)

I think Board is the right place. They can ask members or not, as they wish.

It was Board who commissioned the current logo.

But it was a previous board, not the current one.

it's the entity, not the persons, that matter. If not, we'd have to revisit everything each time a new board is installed.

Ge0rG: I'm not sure how that matters.

On rereading, I try to understand what exactly Board is the right place to do? To decide which of the three logo variants to use? ✏

I'll suggest to Board to accept the logo improvement as suggested by me in the PR

+1

actually, is anyone from Board here (or anyone that can add this to Trello)? The Board meetings are at a very inconvenient time for me.

Martin, MattJ, nyco show 'available' in my presence list :) Can any of you please add a Trello card to the Board Trello collection: "Descide wether to accept logo improvement as provided in https://github.com/xsf/xmpp.org/pull/363 "?

s/improvement/change/ :)

Hey, I went from 'fix' to 'improvement' :D

_just for you_ ;)

😁

Can we go deeper? How neutral can you word that?

Zash: yes, we probably can. No, I won't.

"Are Board foolish enough to reject the magnificent improvement as provided in [...]"

dwd, :) and - do you still have access to the board trello thingy? I've given up on board picking up my topics from the mailing list.

dwd: an overwhelming majority of the people have...

Guus: having your item on the trello is not a guarantee for anything.

"We, the people of XSF, hereby appeal to the Board to accept the sensible correction of our Logo as provided in... "

Ge0rG: for me, it's the only way that I had some success.

Ge0rG: this could be a subtitle for a project management course

Guus: IIRC the SCAM reference to your mail has been on trello for multiple weeks.

tux for Board! :D

Ge0rG: Please note that I wrote: "some" success.

Guus, https://trello.com/c/KMFd33fZ/285-approve-guuss-logo-amendments

(heart)

"amendments" nice. :)

will that be the 1st amendment to our logo?

Will the second amendment contain bear arms?

The first time round I read "bear" as "beer"

(that was likely his intention)

Which'd be more apropos.

I heard that the biggest proponents of the second amendment are also proponents of beer.

Guus: not at all.

But I think the association of bear arms to the second amendment is a purely US-American thing.

oh dear

that pun hurt me

dear deer?

In my opinion, that pun is the only positive thing about the second amendment.

intosi hey :)

https://about.mattermost.com/blog/u-s-federal-agency-migrates-from-jabber-to-mattermost-the-open-source-way/

Wat

the cisco product, I assume

yes

I'm not sure why but I can't forget the fact that it's not XMPP. And I'm sure I'm not the only one, reading this article

What's not what?

cisco's jabber thing

Is it not? Maybe we need to pull their JABBER[tm] license, then?

Is it?

"Not only did Mattermost support the Pidgin interface for hundreds of their internal users", from what I hear the gateway I really meh

gateways tend to be meh

sure

MUC doesn't provide a room creation date / age type of attribute out of the box, correct?

Lots of work to do it nicely

Guus: Doesn't ring any bells, probably not.

Does https://xmpp.org/community/events.html ever actually get updated? Someone just asked me when the summits were because there's not one on the calendar (they were looking at that page)

Maybe it should link to an up to date list?

or to the calendar

I was going to recommend that they look at the calendar instead, but I can't actually find a link to it on the website

Yeah - I can't find one.

Thought it might be in the agenda somewhere but it's not.

That page could use some words about the annual Brussels summit

oh hi, I didn't see that you were also here :)

SCAM needs to address that. Someone should kick those guys in action.

I saw that nyco recently added something to the wiki - but we've yet to organize ourselves

by-the-by: I'd welcome PRs that improve that page.

Guus, FYI: SCAM is currently "only" a Work Team. The Board (on your request, probably) could spin up a SIG, which is just an open forum, no membership involved. I suspect you have something akin to this going on anyway, but it'd mean the Work Team itself would have the spend authorization, whereas the SIG can just get on with more general work like Wiki pages.

dwd - I'm unsure what value the SIG would add, pragmatically. *everyone* can do pretty much anything that SCAM intends to do, apart from perhaps budgetting things, and interaction with the social media accounts. As summits, conferences and meetups are very topical, I'd expect the effecitve membership of a SIG to change between each event (well, I expect that that *wont* happen in reality).

Well, yes. A SIG is, more or less, a mailing list.

I can get that without formally defining a SIG

board already OK'd that.