XSF Discussion - 2018-12-20

https://burtrum.org/up/1c2f67f1-92c3-4340-8c77-a04bc8ccf85c/bHXnBWvGS-mnfKxuKEngdg.gif

This must be the logo

what the...

I'm gone _one day_ and I see logo's in flaming letters?

moparisthebest: you get my vote

Run for presidency

executive director?

not enough lasers and metallic letters to me

lasers only go on sharks (and the occasional ill-tempered bass), not logos

Guus, pft, raptors!

laserraptors!

https://www.youtube.com/watch?v=Bh7bYNAHXxw

I want a president riding on a bear.

a laserraptor!

Ge0rG will you settle for an action figure? https://www.amazon.co.uk/Putin-Riding-Bear-Action-Figure/dp/B00X61MVE8

Guus: sure thing, even with the printing on the package being beyond broken

Although I sent apologies for missing the upcoming board meeting, I unexpectedly managed to make it in time.

Great

("woohoo!" "yeah!")

thanks Seve 🙂

hey

:)

prrrods...nevermind

XSF Board Meeting | Logs: http://logs.xmpp.org/xsf/ | Agenda https://trello.com/b/Dn6IQOu0/board-meetings

0. Welcome

It seems we have everyone.

Dave raised a point about XEP-0412, so that's on the agenda.

it's even in Trello board

I have nothing else for the agenda

Me neither

prios?

the former board handed it over

I don't think they did.

But I see you added it as a card, so it is on the agenda

Useless bunch

1. Note taker

dwd around?

Guess not.

Continuing as we have a bunch of items.

2. XEP-0412, Compliance Suites 2019

I agree with Guus' comments on the board list: let's create a place holder for this XEP until such time it is clear what the Council decides.

Probably similar to what was done for XEP-0028.

As I've replied on the board list (which is not publicly accessible, so let me repeat: I'm against keeping a XEP that was prematurely published around.

Guus's words make sense, indeed

wfm

jonas’: can you take care of this?

for the record: My main argument is that third parties might take the fact that it is published as a reason to start work based on it. As long as there's a chance that the XEP will be revoked/unpublished, we should take steps to avoid people from spending resources on something that we're not sure of yet.

the probability that it happens again is non-zero so let's revert like code can be in a repo

Second, I don't like how this can be perceived as putting pressure on council members that yet need to vote. A veto now will cause more issues (having to retract the XEP), which takes away from the freedom of choice of these council members. I'm sure that Kev can hold its own, but lets not create a precedent here. We can prevent this by rolling back before the remaining council members cast their vote.

ralphm I don't think jonas’ has access to that mailing list

so he would not have seen my response.

or suggestion to fix

the pressure might be already felt, by mistake of course

nyco: the problem is that the number was given out, and if there's going to be any XEP for this, it should be the one for compliance suites, or a tombstone.

Guus: I just wrote the fix above: like XEP-0028

that's only a technical workaround

I'm not sure what happened with XEP-0028, ralphm

I'm happy to link it here: https://xmpp.org/extensions/xep-0028.html

ah, ok, that never got replaced/restored, but is retracted 🙂

I'm not sure if it should be removed from source control, though. Just adding a new commit with a notice like this should suffice.

yeah, something similar would work.

XEP-0028: No Such XEP XEP-0412: No More Such XEP XEP-0412: Like XEP-0028

I'm sure the Editor Team can resolve this.

yep, not our duty

The Editor Team being just jonas’ nowadays?

nyco: instructing them what to do in this case is, so we just did.

Guus: no, but he added this particular commit

who else is editor? Sam's membership expired.

https://xmpp.org/about/xsf/editor-team <-- ah, a bunch

I don't think think so, work teams don't have an expiry, I think.

there is a card "Call for editors" in our Trello board

can non-members be part of a work team?

When taking back the CommTeam, only members were accepted

Guus: no

“Participation in Teams shall be limited to elected Members of the Corporation.”

So, Sam's out, to my disappointment.

Ah.

Good point

moving on

3. Compliance Suites (again)

This point is about the discussion we had last week, regarding badges

Dave suggested, on list, something that was also mention in the meeting:

“So I suggest we run an Experiment. This experiment would have some badges that developers can claim on their projects, fully self-certified (ie, we do not attempt to create a compliance suite). The Badges themselves - the images used - would remain copyright XSF - I don't think we need the full weight of trademark law. We agree to revisit the scheme in 6 months and assess how it's being used.”

I'd like to put this up for a vote.

wfm

+1

+1

yep, plus one

try and iterate, I like that

"ie, we do not attempt to create a compliance suite" <-- that does not relate to the XEP, but instead to an automated verification tool, right?

yes

we'll see what we make of it

+1

given the experience and feedback

Seve?

Not sure yet, honestly, it is a bit abstract, but I like to try and iterate as nyco said

is that a +0?

I'm +0

Ok

Yes, thanks ralphm

or -0 ?

Motion carries.

I've added a trello card on a backburner list, for us to remember to evaluate this in +6M

I'll discuss with dwd how to move forward to actually have images that represent a badge.

Guus: thanks

4. Call for Editors

do we need to facilitate the badges being created?

I have a graphic designer who may help us

if someone volunteers to create such badges, that's be great

'd

nyco if he'd be interested, that would be great

could you ping him?

she

her

I'm on it

Cool

thanks

Now, onto #4

So this was raised by Dave on list

But I suggested that Council should issue this call, as they actually appoint candidates.

(I didn't see Dave's mail)

or really, they select them and we appoint

Our website lists 6 editors, one of which is Sam. We furher have Kev, PSA, Jonas', Flow and JCBrand

Mail from 2018-12-12, included this:

“> > 1) XSF Editor - this team needs more members. Could you put out a call? (I meant to ask last week, actually). Given your charter, with the XMPP Council selecting volunteers and presenting them to the Board for approval, I believe it would be proper for you to put out the call to our membership. ”

(the latter is my reply)

Dave agreed and would.

I'm happy for either to issue that call.

So I think this item is handled.

5. GSoC

I sent a request for help to the mailing list, but did not get any response

We put out a request for an admin. Have we gotten candidates yet?

ok

Keeping this one on.

Let's nudge in the new year

let's not keep it to long though

strive to decide one way or the other mid january?

Guus: agreed

yep

6. Summit / FOSDEM

I don't have anything to report.

nor me.

me neither

7. Meeting with Peter

ah

Still pending.

😢

8. Board Priorities

nyco says this was carried over.

so this is a subject that the former board has passed on, like a hot potatoe do we want to commit to prios? or we drop it? (or any other option?)

given the ineffectiveness of last board on this (them slackers!), I wonder if this has any practical use.

I have the feeling that the board resolves issues as they arrive we may bot have common, shared, larger goals

I think in general the board's role here is to enable most of these things to happen

We established SCAM for meetups, for example, and I think that's going well

The main thing blocking many other priorities is funding

Sure, we need to do stuff (c)(r), but do we need a defined list of priorities for that to happen?

which is something we are focusing on

MattJ and time

so I don't have any problems with the board's current tasks

i.e. setting a priority is fine, but it has to translate to action items. What are those?

This was my problem with all the previous discussions about priorities

correct: prios > actions do we want to support that train of thoughts?

Sure

So we continue as we have.

wfm

My #1 priority is fixing our funding problems

Agreed

how? what actions have (expected) impact?

I guess fixing the following up with sponsors would be a great start, and a big effort

XSF sponsorship AND Summit's

We have totally failed at dealing with our sponsors for the past few years (at least). ralphm and Guus are working towards fixing that (with help from stpeter)

Well, we need to clean up our list of sponsors, assess our current financial situation with Peter, and then come up with an idea of what we want to do. E.g. the Summit always costs us money, and if we want to do more, we would need money.

With funds coming in, we'll be able to better fund meetups and such, which was the main priority we discussed after the survey results were processed

Right, I'm trying to schedule a meeting before end-of-year

let's not expect fixing sponsorship will resolve lots of pain points ✏

it's a place to start.

ok then

I generally agree

Sponsorship is our only source of money, so yeah, it does

The other resource is people, and that's a tough one to resolve in general.

9. AOB?

?

none from me

None here

10. Date of Next

+1W, provisionally

ok

I think I can attend

with the holidays, all bets are off for me

(As in, I'll have to get permission from my wife 😉 )

I should be able to attend as well

11. Close

Thanks all!

thx all! 😉

Thank you guys

XSF Discussion | Logs: http://logs.xmpp.org/xsf/ | Agenda https://trello.com/b/Dn6IQOu0/board-meetings

happy holidays!

Thanks

No news about the Trademark license I asked Board about?

thanks for the ruling, board, will take care of it immediately

can someone confirm though that I’m reading the backlog correctly in the sense that board prefers the XEP to be un-published?

Yes.

jonas’: in such a way that there's a place holder, like with XEP-0028. Feel free to craft a reasonable message.

did both

build is in progress

Yay

ralphm, FYI https://xmpp.org/extensions/xep-0412.html

there’s no state which has a more fitting "red text below the metadata" unfortunately

(and that’s generated by the templating stuff)

I think it is fine like this. Thanks!

you’re welcome I guess? :)

So glad we have a process for that. It would have been a horrible oversight if we just waited for the last council member to vote.

If only somebody had remembered that process after XEP-0403...

hm?

To have it as 404

pep. :p

jonas’, I don't guarantee I have time to help with editing as an everyday^H^H^H week thing, but is there anything that I can help automate maybe?

pep., most stuff which can be automated is already

the only thing I’m missing is something which hooks on the finished docker builds and tells me that they’re done, so that I can send the emails

(the email sending is 99% automated, but I’m paranoid and we agreed on not sending out mails for editorial changes to keep the Signal/Noise ratio good, and that’s not implemented in the tool yet) ✏

soo… if you’re inclined to make a thing which receives the docker-build-has-finished webhook and sends me a message, that’d be good

via jabber, preferably

because when it comes via jabber, i can easily hook my buildbots into doing the email sending once I’m confident that the tooling will do the right thing

PubSub!

Link Mauve, also good

the buildbots are based on pubsub already ... buuuut I’d have to modify them to be able to subscribe to more than one node