XSF Discussion - 2021-08-26

.

!

?

¡

‽

...

Quorum, at least. ralphm?

Do you want to chair?

Not particularly, but I can :)

MattJ, Tell you what, you chair and I'll do minutes.

Trello looks like it needs a sweep, some old stuff there. I think the two items on my radar are approving the fiscal host stuff, and the recent PR for XEP-0001 (rename Draft stage -> Stable)

0) Roll call

I'm here.

I think we're here

Anyone else with items for the agenda?

Sadly not, though I do need to find some time for that CoC again.

1) Fiscal host policies

As far as I know this is still outstanding. Has anyone not reviewed it who still wants to? It's been dragging on for a bit.

https://pad.disroot.org/p/XSF_Fiscal_Host_Rules fwiw

I suggest we write a post on members@ with the rules in, and ask for any last comments.

I can do that

2) Renaming 'Draft' stage to 'Stable' in XEP-0001

PR at https://github.com/xsf/xeps/pull/1100

Still on holiday. Back next week

No worries ralphm, enjoy :)

jonas’, any comments from Editors?

I'm actually fine with this rename. Draft was a copy of the IETF's "Draft" stage, which itself has disappeared. ✏

So it's now even harder to explain. Calling it "Stable" seems to convey what it needs to.

MattJ, no comment from the editors, except that the technical implementation will probably keep Draft in some non-website-visible places for technical reasons.

wfm

I sent comments from Council to board@, did those arrive?

Oh yes, I did see that, thanks

Okay, I motion we adopt this change to XEP-0001

+1 from me

Without context, I still approve. +1

Goes

2/4

Oh, sorry. +1.

arc, ?

+1

Great

I think that's everything then. AOB?

hm

should someone have asked members@ or standards@ on the Stable vs. Draft thing?

We seem to have already voted on it

🤷

If we want to make sure there are no concrete objections, I can send a note out about this too (and say, delay merging the PR by a week)

I won't touch the PR anyway until tuesday, so that would definitely work for me

Okay, assuming no other business

3) Date of next +1W

4) The End

`<fin/>`

MattJ (or whomelse may chair): to avoid those awkward pauses, Council has moved to letting everyone raise their AOB during the meeting (thanks asynchronous text chat!), so I typically only break for like 15s or so when the AOB section comes up and then continue. ✏

Board meetings are defined by their awkward pauses

oh no, I hope we didn't destroy a tradition there with council

Heh

Thanks MattJ.

Thx

> Expenses must be have been pre-approved by the treasurer. https://pad.disroot.org/p/XSF_Fiscal_Host_Rules Might any native speaker check this sentence? For me it seems like the it should be _have been_ instead of _be have been_.

Either of "must {be,have been} pre-approved" makes sense I think

I guess depending on the tense used in the rest of the text

Then I'd go for _must be pre-approved_.

But I leave this to the native speakers, but the _be must have been_ just doesn't make sense for me.

But maybe this is something very british as I often fail to parse very british texts. :D

'must be have been' can't work. And 'must have been' sounds weird. 'have to have been' would maybe work. 'must be' sounds good.

If you can't read whatever syntax that is, I meant "must be pre-approved" and "must have been pre-approved" both work, right?

I can and I say your second option sounds weird. But maybe it works? 'must be' definitely does work.

Not a native speaker but both sound sane to me.

Mhm.

Slightly different meanings tho, something vs past tense

True. As you already said, it depends on the rest.

"must be have been" is wrong (likely just a composition change mid-sentence); "must be pre-approved" is correct; "must have been pre-approved" is also correct, but.. funny; "have to have been" is clunky but in too common usage

I'd go with "must be pre-approved" or "must have been approved", depending on required meaning

> If you can't read whatever syntax that is, I meant "must be pre-approved" and "must have been pre-approved" both work, right? That's how I understood it.

Not late enough for the end of month XMPP Newsletter reminder 🙂 Please add your project news. You can simply add it via this pad: https://yopad.eu/p/xmpp-newsletter-365days Last addition from August accepted till 2nd of September. Release is planned by 5th of September. Good night to most of you!