matplotlib-devel Mailing List for matplotlib

I couldn't put an exact date on when John began matplotlib, but its 
sourceforge repository was registered in June of 2003. Python 2.2 was 
the latest version available. Microsoft Windows XP was on the shelves, 
Mac OS X was new to the scene, and Linux had yet to be made easy by the 
likes of Ubuntu and Fedora. Facebook, Twitter and the smartphone 
weren't yet available. And the idea of richly interactive and 
productive applications running in the cloud was still considered 
crazy. A decade is a long time for an open source project, and it's a 
testament to John's hard work and keen decision-making that matplotlib 
has thrived for so long and grown into such a large community of smart 
and talented users and developers. Bravo, John.
To remain relevant in its second decade, matplotlib is being pulled 
simultaneously in two directions. On the one hand, to handle larger and 
more complex data, it needs to get closer to the hardware to make better 
use of GPUs and multicore CPUs. On the other hand, it needs to become a 
first-class member of the most important GUI of our time, the web 
browser, and to do so without sacrificing any of the power and 
flexibility it gets from being a Python library. Challenging stuff, but 
not unattainable given the enormous brain trust we've got here.
Procedurally, one thing I've been feeling rather acutely lately is that 
the firehose of github issues is not always the best way to track larger 
changes. I'd like to propose that we set up an informal system of 
"Matplotlib Enhancement Proposals" (MEPs) to manage larger changes to 
matplotlib that might cut across a number of different subsystems. 
Numpy puts these in their source code repository, but we may just want 
to use the github wiki to make it even easier for non-developers to 
contribute ideas. I'm not envisioning anything super formal here -- 
just something to keep track of the larger goals that won't get lost 
among hundreds of smaller issues. Details can be discussed here (I'd 
love suggestions from other projects) and I'll set something up soon. 
I'm sure we all have our own pet projects we'd like to do "time willing" 
and I look forward to discussing and making headway on some of those.
And back to the immediate future: we've got a release to get out: the 
first release to support Python 3.x. Exciting times. Details to follow 
in another e-mail thread.
John, thanks again for the honor and I hope I can follow your example of 
leadership. They are big shoes to fill.
Mike
On 08/02/2012 05:25 PM, John Hunter wrote:
> It is a great honor for me to announce that Michael Droettboom has
> agreed to take on the role of lead developer of matplotlib. Since
> Michael joined the project in 2007, he has been responsible for much
> of the code that brought matplotlib from being an excellent tool to a
> world class one. No one in the world understands the code from the
> inside out like he does, and many of his contributions, while often
> unseen at the surface, have laid the foundation for matplotlib to
> reach further into the wild and wonderful things it can now do.
>
> To name a few of his contributions: generic, optimized caching
> transformations; dramatic backend simplification and rationalization;
> countless optimizations; implementation of Knuth mathtex layouts;
> python3 support, and dolphins! I like to tell people Michael codes
> with the force of ten men, and he's an incredible asset to our team.
>
> My role has been significantly diminished of late -- although I have
> been the nominal lead developer, in practice I have been a release
> manager. Unfortunately, I need to take some time to focus on family
> health issues, but will continue to follow development and make
> contributions as I can. We'll be looking for a release manager soon,
> and if you are interested in stepping up, we'll welcome the effort.
> We have a wonderful distributed development team using github pull
> requests, and the line between core developers, project leaders and
> plain-ole contributers is blurry. But I think it helps to have
> someone thinking about the project as a whole, who is willing and able
> to make decisions when necessary, and no one is better suited to doing
> this than Michael.
>
> I also extend my heartfelt thanks to Perry Greenfield and STScI. They
> have been supporting matplotlib since 2004 with ideas, code and
> developer resources. They employ Michael currently, and are part of
> the reason why he is able to take on the leadership of this large
> project.
>
> Michael, many thanks.
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

John, I wish all the best you and your family. You have been the hub
of a truly brilliant project for which I can only see its userbase
continuing to expand.
Mike, your appointment is thoroughly deserved and I look forward to
continuing to work closely with you and the rest of the matplotlib
team. Congrats!
Phil
On 2 August 2012 23:06, Benjamin Root <ben...@ou...> wrote:
>
>
> On Thursday, August 2, 2012, John Hunter wrote:
>>
>> It is a great honor for me to announce that Michael Droettboom has
>> agreed to take on the role of lead developer of matplotlib. Since
>> Michael joined the project in 2007, he has been responsible for much
>> of the code that brought matplotlib from being an excellent tool to a
>> world class one. No one in the world understands the code from the
>> inside out like he does, and many of his contributions, while often
>> unseen at the surface, have laid the foundation for matplotlib to
>> reach further into the wild and wonderful things it can now do.
>>
>> To name a few of his contributions: generic, optimized caching
>> transformations; dramatic backend simplification and rationalization;
>> countless optimizations; implementation of Knuth mathtex layouts;
>> python3 support, and dolphins! I like to tell people Michael codes
>> with the force of ten men, and he's an incredible asset to our team.
>>
>> My role has been significantly diminished of late -- although I have
>> been the nominal lead developer, in practice I have been a release
>> manager. Unfortunately, I need to take some time to focus on family
>> health issues, but will continue to follow development and make
>> contributions as I can. We'll be looking for a release manager soon,
>> and if you are interested in stepping up, we'll welcome the effort.
>> We have a wonderful distributed development team using github pull
>> requests, and the line between core developers, project leaders and
>> plain-ole contributers is blurry. But I think it helps to have
>> someone thinking about the project as a whole, who is willing and able
>> to make decisions when necessary, and no one is better suited to doing
>> this than Michael.
>>
>> I also extend my heartfelt thanks to Perry Greenfield and STScI. They
>> have been supporting matplotlib since 2004 with ideas, code and
>> developer resources. They employ Michael currently, and are part of
>> the reason why he is able to take on the leadership of this large
>> project.
>>
>> Michael, many thanks.
>
>
>
> Congrats, Michael!
>
> Ben Root
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On Thursday, August 2, 2012, John Hunter wrote:
> It is a great honor for me to announce that Michael Droettboom has
> agreed to take on the role of lead developer of matplotlib. Since
> Michael joined the project in 2007, he has been responsible for much
> of the code that brought matplotlib from being an excellent tool to a
> world class one. No one in the world understands the code from the
> inside out like he does, and many of his contributions, while often
> unseen at the surface, have laid the foundation for matplotlib to
> reach further into the wild and wonderful things it can now do.
>
> To name a few of his contributions: generic, optimized caching
> transformations; dramatic backend simplification and rationalization;
> countless optimizations; implementation of Knuth mathtex layouts;
> python3 support, and dolphins! I like to tell people Michael codes
> with the force of ten men, and he's an incredible asset to our team.
>
> My role has been significantly diminished of late -- although I have
> been the nominal lead developer, in practice I have been a release
> manager. Unfortunately, I need to take some time to focus on family
> health issues, but will continue to follow development and make
> contributions as I can. We'll be looking for a release manager soon,
> and if you are interested in stepping up, we'll welcome the effort.
> We have a wonderful distributed development team using github pull
> requests, and the line between core developers, project leaders and
> plain-ole contributers is blurry. But I think it helps to have
> someone thinking about the project as a whole, who is willing and able
> to make decisions when necessary, and no one is better suited to doing
> this than Michael.
>
> I also extend my heartfelt thanks to Perry Greenfield and STScI. They
> have been supporting matplotlib since 2004 with ideas, code and
> developer resources. They employ Michael currently, and are part of
> the reason why he is able to take on the leadership of this large
> project.
>
> Michael, many thanks.
>
Congrats, Michael!
Ben Root

It is a great honor for me to announce that Michael Droettboom has
agreed to take on the role of lead developer of matplotlib. Since
Michael joined the project in 2007, he has been responsible for much
of the code that brought matplotlib from being an excellent tool to a
world class one. No one in the world understands the code from the
inside out like he does, and many of his contributions, while often
unseen at the surface, have laid the foundation for matplotlib to
reach further into the wild and wonderful things it can now do.
To name a few of his contributions: generic, optimized caching
transformations; dramatic backend simplification and rationalization;
countless optimizations; implementation of Knuth mathtex layouts;
python3 support, and dolphins! I like to tell people Michael codes
with the force of ten men, and he's an incredible asset to our team.
My role has been significantly diminished of late -- although I have
been the nominal lead developer, in practice I have been a release
manager. Unfortunately, I need to take some time to focus on family
health issues, but will continue to follow development and make
contributions as I can. We'll be looking for a release manager soon,
and if you are interested in stepping up, we'll welcome the effort.
We have a wonderful distributed development team using github pull
requests, and the line between core developers, project leaders and
plain-ole contributers is blurry. But I think it helps to have
someone thinking about the project as a whole, who is willing and able
to make decisions when necessary, and no one is better suited to doing
this than Michael.
I also extend my heartfelt thanks to Perry Greenfield and STScI. They
have been supporting matplotlib since 2004 with ideas, code and
developer resources. They employ Michael currently, and are part of
the reason why he is able to take on the leadership of this large
project.
Michael, many thanks.

I will also try to look at the GL backend again.
One of the main difficulty I see is to handle GPU memory properly. For example, to draw a line collection (using OpenGL) I first build a vertex buffer that is sent to the GPU and then offset/translate/rotate can be done locally/globally very efficiently without rebuilding the vertex buffer. In the template backend however, the "draw_path" function receives a path to be rendered and I need to ensure it is build only once and only applying transforms for subsequent calls. Also, Mike explained the overall situation very well (last year on this mailing list) regarding backend performances.
As for NumFOCUS, what kind of support do you expect ?
Nicolas
On Aug 1, 2012, at 16:15 , Benjamin Root wrote:
> 
> 
> On Wed, Aug 1, 2012 at 6:44 AM, Nicolas Rougier <Nic...@in...> wrote:
> 
> 
> Thanks. Apart from the speed, an OpenGL backend could be also useful for the ipython notebook using webgl (but I'm a total newbie at webgl).
> 
> Nicolas
> 
> 
> Nicolas,
> 
> It is great to see that you have made some progress with glumpy! It is my hope that after the effort I have been making to refactorng the Axes class that I would then move on to studying glumpy to see how to bring that work into matplotlib. It is certainly will not be trivial. I like the idea of making it into a GSoC project. Maybe we can get NumFOCUS to support that effort?
> 
> Cheers!
> Ben Root
>