mpl governance

tacaswell · July 31, 2016, 10:32pm

Folks,

During the sprints at SciPy Mike Droettboom and I started to adapt the
Jupyter governance documents for matplotlib.

We are doing this in the open, and a pull request of the changes is at:

https://github.com/matplotlib/governance/pull/1

To be clear, this is a work in progress and is not final or in force.

We propose the mechanism for ratifying the these documents is to, after
input from the community, have the current "matplotlib Executive Committee"
(the signers of the FSA with NUMFocus) vote.

Tom

ps A very similar email was sent to the matplotlib-devel list on July 17
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-users/attachments/20160731/aa32aa09/attachment-0001.html>

tacaswell · July 31, 2016, 10:36pm

I am not sure what you mean.

···

On Sun, Jul 31, 2016, 18:35 Dipankar ?Dipu? Ganguly <dipugee at gmail.com> wrote:

How will this impact on the image processing aspects?

Dipu

Dipankar Ganguly
Consultant: Strategy/Technology/Commercialization
Bothell, WA
Cell: 408-203-8814
email: dipugee at gmail.com
Dipankar (Dipu) Ganguly - Chief Strategic Advisor - Januity | LinkedIn

On Jul 31, 2016, at 3:32 PM, Thomas Caswell <tcaswell at gmail.com> wrote:

Folks,

During the sprints at SciPy Mike Droettboom and I started to adapt the
Jupyter governance documents for matplotlib.

We are doing this in the open, and a pull request of the changes is at:

Initial adaptation from Jupyter to matplotlib by mdboom · Pull Request #1 · matplotlib/governance · GitHub

To be clear, this is a work in progress and is not final or in force.

We propose the mechanism for ratifying the these documents is to, after
input from the community, have the current "matplotlib Executive Committee"
(the signers of the FSA with NUMFocus) vote.

Tom

ps A very similar email was sent to the matplotlib-devel list on July 17

------------------------------------------------------------------------------
_______________________________________________
Matplotlib-announce mailing list
Matplotlib-announce at lists.sourceforge.net
matplotlib-announce List Signup and Options

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-users/attachments/20160731/13454aa3/attachment.html>

tacaswell · August 27, 2016, 6:09pm

Folks,

Following up on last month's email, are there any comments, for or against,
adopting the Jupyter governance model and the mechanism of ratifying the
adoption?

Tom

···

On Sun, Jul 31, 2016 at 6:32 PM Thomas Caswell <tcaswell at gmail.com> wrote:

Folks,

During the sprints at SciPy Mike Droettboom and I started to adapt the
Jupyter governance documents for matplotlib.

We are doing this in the open, and a pull request of the changes is at:

Initial adaptation from Jupyter to matplotlib by mdboom · Pull Request #1 · matplotlib/governance · GitHub

To be clear, this is a work in progress and is not final or in force.

We propose the mechanism for ratifying the these documents is to, after
input from the community, have the current "matplotlib Executive Committee"
(the signers of the FSA with NUMFocus) vote.

Tom

ps A very similar email was sent to the matplotlib-devel list on July 17

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-users/attachments/20160827/5da83e3c/attachment.html>

pmhobson · August 29, 2016, 3:39pm

I think this is a good idea.

···

On Sat, Aug 27, 2016 at 11:09 AM, Thomas Caswell <tcaswell at gmail.com> wrote:

Folks,

Following up on last month's email, are there any comments, for or
against, adopting the Jupyter governance model and the mechanism of
ratifying the adoption?

Tom

On Sun, Jul 31, 2016 at 6:32 PM Thomas Caswell <tcaswell at gmail.com> wrote:

Folks,

During the sprints at SciPy Mike Droettboom and I started to adapt the
Jupyter governance documents for matplotlib.

We are doing this in the open, and a pull request of the changes is at:

Initial adaptation from Jupyter to matplotlib by mdboom · Pull Request #1 · matplotlib/governance · GitHub

To be clear, this is a work in progress and is not final or in force.

We propose the mechanism for ratifying the these documents is to, after
input from the community, have the current "matplotlib Executive Committee"
(the signers of the FSA with NUMFocus) vote.

Tom

ps A very similar email was sent to the matplotlib-devel list on July 17

_______________________________________________
Matplotlib-users mailing list
Matplotlib-users at python.org
Matplotlib-users Info Page

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-users/attachments/20160829/07433fe5/attachment.html>

dipugee · August 30, 2016, 12:28am

Hi:

I have ImageJ installed on the same Mac that I am using to develop IPython Image Processing algorithms under Anaconda Navigator?s Jupyter. Can I load ImageJ as a package in my Image Processing environment and call its functions as I do with matplotlib?

Thanks

Dipu

Dipankar ?Dipu? Ganguly
dipugee at gmail.com
Cell: 408-203-8814Dipankar ?Dipu? Ganguly
dipugee at gmail.com
Cell: 408-203-8814

···

On Aug 29, 2016, at 8:39 AM, Paul Hobson <pmhobson at gmail.com> wrote:

I think this is a good idea.

On Sat, Aug 27, 2016 at 11:09 AM, Thomas Caswell <tcaswell at gmail.com <mailto:tcaswell at gmail.com>> wrote:
Folks,

Following up on last month's email, are there any comments, for or against, adopting the Jupyter governance model and the mechanism of ratifying the adoption?

Tom

On Sun, Jul 31, 2016 at 6:32 PM Thomas Caswell <tcaswell at gmail.com <mailto:tcaswell at gmail.com>> wrote:
Folks,

During the sprints at SciPy Mike Droettboom and I started to adapt the Jupyter governance documents for matplotlib.

We are doing this in the open, and a pull request of the changes is at:

Initial adaptation from Jupyter to matplotlib by mdboom · Pull Request #1 · matplotlib/governance · GitHub

To be clear, this is a work in progress and is not final or in force.

We propose the mechanism for ratifying the these documents is to, after input from the community, have the current "matplotlib Executive Committee" (the signers of the FSA with NUMFocus) vote.

Tom

ps A very similar email was sent to the matplotlib-devel list on July 17

_______________________________________________
Matplotlib-users mailing list
Matplotlib-users at python.org <mailto:Matplotlib-users at python.org>
Matplotlib-users Info Page

_______________________________________________
Matplotlib-users mailing list
Matplotlib-users at python.org
Matplotlib-users Info Page

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-users/attachments/20160829/067247ab/attachment.html>

jason · August 30, 2016, 1:00am

We're about to have some discussions in Jupyter about our governance model,
and probably tweak it now that we have more experience with it. While that
experience may not transfer to matplotlib's situation, it still might be
good to see that discussion before making huge changes.

Thanks,

Jason

···

On Mon, Aug 29, 2016 at 11:40 AM Paul Hobson <pmhobson at gmail.com> wrote:

I think this is a good idea.

On Sat, Aug 27, 2016 at 11:09 AM, Thomas Caswell <tcaswell at gmail.com> > wrote:

Folks,

Following up on last month's email, are there any comments, for or
against, adopting the Jupyter governance model and the mechanism of
ratifying the adoption?

Tom

On Sun, Jul 31, 2016 at 6:32 PM Thomas Caswell <tcaswell at gmail.com> >> wrote:

Folks,

During the sprints at SciPy Mike Droettboom and I started to adapt the
Jupyter governance documents for matplotlib.

We are doing this in the open, and a pull request of the changes is at:

Initial adaptation from Jupyter to matplotlib by mdboom · Pull Request #1 · matplotlib/governance · GitHub

To be clear, this is a work in progress and is not final or in force.

We propose the mechanism for ratifying the these documents is to, after
input from the community, have the current "matplotlib Executive Committee"
(the signers of the FSA with NUMFocus) vote.

Tom

ps A very similar email was sent to the matplotlib-devel list on July 17

_______________________________________________
Matplotlib-users mailing list
Matplotlib-users at python.org
Matplotlib-users Info Page

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
Matplotlib-devel Info Page

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-users/attachments/20160830/d7dd93c7/attachment.html>

bussonniermatthias · August 30, 2016, 1:23am

Hi all,

To extend on what Jason said, the discussion have started privately on
the Jupyter Steering council mailing list, we'll move it to a public
space but we want to shorten what have been posted and make sure it's
suitable for public consumption.

···

--
M

On Mon, Aug 29, 2016 at 6:00 PM, Jason Grout <jason at jasongrout.org> wrote:

We're about to have some discussions in Jupyter about our governance model,
and probably tweak it now that we have more experience with it. While that
experience may not transfer to matplotlib's situation, it still might be
good to see that discussion before making huge changes.

Thanks,

Jason

On Mon, Aug 29, 2016 at 11:40 AM Paul Hobson <pmhobson at gmail.com> wrote:

I think this is a good idea.

On Sat, Aug 27, 2016 at 11:09 AM, Thomas Caswell <tcaswell at gmail.com> >> wrote:

Folks,

Following up on last month's email, are there any comments, for or
against, adopting the Jupyter governance model and the mechanism of
ratifying the adoption?

Tom

On Sun, Jul 31, 2016 at 6:32 PM Thomas Caswell <tcaswell at gmail.com> >>> wrote:

Folks,

During the sprints at SciPy Mike Droettboom and I started to adapt the
Jupyter governance documents for matplotlib.

We are doing this in the open, and a pull request of the changes is at:

Initial adaptation from Jupyter to matplotlib by mdboom · Pull Request #1 · matplotlib/governance · GitHub

To be clear, this is a work in progress and is not final or in force.

We propose the mechanism for ratifying the these documents is to, after
input from the community, have the current "matplotlib Executive Committee"
(the signers of the FSA with NUMFocus) vote.

Tom

ps A very similar email was sent to the matplotlib-devel list on July 17

_______________________________________________
Matplotlib-users mailing list
Matplotlib-users at python.org
Matplotlib-users Info Page

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
Matplotlib-devel Info Page

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
Matplotlib-devel Info Page

jason · August 31, 2016, 4:20pm

FYI, here is the (beginning of the) public discussion of the Jupyter
governance model we were talking about:

github.com/jupyter/governance

Feedback on governance

opened 03:49PM - 31 Aug 16 UTC

Carreau

Hello All, This follows some conversation that I had at SciPy, as well as some… discussion that started on the steering council mailing list but we believe it is important to get this discussion in public. I heard a lot of good things about our governance policy and our governance documents; at SciPy in particular, but also other event, or even on a day to day basis. In particular you will be happy to know that Matplotlib want to adopt the same governance structure, and is looking to roughly take our documents as is by just replacing Jupyter by Matplotlib: https://github.com/matplotlib/governance/pull/1 I think though that some wording in the various documents and some details of the governance structure could be improved, mainly to convey better the spirit of the document. The current governance document require people to have been "involved" in the project for a period of at least a year: > 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 This is a perfectly reasonable requirement to be sure that the candidate have shown a long term interest to the project. I'm concern though that this is in practice biases toward technical contributions. We did explicitly make the language in the governance document vague, in order to include more people: > 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 work, etc I think we can do a better job regarding this point by trying to get in the steering council members from various horizons and with often various vision for the project. I think in that long time user of Jupyter like Greg Wilson, Lorena Barba, Doug Blank, could be of great help in the council as they are regular users of the notebook and are in contact with people using the notebook on a day to day basis. I believe people like Gael Varoquaux, have extremely valid critics of the notebook in part because of they have to stay on Old version of the packages and upgrade often leapfrog in many versions. People have a wider-view of the project like Jamie Whitacre and Carol Willing would be extremely helpful as well,... Thus I would like to try to emphasise the diversity of the steering council. My personal though, is also that the steering council might be too large (or on the verge of becoming too large), and adds a lot of noise for each of the members. I would like to think about a "restricted board" that could make more non-sensitive decision without the all council approval. This does not prevent the board to request advice from council advisor, that could more technical in specific domain. I think in particular at people like Adrew Gibiansky Haskell), Philipe A. (R) , that have show longterm regular involvement in the project on highly specific technical points. This leave also the door open to have a rotating board, which is smaller, and that could be picked changed at regular interval in order to relieve some of the board member from yet-another-task. The reduced board size could also likely resolve things more quickly, as it is often hard to get global consensus. How to select this board might also help address on of the other main comment I had related to the following point of the governance: > Potential Council Members are nominated by existing Council members and voted upon by the existing Council after asking if the potential Member is interested and willing to serve in that capacity. This sounded for many as a selective private club. I would like to see if we can experiment with asking the community to select members. For example on a 6 month basis, ask for an anonymous (?) proposal of someone who they think have an non-negligible impact on promoting helping with Jupyter. One other point that I have heard a few time is that despite recognizing that the member of the council are extremely valuable to the project, the nomination process and the 1 year of involvement looks a lot like a reward for seniority ; not that it is, but I can completely see the reasoning from a quick glance at the process. The SageMath project does apparently have a specific distinction for long standing member. I would like to consider this as an option as well as it would clearly distinguish long-term technical and regular involvement from actually being part of the governance. I can also completely see people that would be happy to get a distinctions for being a long standing member, without wanting to be part of the governance. Thanks

Jason

···

On Mon, Aug 29, 2016 at 9:23 PM Matthias Bussonnier < bussonniermatthias at gmail.com> wrote:

Hi all,

To extend on what Jason said, the discussion have started privately on
the Jupyter Steering council mailing list, we'll move it to a public
space but we want to shorten what have been posted and make sure it's
suitable for public consumption.

--
M

On Mon, Aug 29, 2016 at 6:00 PM, Jason Grout <jason at jasongrout.org> wrote:
> We're about to have some discussions in Jupyter about our governance
model,
> and probably tweak it now that we have more experience with it. While
that
> experience may not transfer to matplotlib's situation, it still might be
> good to see that discussion before making huge changes.
>
> Thanks,
>
> Jason
>
>
> On Mon, Aug 29, 2016 at 11:40 AM Paul Hobson <pmhobson at gmail.com> wrote:
>>
>> I think this is a good idea.
>>
>> On Sat, Aug 27, 2016 at 11:09 AM, Thomas Caswell <tcaswell at gmail.com> > >> wrote:
>>>
>>> Folks,
>>>
>>> Following up on last month's email, are there any comments, for or
>>> against, adopting the Jupyter governance model and the mechanism of
>>> ratifying the adoption?
>>>
>>> Tom
>>>
>>>
>>> On Sun, Jul 31, 2016 at 6:32 PM Thomas Caswell <tcaswell at gmail.com> > >>> wrote:
>>>>
>>>> Folks,
>>>>
>>>> During the sprints at SciPy Mike Droettboom and I started to adapt the
>>>> Jupyter governance documents for matplotlib.
>>>>
>>>> We are doing this in the open, and a pull request of the changes is
at:
>>>>
>>>> Initial adaptation from Jupyter to matplotlib by mdboom · Pull Request #1 · matplotlib/governance · GitHub
>>>>
>>>> To be clear, this is a work in progress and is not final or in force.
>>>>
>>>> We propose the mechanism for ratifying the these documents is to,
after
>>>> input from the community, have the current "matplotlib Executive
Committee"
>>>> (the signers of the FSA with NUMFocus) vote.
>>>>
>>>> Tom
>>>>
>>>> ps A very similar email was sent to the matplotlib-devel list on July
17
>>>
>>>
>>> _______________________________________________
>>> Matplotlib-users mailing list
>>> Matplotlib-users at python.org
>>> Matplotlib-users Info Page
>>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> Matplotlib-devel Info Page
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> Matplotlib-devel Info Page
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-users/attachments/20160831/a68bab23/attachment.html>