[Numpy-discussion] NumPy steering councils members
njs at pobox.com
Fri Jul 21 15:59:37 EDT 2017
On Jul 21, 2017 9:36 AM, "Sebastian Berg" <sebastian at sipsolutions.net>
On Fri, 2017-07-21 at 16:58 +0200, Julian Taylor wrote:
> On 21.07.2017 08:52, Ralf Gommers wrote:
> > Hi all,
> > It has been well over a year since we put together the governance
> > structure and steering council
> > (https://docs.scipy.org/doc/numpy-dev/dev/governance/people.html#go
> > vernance-people).
> > We haven't reviewed the people on the steering council in that
> > time.
> > Based on the criteria for membership I would like to make the
> > following
> > suggestion (note, not discussed with everyone in private
> > beforehand):
> > Adding the following people to the steering council:
> > - Eric Wieser
> > - Marten van Kerkwijk
> > - Stephan Hoyer
> > - Allan Haldane
> Eric and Marten have only been members with commit rights for 6
> While they have been contributing and very valuable to the project
> significantly longer, I do think this it is a bit to short time to be
> considered for the steering council.
> I certainly approve of them becoming members at some point, but I do
> want to avoid the steering council to grow to large to quick as long
> it does not need more members to do its job.
> What I do want to avoid is that the steering council becomes like our
> committers list, a group that only grows and never shrinks as long as
> the occasional heartbeat is heard.
> That said if we think the current steering council is not able to
> its purpose I do offer my seat for a replacement as I currently have
> really been contributing much.
I doubt that ;). IIRC the rules were "at least one year", so you are
probably right that we should delay the official status until then, but
I care much personally.
Fwiw, the rule to qualify is at least one year of "contributions" that are
"sustained" and "substantial". Having a commit bit definitely helps with
some kinds of contributions (merging PRs, triaging bugs), but there's no
clock that starts ticking when someone gets a commit bit; contributions
before that count too.
To become eligible to join the Steering Council, an individual must be a
Project Contributor who has produced contributions that are substantial in
quality and quantity, and sustained over at least one year. Potential
Council Members are nominated by existing Council members, and become
members following consensus of the existing Council members, and
confirmation that the potential Member is interested and willing to serve
in that capacity. [...]
When considering potential Members, the Council will look at candidates
with a comprehensive view of their contributions. This will include but is
not limited to code, code review, infrastructure work, mailing list and
chat participation, community help/building, education and outreach, design
Also FWIW, the jupyter steering council is currently 15 people, or 16
By comparison, Numpy's currently has 8, so Ralf's proposal would bring it
Looking at the NumPy council, then with the exception of Alex who I haven't
heard from in a while, it looks like a list of people who regularly speak
up and have sensible things to say, so I don't personally see any problem
with keeping everyone around. It's not like the council is an active
working group; it's mainly for occasional oversight and boring logistics.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion