[IPython-dev] Should I still contribute to IPython ?
Tue Dec 18 10:03:39 CST 2012
On 12/18/12 8:38 AM, Thomas Kluyver wrote:
> On 17 December 2012 20:00, Brian Granger <firstname.lastname@example.org
> <mailto:email@example.com>> wrote:
> * How do we manage communication? Verbal communication is much more
> efficient than emails or even IRC. The 4 people at Berkeley will have
> an incredible advantage in being able to talk daily. We don't want to
> cripple or remove that advantage, but we need to figure out how to
> include other core devs and people from the community. This is
> particularly relevant to myself as I am the only person involved in
> the Sloan work that is not at Berkeley.
> I think this issue - communication - is becoming key. I spent a day away
> from my computer, and came back to >40 new e-mails in my IPython folder
> (in addition to the 20 odd unread that I'm planning to get round to one
> day). That's a mixture of our two mailing lists and the Github
> notification messages. I get the feeling we're approaching a critical
> point, where it's no longer possible for us as individuals to keep up
> with all the discussions going on.
> To my mind, we need to split things up. We already have an informal
> separation of interests - for instance, I leave most of the discussion
> about the notebook front-end to others, but get more involved with
> IPython.core. I think we need to make this a bit (not too much) more
> formal, so that no-one falls down the cracks as everything speeds up.
> This could mean, e.g. more specialised mailing lists, or having a
> consistent process for handling incoming issues.
If Github had a better issue tracker, it'd be much easier. For example,
if you could get notifications for certain labels, and if random people
could add labels (or only add certain types of labels), things would be
I'd suggest not splitting up the project mailing lists, but rather
ignoring emails that appear to touch things you aren't interested in.
Just at the critical time, you don't want to fragment the (still small)
More information about the IPython-dev