Indeed, see my post about this almost a year ago (yikes!):
https://groups.google.com/d/msg/sagemath-numfocus/5DkIDzlLksM/BMxvAMfCAAAJ
It's something I've been wanting to take some charge on, but it's a
little complex, because part of the process for NumFOCUS sponsorship
will require some community organizing on my/our parts. In particular
(and I believe this would be good in general) we need to formalize a
bit better some aspects of Sage's project governance. This doesn't
necessarily mean we need to *change* much, but rather formalize a bit.
The main thing that we would have to establish that does not currently
exist is some kind of semi-formal governence body of 3 to 5 people:
"Have a leadership body or team consisting of at least 3 people; these
people should not be employed by the same entity or share a common
affiliation beyond that of the project."
NumFOCUS otherwise doesn't make any requirements as to what those
peoples' role on the project is, how they're selected, or what kind of
power or control they have over the project. My suggestion would be
to give them as limited power as possible. The main point of this is
just that the project has some guarantee of continuity that isn't
dependent on the whims of just one person (or a disorganized blob of
random people moving in and out of the project). To have some
reliable points of contact for the project. The main issue at stake
here is that these people are likely to be the first point of contact
when it comes to deciding how funds get distributed, so to that extent
it is important.
And so, as such, we don't really want to pick a "leadership body"
without some kind of agreed-upon semi-formal governance document
which, among other things, explains the composure of this leadership
body, what its job is (as stated above as limited as possible), how
its members were chosen, and procedures for adding/removing/rotating
members.
Python's recently adopted PEP-13 can serve as a good example:
https://www.python.org/dev/peps/pep-0013/
But it doesn't even have to necessarily be as wordy as that. Another
good example is this slide that William made last year that sums of
Sage's governance in 3 bullet points:
https://cocalc.com/6cd832d3-c523-41e3-9e54-c8f2d2e8fa2a/raw/travel/2018/2018-07-icms/talks/sage/slides/slides.html#5
* Governance:
* when something is disputed, there's a vote on the sage-devel
mailing list
* count the votes a week later
* you get to vote if you are paying attention
Beyond details of the leadership body I would hesitate to "formalize"
anything much beyond rewriting those bullet points as 3 or 4
sentences. We want to keep this simple as possible to keep the
likelihood of disagreement over this to a minimal (though I'm sure
there will be some).
I think it would also be good to formalize the information on
https://wiki.sagemath.org/Community a little better, in the form of a
document that is easily accessible on the main
sagemath.org website
and is not easily editable without submitting pull requests.