Difference between revisions of "Board-Meeting-2022-12-14"

Jump to navigation Jump to search
3,849 bytes added ,  17:55, 14 December 2022
no edit summary
Line 39: Line 39:


==Action Items==
==Action Items==
= Meeting Notes =
== Quorum ==
* Present: Eddie, Matthew, Peter, Ralph, Arc
Guests: MSavoritas, Jonas, Kev, Daniel, Zash, perhaps a few others
== Chair Selection ==
* Ralph
== Editor, Processes, Tooling ==
Eddie:
* a few folks (Jonas, Guus, Georg, etc.) created issues at the GitHub repo
* see https://github.com/xsf/xeps/issues
* would the XSF be willing to fund some of the work?
* could we raise some funds to support the work? (e.g., via OpenCollective)
* there seems to willingness to fund XMPP software projects, might be for standards as well
* this is core work of the XSF
* this situation could be not only a risk but an opportunity
Matthew:
* I have thoughts on the role in general
* as to the current situation, we won't have time to modify processes etc.
* need to find someone to fill in now
* if we are going to put more resources in, make it less robotic and more editorial
  * both editing and writing specs
Ralph:
* clarifying question: editorial or actually writing specs?
Matthew:
* don't think it's necessary for someone to do both
* but if we can automate more of the button-clicking, that person could have more of an editorial role
* there has been initial work on tooling
* I've done a few things to run scripts on PRs and such
* some kind of CI framework to have a PR, run builds, etc.
* still need to add glue for CI workflow
* Guus submitted a PR for linting (now merged)
* I understand the idea of hiring someone but it's more about how than who
* I don't feel comfortable just posting to a freelance site to find someone
* we need someone who understands the standards process, our community, etc.
* I suspect we have lots of volunteers, who don't necessarily need money but direction
Eddie:
* we've had a few people offer to assist
* agree that we don't necessarily need to pay people
Ralph:
* when people stop doing stuff, then someone will eventually step up
* I don't know what the implications would be of hiring someone
Kev:
* if someone wants to throw money around, that's grand
* but it should happen fairly
* needs to be a process for choosing someone
* let's also get clear on what we need for tooling
* what would make life easy for
MSavoritias:
* I don't have a problem being someone who works on tooling
* I have some time to help out with pipelines etc.
* the reason I haven't done that much is that I don't have GitHub
Peter:
* we do have $16k in the bank and can spend if needed
* if we are going to pay people, there could be implications and we'd need to investigate
* I would be happy to do a bunch of the bit-flipping for now
* if we look at how things like Rust does RFCs and Python does PEPs,
Ralph:
* we won't be able to make a decision today but let's be active in figuring this out
Jonas:
* there are things we can do that could be spread around a team
* I'm happy to provide input beyond what is in the issues
* but what's in the issues would solve a large percentage of the problems
* the mechanical bits make it unpleasant
* I'd be happy to assist
Ralph:
* what I'm looking for now is that we need to organize this effort
Peter:
* we have volunteers but someone needs to
Matthew:
* I'm happy to help with technical leadership but I don't want to do all the work
* we need:
  * an acting editor
  * people to write the tooling
* I think we have those
Kev:
* it would help to understand what exactly the process is that Jonas follows now
Peter:
* Jonas, I will coordinate with you about that
== Confirmation of Officers ==
* Matthew Wild ED
* Peter Saint-Andre Treasurer
* Alex Gnauck Secretary (provisional)
== Google Summer of Code ==
* Eddie offered to be the Org Admin
== FOSDEM ==
* no board involvement needed right now
* Ralph is working on the location for the Summit
* Eddie
== Feedback ==
* Jitsi seemed OK, maybe not use it all the time
80

edits

Navigation menu