XSF Communications Team - 2019-03-01

Thanks for a new newsletter guys!

For future reference: please stylize Openfire like that, instead of OpenFire.

Ah ah

Any news for the old new https://xmpp.org/2019/01/the-xmpp-newsletter-31-january-2019 ?

A lot of people are lost with it

Dead link

Already one month.

huh? Where is that link?

Guus: 👍

Neustradamus Where is that link being used?

We can only fix the URL if we have a rewrite for the old URL

Which means configuring the webserver

Not something I can do

jc: in planet for example

We had several talks about this problem but no change

I have created a ticket of course for history like all opened tickets

XMPP.org tickets: https://github.com/xsf/xmpp.org/issues Jabber.org tickets: https://github.com/stpeter/jabberdotorg/issues

Manifesto tickets: https://github.com/stpeter/manifesto/issues

Link Mauve and pep.: With your good memory, can you talk again about the bad newsletter link?

That's weird, why does the planet have the "wrong" link?

I have waited the change for social network... But I have done with the bad date... Because no change.

Always complicated with XSF team... Since several years for have a solution to problems.

Guus: do you have access to the webserver configs for xmpp.org?

I checked the issue Neustradamus but I think that is for iteam instead?

Because I don't have access to any of that

Iteam has a lot of work since several years badly.

So maybe we need more hands on the team

XSF iteam and Jabber.org iteam (do not mix)

Do not forgot the XSF server crash...

Neustradamus, in the meantime they're the only ones with server access

Debian 10 will be release soon, I hope change for TLS problems...

An update of the old manifesto for be more secured... Without SSLv3...

An update of the old M-Link version for jabber.org...

Does the XSF manage jabber.org? Because is not the same XSF managing that server and people that happen to be in the XSF to manage that server

"XSF iteam and Jabber.org iteam (do not mix)" -> https://www.jabber.org/team.html -> https://xmpp.org/about/xsf/infrastructure-team

Please look here the ticket like a lot of other -> https://github.com/xsf/xmpp.org/issues/483

Neustradamus, I guess you want to say all this in iteam@muc.xmpp.org, not here

I have not access :)

You cannot join that MUC?

Yes

Not new ;)

banned?

Because it's the same MUC service

What did you do naughty Neustradamus?

:D

So I don't see many other problems

About Jabber.org, there is a ticket to change to organization on github... https://github.com/stpeter/jabberdotorg/issues

Please look this closed ticket: https://github.com/stpeter/jabberdotorg/issues/1

Can you stop waving unrelated tickets in front of us please

There are tickets about XSF and Jabber.org (some guys are same)

Good, now what

They're not here ✏

It is commteam no?

whatever.. I have more important things to do

There are communication problems since a long time... Need to be solved ✏

Neustradamus, I appreciate a lot your effort, if you have a list of issues please make that list and then I will check. But right now I just don't understand you :)

Look tickets on github

Easy

All have visibility on it

Not only my tickets of course: - https://github.com/xsf/xmpp.org/issues - https://github.com/stpeter/jabberdotorg/issues (do not forgot closed tickets) - https://github.com/stpeter/manifesto/issues

And I can thank again MattJ and Guus about XMPP.net for work done.

Neustradamus, ok I will take a look at them, but I would love to have some specific topics to look into, because I just can't check all the issues. I need something you want to fix.

Easy to look tickets, thanks in advance SouL

Maybe 2019 will be the best year for all.

jc: https://github.com/xsf/xmpp.org/issues/532#issuecomment-468615155

I'm going on holiday to South Africa tonight and will be away for the next weeks, so someone else will have to do it

Happy holiday jc!

thanks 🙂

https://github.com/xsf/xmpp.org/pull/539

Oh I didn't even spot that one 😿 Thank you pep.

Going to merge in 2 minutes