[Pandas-dev] pandas governance

[Jeff Reback]

yes on board with this as well. We do have a fiscal governance document
w.r.t. NUMFocus. That should at the very least be reference by
the governance docs. Certainly starting with the jupyter docs is a good
think.

I don't think we will have the long-long-long discussion that numpy had
about the steering committee representation :)

Jeff

On Tue, Jan 5, 2016 at 7:29 PM, Joris Van den Bossche <
jorisvandenbossche at gmail.com> wrote:

> Sounds very good!
>
> Certainly now we are a NumFOCUS supported project (and have to deal with
> financial things), I think this is important to do.
>
> 2016-01-05 19:15 GMT+01:00 Wes McKinney <wesmckinn at gmail.com>:
>
>> hi folks,
>>
>> I'm sorry I didn't do this 2 or 3 years ago when I first handed over
>> release management responsibilities to Jeff, y-p and others, but it
>> would be good for us to formalize the project governance like most
>> other major open source projects. See IPython / Jupyter for an example
>> set of governance documents
>>
>> https://github.com/jupyter/governance
>>
>> Numpy also recently adopted a goverance document, based on the Jupyter
> one: http://docs.scipy.org/doc/numpy-dev/dev/governance/governance.html
> and https://github.com/numpy/numpy/pull/6352.
> Maybe also worth a look (although I don't know what they exactly changed
> from the Jupyter one).
>
>
>> I don't have particular concerns over the project's direction and
>> decision making procedure, but as I've had several people raise
>> private concerns with me over the last few years, I think it would be
>> good for the community to have a set of public documents on GitHub
>> that lists people and process in simple terms. This is especially
>> important now that we can receive financial sponsorship through
>> NumFOCUS, so that sponsored contributions are subject to the same
>> community process as volunteer contributions.
>>
>> A basic summary of how we've been informally operating is: Project
>> committers (as will be defined and listed in the governance documents)
>> make decisions based on consensus; in the absence of consensus (which
>> has rarely occurred) I will reserve tie-breaking / BDFL privileges. I
>> don't recall having ever having to put on the BDFL hat but it's the
>> "just in case" should we reach some impasse down the road.
>>
>> Sounds good!
>
>
>> I can take a crack at assembling something based on the IPython
>> governance docs if that sounds good.
>>
>> At the end of the day, an OSS project is only as strong as the
>> individuals committing code and reviewing patches. As pandas will be 8
>> years old in April, with 6 years as open source, I think we have a
>> good track record of consensus-, common-sense-, and
>> fact/evidence-driven decision making.
>>
>> best,
>> Wes
>> _______________________________________________
>> Pandas-dev mailing list
>> Pandas-dev at python.org
>> https://mail.python.org/mailman/listinfo/pandas-dev
>>
>
>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20160106/94ce5fa7/attachment.html>