XSF Communications Team - 2018-02-22

JC, it'd be good to have a list of comm-team members, and a chair

Hopefully, we can put that to a board vote later today

The list was on the first mail, right? We are messing a chair.

oh, right. it is in the mail

I guess Winfried also

I only remembered the 'open team' aspect that was described

but you're right

Missing, not messing, sorry.

It's me messing with the keyboard..

Guus, Seve: yes, everybody in the original email plus Winfried Tilanus

Guus, Seve: concerning a chair, if no one else wants to, I'm willing to chair

SaltyBones, nyco: ^

Whatwhatwhat?

Oh yeah JC should do it!

this is being discussed in @xsf now

I'm on the street so I cannot check, I agree with jcbrand chairing.

The board just voted in favor of establishing the communcations work team again, in compliance with all things discussed on the mailinglist, and JC as chair. There was one difference; as our bylaws prohibits non-XSF members to be part of a work team, SaltyBones could not be voted in the team.

please take that as a hint to sign up as a member, SaltyBones :)

Great news, thanks Guus

we've further discussed with iteam (intosi was present) that they'll facilitate giving team members access to the resources they need (think the github repo and social media accounts). I suggest that you compile a list of github and twitter account names, and ask iteam for access

I neglected to explicitly add Winfried to the member list - I overlooked

SeveFP is my github

Standing on the train, not much I can do typing with one hand.

JC, can you arrange for access with iteam (intosi)? No need for me to be a middle man there.

oh, intosi already made a github group for you, that JC can manage

Guus: will do

might I suggest that one of the first things you guys do is re-instate a public work team page again, similar to https://xmpp.org/about/xsf/editor-team ? :)

I'm excited for this to have happened! Looking forward to see what we can make of this!

Thanks for your help with this Guus

jc: happy to

oh wow, I woke up late and a lot of stuff has happened today. I will have to review guidelines for what it means to be on an offical work team (this is new to me, so if I'm stumbling around, don't mind me)

The commteam is not complete in email it is normal?

There are forgotten things, no? Winfried and me are not in the list

Neustradamus: did you ever request to be part of the team?

We forgot about Winfried, will ask that he gets added still

Is there an established way to add members to a workteam?

Daniel_W: members need to be approved by the board

But before that happens they need to at least indicate their desire to be on the team :)

I wrote an email the the XSF members list, with an initial member list ;)

Afterwards Winfried indicated he wants to be on the team as well

Thank you very much Guus

Also thanks to jcbrand

SaltyBones, will you apply for membership? What a surprise, I thought all participants at the Summit were members.

(except invited people)

A positive surprise, I mean!

I honestly have no clue how to even do that... ;)

https://xmpp.org/community/membership.html

basically edit a wiki page about yourself, and wait for the votes

> Currently three work teams are chartered and active:

And it then lists 4

My bad 😂

When you guys add Comms, can you please fix that too? You all should have access to the github repo now!

Oh that's cool

I have sent a message here, I contact you in private (no reply) and no changes here: https://wiki.xmpp.org/web/CommTeam and in the mail on members@, no date for the beginning...

jcbrand is not here oups

Guus, what is the page you quoted the "Currently three work teams..."?

Neustradamus, sorry, what do you mean?

Seve, this one: https://xmpp.org/community/membership.html

Guus, ok thanks

I'll add the old https://wiki.xmpp.org/web/CommTeam page back to the wiki sidebar

can you guys fix the content?

Yes, we have to check together what we put there and such

Guus, do you think it is ok if I fix the 'three' to 'four' for now? While we get more things in place? Or I shouldn't?

Seve, go for it

Also, feel free to take ownership

As a member of the Communications Work Team we trust you to use your best judgement here - that's the reason why I like having such a team

Also, as long as you know how to undo a certain change, I'm happy for you to make mistakes.

Have you seen the readme, that lists how you can test changes locally?

Guus, thank you, I'm checking!

(A lot of my work has been lost with the server crash... And I have not saved). Hope that now that there are backups...

Neustradamus, if you refer to the wiki server crash - that was about a year ago. Any backups we had are already used.

Yes yes, a lot of datas have been lost...

Hope that now, it will be better for do not lost again

Between 21 June 2017‎ to 21 October 2015‎ nothing It was me who was updating the main page and applications part with Alex Not to mention other contributions...

Neustradamus, we will take care of it from now on. I'm sorry, I know how you feel but we have to look forward and learn from that.

Like I have already informed on the xsf mucroom, a missing link: http://xmpp.org/about-xmpp/faq/

where did you find that link? https://xmpp.org/about/faq.html does work

On the Web

It is a missing redirection

It was from the old website

If we don't link to this from our own sources any more, I'm less concerned.

But a redirection is done on the webserver...

?

The server has a lot of url rewritting...

It is one to add

Agreed, that'd be nice.

but again, if there's no-one linking to this... not the highest of priorities.

Neustradamus, what is http://xmpp.org/about-xmpp/faq/? Redirect to https://xmpp.org/about/faq.html ?

http://xmpp.org/about-xmpp/faq/ must be redirected to https://xmpp.org/about/faq.html

Like http://xmpp.org/xmpp-software/clients/ for example...

Neustradamus, but we don't point anywhere to there, I don't get why is needed.

Seve, at some point in the past, that page apparently existed, so external sources might still refer to it. That said, I analyzed our access logs a couple of months ago for 404's - this was not in the top (if it was in it at all)

so, yeah, we could add that redirect to fix an issue that's probably not occurring for anyone in the wild.