[IPython-dev] Feature and scope creep in IPython

Brian Granger ellisonbg at gmail.com
Wed Jan 9 14:12:50 EST 2013


Over the last few weeks, a few of us on the core dev team have been
having conversations about the increased development activity that the
Sloan foundation money will bring to the project.  In case you haven't
noticed, we are already bursting at the seams with pull requests and
GitHub issues.  This raises the question of how on earth will we
manage all the *additional* activity.  I stared to write an email to
this list about these issues, but the email grew into two blog posts
about the general question: how do open source projects decide which
features to implement?

Here are the blog posts:


I think this issue is really important for the project to consider if
we are going to successfully scale our efforts.  Please read this,
think about it, and post your thoughts here, as it related to IPython.
 At a practical level, we need to figure out better work flow for our
GitHub issues, especially ones for new features.  I propose one option
in my blog post, but I am sure there are others.



Brian E. Granger
Cal Poly State University, San Luis Obispo
bgranger at calpoly.edu and ellisonbg at gmail.com

More information about the IPython-dev mailing list