XSF Discussion - 2019-04-25

https://xmpp.org/2019/01/google-summer-of-code-2019/ is that pelican failing to parse the Project_Ideas url? Do we have to tell it for every single one?

Is there an equivalent markdown for `<https://foo.bar>`_ (note, I don't know if that's valid rst either, without a link description)

pep., [url](description)?

or just [url](url)?

right, I did the latter, but that seemed a bit repetitive

pep.: <url> maybe?

http://www.astroscu.unam.mx/rmaa/RMxAC..51/PDF/RMxAC..51_articulo06.pdf

flow: Cool

It appears to be open access, so maybe the XSF could blog about it

Added to https://wiki.xmpp.org/web/News_and_Articles_for_the_next_XMPP_Newsletter#Other - I hope that was right

this is nice to read!

yup !

pep., https://github.com/xsf/xmpp.org/pull/560/files#r278525237

flow would be a nice addition to https://xmpp.org/uses/

Yay, we got 4 slots for GSoC :)

Ah no wait, nvm

jonas’: sure, I was just fixing the link :p

pep., it solves your link markup dilemma :)

I'd say that'S a workaround rather than a fix

But that looks better yes

it’s a fix, because it also fixes the a11y issues of raw URLs

not a fix for my issue

vanitasvitae yes we did.

0. Welcome + Agenda

Hi!

Who do we have today?

I can't join in today, as announced

o/

Guus: no worries

will try to read along

Seve?

1. Minute taker

Who?

(Assuming that nyco is actually here)

(I am)

No minute taker, I assume

Guess no meeting then.

This is getting ridiculous.

because no one wants to take notes? we can still have a meeting, can't we?

No

Having meetings without minutes is not acceptable to me, to be honest.

It's not acceptable according to the org bylaws

And that, I didn't even check.

then we're quite regularly out of bounds

we failed many times to deliver those minutes

Yes, and I am a bit fed up with it.

so am I

So, either one of us takes notes, or we find a sustainable other solution.

I still believe we should use a real-time collaborative text editor just proposing a solution to the lack of volunteers

ok, let me take the notes today

nyco: it is not ideal to have people taking part in the discussion also having to take notes.

go on

please

Ok, thank you.

it is less ideal to have no notes

2. Infrastructure Team lead

I have not seen anyone step up for this?

neither have I

I offer a "Pain au Chocolat" to anyone who will take the lead!

:-D

(that's extrinsic motivation, but hey)

I'll take it

More than I ever got for it :p

MattJ: the pain or the pain?

Oh dear

ok, one for Kev as well => send me privately your mail address

> MattJ: the pain or the pain? indeed, needs clarification and precision

I'll take the pain

But seriously, if nobody else steps up, I'm willing to take it on

I am taking a leap here knowing Kev and Intosi won't object to MattJ as lead, so I motion we appoint MattJ as lead of iteam.

+1

+1

one _pain_ for MattJ 😉

+1

Just one. And a chocolate pastry. Sounds like deal :)

MattJ: you may vote

I can take notes after the meeting, not while we are at it

Well, since I proposed it... +1?

thanks a lot to both Kev and MattJ, congrats MattJ! 😉

Good. The ayes have it.

3. Deferred XEP typos

(@Kev: got your golden parachute?) ✏

I seem to remember there was recent discussion on this in Council?

jonas’: ?

Fine with MattJ as lead for the record.

Kev: thanks. Wasn't there recent discussion in Council on XEP version numbers that touches on this?

On a call at the moment, sorry.

https://github.com/xsf/xeps/pull/780

that?

Ah yes.

happy for Matt to have accepted chocolate-induced-pain.

I think that PR should have review by Council, first.

I.e. I wouldn't like to make changes to XEP-0001 with them forming an opinion on it.

without

I've added the _Needs Council_ label to make sure, and let the minutes reflect that we'd like their input.

4. Server setup

board can form an opinion without Council

no need to wait expressing the opinion - we can hold off voting on it though.

Guus: yes we can, but I like their opinion when it changes the process.

I had a brief discussion with Edwin on the server setup.

iteam members have been a bit swamped with other stuff to pick this up.

In any case, they would like to balance the existing offer to continue hosting parts of our infrastructure where it is now, while also looking into having stuff in some cloud offering

(most likely AWS)

Examples include DNS resolution and hosting our website.

I'd be quite happy with the XSF officially adopting $some_cloud_provider for (at least some) infrastructure

There's no actionable plan, yet, but I have expressed that Board would be ok with paying for hosting some of our infra at AWS. I also think it makes sense to retain existing hosting, but there might be some required hardware upgrades, too.

So MattJ, let's have that discussion with iteam, I'd be happy to sit in and help out.

Great

it would be nice to have the mission critical stuff in some stable environment (maybe we can push to aws from travis directly and save the docker roundtrip for the website and xeps, too?) and allow more experimental stuff on the main machine

jonas’: noted. Moving this discussion to iteam.

5. Tigase / XMPP Logo

I haven't asked stpeter yet. Will contact him this week.

6. AOB

not for me

7. Date of Next

+1W

8. Close

Thanks All!

-1, I'll try to join from my holidays in Italy

Thanks ralphm/all

thx

> Thanks ralphm/all ralphm divided by all?

Oh, I think I'm on a plane next week.

still have wifi? 😉

nyco: such is the fate of a chair person

nyco: crossatlantic, so no

Since I'm flying at 11:00 CEST to JFK, I'm sure I'd be somewhere just passed Iceland or so

Thank you for the meeting guys

minutes sent, please read and correct me if I got something wrong or forgot anything

Thanks nyco :)

Congratulations MattJ

enjoy the pain.

Thanks :)

MattJ, congrats!

MattJ: congratulations! Now please let me bother you in your new role with https://github.com/xsf/mediawiki-docker/issues/2

uh-oh

So it begins

It's merely half a year that I'm asking for that feature

Congrats to MattJ for iteam! After your good job with XMPP.net it is normal!

Can not wait the update of this part: https://xmpp.org/about/xsf/infrastructure-team

Neustradamus: make a PR?

Time to move the https://github.com/stpeter/jabberdotorg to org? Ticket: https://github.com/stpeter/jabberdotorg/issues/9 And have an update of this page too: https://www.jabber.org/team.html

Ge0rG: Only the leader knows what people are in team ^^ cleaning time :)

Linked to https://github.com/xsf/xmpp.org/issues/483

we need a LIDAR!