mpl governance

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>

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
http://www.linkedin.com/in/dipugee

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:

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

------------------------------------------------------------------------------
_______________________________________________
Matplotlib-announce mailing list
Matplotlib-announce at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-announce

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

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:

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/20160827/5da83e3c/attachment.html>

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:

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

_______________________________________________
Matplotlib-users mailing list
Matplotlib-users at python.org
https://mail.python.org/mailman/listinfo/matplotlib-users

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

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:

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

_______________________________________________
Matplotlib-users mailing list
Matplotlib-users at python.org <mailto:Matplotlib-users at python.org>
https://mail.python.org/mailman/listinfo/matplotlib-users

_______________________________________________
Matplotlib-users mailing list
Matplotlib-users at python.org
https://mail.python.org/mailman/listinfo/matplotlib-users

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

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:

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

_______________________________________________
Matplotlib-users mailing list
Matplotlib-users at python.org
https://mail.python.org/mailman/listinfo/matplotlib-users

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel

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

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:

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

_______________________________________________
Matplotlib-users mailing list
Matplotlib-users at python.org
https://mail.python.org/mailman/listinfo/matplotlib-users

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel

FYI, here is the (beginning of the) public discussion of the Jupyter
governance model we were talking about:
https://github.com/jupyter/governance/issues/19

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:
>>>>
>>>> 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
>>>
>>>
>>> _______________________________________________
>>> Matplotlib-users mailing list
>>> Matplotlib-users at python.org
>>> https://mail.python.org/mailman/listinfo/matplotlib-users
>>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>

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