XSF Discussion - 2021-10-28

Ge0rG, seen the mail on standards@ regarding CS-2022?

jonas’: thanks!

My first impression is that I don't like the removal of "Core", and that's actually a non-problem because nobody but the weirdest nerds will write "Core Core IM" anyway.

0. Welcome

Hi. Who do we have today?

Here

Present

dwd?

o/

Agenda items?

An update on the fiscal hosting application

https://github.com/xsf/xmpp.org/pull/997 is this a board matter or is this just between us operators@ moderators?

The latter, I feel

Agree

Ok let's start

ack

1. Minute taker

I think that's arc

2. Fiscal Hosting

MattJ go

:crickets:

Just to follow up from last week, I contacted the applicants and they responded with the details I felt were missing. They have also created an initial repository where they will work, and have confirmed a MIT license: https://gitlab.com/deblounge/xmppjs-mam-plugin

On a related note, I'll ping peter again about enabling donations (we accidentally did something wrong and it's bank account only for now, which no one will likely want to deal with)

Thanks to both. What's still left to do?

They're applying to us because the developers have had trouble with some of the larger funding platforms not supporting the country in which they are based. As far as we can tell there should be no issue transferring funds between the XSF and their country.

I think (?) everyone approved a motion to accept the application last week, except for me

(pinged)

I'm prepared to approve it now

Ok, great

click

Yeah, click it, I'm unchanged in my view.

*thumbsup* shall I follow up with a welcome email, or would you like to do that too MattJ as a representative of the board?

Ok, with that out of the way, anything else on this topic?

I mean, they'll see the accepted either way, so maybe it doesn't matter

Sam: please go ahead

Will do. Thanks again all.

Nothing else on this topic from me

3. AOB

I got a ping on https://github.com/xsf/xmpp.org/issues/994

Can we just have communications team figure that out?

It'd be great if we can, but I'd be surprised if it were practical to translate many of the pages given our available resource.

I'm uneasy about it

Well, sure. Hence my question on demand. I wouldn't recommend putting energy in this right now.

I'd love to have a fully translated site for every language, but based on volunteer efforts alone the result will be incomplete and almost consistently out of sync with the English version

In what sense? We can't (meaingfully) translate bylaws and things, but having the capability to translate the occasional blog post or newsletter seems OK?

I think it may be useful to identify some specific pages that would benefit from this. Pages that don't change very often. That I would be fine with, but not the entire site.

floor comment: (1) the beefy part of xmpp.org are the XEPs. There is no chance we'll get consistent implementations for those (though this is a weak argument). (2) what is the xmpp.org target audience? do they need translations? (3) how would we ensure that a translation is kept up to date when a page needs to change?

for blog posts and newsletters, it would be really great to have the translated versions which already exist in the world on the site itself I think

I agree with that. Have translations of blog posts and news letters, but keep official documents in English only. Particularly XEPs and other organizational documents.

I'll pass this as feedback on the ticket

Anything else today?

> I agree with that. Have translations of blog posts and news letters, but keep official documents in English only. Particularly XEPs and other organizational documents. That sounds good to me, and should be fairly easy to do with hugo

Sounds good to me.

+1

Yep

4. Date of Next

I suggest +1W1H

Will that be our last?

No

wfm

The election is on November 25

Ok so we're bumping the meeting time ahead by an hour UTC?

Ah, yes, candidate nominations close on the 7th.

That'd have my preference, due to meeting conflicts

Again I'm fine with that I just want clarity

arc: hence discussing it for once :-D

Cool. Then that seems settled.

5. Close

Thanks all!

I appreciate that.

Gentle ping on initial PR to help fix the registrar. As I said before, I am willing to try and do the work on this, but it will require reviewers and iteam and what not unless someone can give me access to just do it: https://github.com/xsf/registrar/pull/41

(but it's only been a few days, so however people want to proceed is fine by me, I just don't want it falling off the radar)(

Mmmmm

I'll look at what needs doing

https://xmpp.org/registrar/ ta-daa

ooh, nice, I'll go make those fixes you requested. Is that using the same dockerfile + the fixes?

yup

Actually, maybe I don't understand what you mean, it should already be at / and not need rewrites, or do you want it hosted at /registrar?

Well it passes `GET /registrar/` along, which translates to /var/www/registrar/registrar/ which returns 404

Dropping one "registrar" from that `root` line seemed the path of least having to remember how nginx rewrites work

Oh, gotcha. I don't know what best practice is here but it seems wrong to allow all of /var/www to be exposed, not that it's a problem since there's nothing else in there but some default nginx files or something and they wont' be exposed anyways

Not sure if that's what makes "Index of /registrar/" be the heading, but it probably is, and serving from / would be weird

I'm game for whatever though, it just seems to make the most sense to have each container just serve at :80/ and let the main site figure out where it wants that mapped to

I guess I can just disable indexing on / too and only allow it on /registrar

SGTM

Maybe one day we could make an index.html for it 🙂

Just figured out how to fix it w/o changing root too, so whichever way you prefer

I was assuming the main site would override /registrar and we'd only serve things in it out of this container, but I went ahead and turned indexing on just in case

I prefer not having to look att the config for the outermost nginx ever again

Pushed a fix that serves at /registrar

Now that that works, it would be good to cleanup the pending reviews against that registry. Again, happy to help as I know the current editor says they don't have time, just need permissions to do it.

Or someone else who's willing to do it in the case of the ones I've made.

Sam, I think you're in the editor team, aren't you?

jonas’: I got removed at some point

oh it seems so

heading to bed now, will figure out what to do next, thanks already!

> Maybe one day we could make an index.html for it 🙂 Something like that is available for /rfcs (index would be served via hugo, files via rfcs folder) but there is an nginx redirect to figure out before it actually works

This one https://github.com/xsf/xmpp.org/pull/975