GuusAs someone who recently lost all his bookmarks, I don't mind having a list of "XSF-internal" MUC rooms.
GuusBut on our public website, I'd focus on rooms that are of interest to the intended audience.
GuusI don't think that the SCAM and Communication Teams MUCs are that.
Guusmabye create the list on the wiki instead?
SouLIf that list is required, I would maybe keep it in the wiki and not in the website. I would rather keep workteams as something internal for the XSF, I don't see the value of random internet people joining this room
SouLI see Guus was faster than me
GuusWell, I don't mind showing that we're an open organisation but I don't think that listing them helps the intended audience finding the correct place to find help.
NÿcoI find these arguments relevant, still I remain hesistant
Nÿcoanyway, that twice -1 vs only one 0
SouLNÿco, what about you?
Nÿco"hesitant", would vote 0 (not +1 not -1)
GuusWhat would be the benefit of having these MUCs listed on the public website, for the intended audience?
Nÿcoas you said, transparency
I'd love to have audience feedback, qualitative rather than quantitative
Nÿcoit lowers the barrier of entry
Nÿcosomeone who would want to suggest just drops a short message on our MUC
GuusAs an alternative to the alternative that I've suggested on Github (which would still work for me): Maybe add the MUCs to the pages of the individual Work Teams?
Guusand/or do both.
Nÿcoeasier than getting an account to modify the wiki, easier than creating a PR or reporting an issue on GitHub
GuusI'd not add them to https://xmpp.org/community/chat.html without making it very clear that these rooms are mostly 'internal' (I prefer to not have them listed at all on that page)
Nÿcoright, forgot that
GuusYou don't need an account to read the wiki
Guusonly to change it.
Nÿcoread, but not write
Nÿcostill, providing feedback to the XSF is difficult
Nÿconot only comm
Guusgiving people more options isn't always an improvement.
Guusregardless, I'm not feeling very strongly about this either way.
GuusI'd personally not add them, but I'm fine with them being added.
Guusgets back to work
SouLIt would maybe fit best on the contact page
SouLlike if workteams where specific departments (Human resources, public relations, etc)
Nÿcoso maybe I'd do Conversations Thu and Converse Fri?
Guusv5.0.5 fixes a very nasty bug that effectively silently drops messages. If we're going to mention the release, doing it sooner rather than later is good.
GuusI'm still not sold on the idea that we're publishing content for other projects in the first place, but I'll leave that to you for now 🙂
NÿcoI'd rather relay JC's announces
Guusnah, no need to rush-rush things
Guusbut I'd suggest moving it up to the pile of scheduled things.
NÿcoI know you're not convinced, I am not yet either to be completely honest
this is only experimentation
we'll see the reception
Guusas this update being deployed will benefit the XMPP ecosystem as a whole
Nÿcobtw, I'll deploy it rght away :)
GuusYeah, for Openfire we need a small wrapper
GuusI'm trying to get anyone-but-me to do that, to reduce the bus factor of that
for transparency and co-construction
are still usefull
Nÿcootherwise, still talking about sharing and building together, how about we sync the CommTeam on a Trello board?
GuusAlthough I don't have an immediate better alternative, I'd not use the term 'diverse' as is done in those templates. These days, 'diverse' mostly refers to diversity in context of race, ethnicity, gender, sexual orientation.
GuusAlthough I don't immediately have a better alternative, I'd not use the term 'diverse' as is done in those templates. These days, 'diverse' mostly refers to diversity in context of race, ethnicity, gender, sexual orientation.
Nÿcowhere do you see "diverse"?
GuusDraft tweets, last one
Guus> XMPP is Diverse - you will never get "locked in" when using XMPP technologies. As an example, you have plenty of options to choose from when looking for a XMPP client. https://xmpp.org/software/clients.html
GuusMaybe re-use these terms? https://xmpp.org/about/technology-overview.html