XSF Communications Team - 2019-11-20

doing it right now

btw, next week, I'm gonna cover:

Newsletter open process XMPP on Social Media

maybe I should add the SCAM sprints

oops: https://github.com/xsf/xmpp.org/pull/641

good point by Guus

As someone who recently lost all his bookmarks, I don't mind having a list of "XSF-internal" MUC rooms.

But on our public website, I'd focus on rooms that are of interest to the intended audience.

I don't think that the SCAM and Communication Teams MUCs are that.

mabye create the list on the wiki instead?

If 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

I see Guus was faster than me

Well, 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.

I find these arguments relevant, still I remain hesistant

anyway, that twice -1 vs only one 0

Nÿco, what about you?

"hesitant", would vote 0 (not +1 not -1)

What would be the benefit of having these MUCs listed on the public website, for the intended audience?

as you said, transparency I'd love to have audience feedback, qualitative rather than quantitative

it lowers the barrier of entry

someone who would want to suggest just drops a short message on our MUC

As 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?

and/or do both.

easier than getting an account to modify the wiki, easier than creating a PR or reporting an issue on GitHub

I'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)

right, forgot that

You don't need an account to read the wiki

only to change it.

read, but not write

still, providing feedback to the XSF is difficult

generally

not only comm

giving people more options isn't always an improvement.

I'm diverging

regardless, I'm not feeling very strongly about this either way.

I'd personally not add them, but I'm fine with them being added.

Hmm

It would maybe fit best on the contact page

like if workteams where specific departments (Human resources, public relations, etc)

https://github.com/xsf/xmpp.org/pull/641 closed, wontfix

thx!

I like how you're putting things like this up for discussion. Thanks!

real of humour?

Real!

cool

I actually appreciate the way you're doing this - no irony intended.

ok, clear, thx

I appreciate how this discussion happened

regarding social media content:

this week: Gajim tomorrow, Conversations next day

next week: call for content for the newsletter, newsletter process, our social media accounts, SCAM sprints

we have analytics on Twitter but nothing on Mastodon, that's gonna be manual :'(

oops, https://github.com/conversejs/converse.js/releases/tag/v5.0.5

so maybe I'd do Conversations Thu and Converse Fri?

v5.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.

like "now"?

I'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 🙂

I'd rather relay JC's announces

nah, no need to rush-rush things

but I'd suggest moving it up to the pile of scheduled things.

I know you're not convinced, I am not yet either to be completely honest this is only experimentation we'll see the reception

as this update being deployed will benefit the XMPP ecosystem as a whole

fair enough

btw, I'll deploy it rght away :)

deployed

CDNs rock

Yeah, for Openfire we need a small wrapper

I'm trying to get anyone-but-me to do that, to reduce the bus factor of that

https://wiki.xmpp.org/web/Twitter_and_Mastodon_content for transparency and co-construction

https://wiki.xmpp.org/web/index.php?title=CommTeam/Newsletter_Twitter_campaign&redirect=no#Draft_tweets are still usefull

otherwise, still talking about sharing and building together, how about we sync the CommTeam on a Trello board?

Perfect!!

Although 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. ✏

where do you see "diverse"?

Draft tweets, last one

> 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

Maybe re-use these terms? https://xmpp.org/about/technology-overview.html

lunch!

https://trello.com/b/dkhCQCOE/commteam

ok

https://upload.movim.eu/files/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/Dcs2Ri8s6822WXzyWG8SiQySQExvUwZKNX1oyOhA/Capture_d_e_cran_2019-11-20_a__16.37.27.png

nice!