Hi, On Thu, Jun 28, 2012 at 3:20 PM, Fernando Perez <fperez....@gmail.com> wrote: > On Thu, Jun 28, 2012 at 3:03 PM, Matthew Brett <matthew.br...@gmail.com> > wrote: >> Fernando - you told me a week or so ago that you'd come across a blog >> post or similar advocating a single list - do you remember the >> reference? > > Found it after some digging: > > http://www.kitware.com/blog/home/post/263 > > and upon rereading it, it doesn't really advocate anything specific > about mailing lists, just talking in general about a project > considering all of its constituents as a single community, rather than > two groups. > > And in that view, one can even argue that a single community can still > benefit from multiple lists, much like the python developers have > agreed to have python-dev and python-ideas as a way of triaging > exploratory discussions form day-to-day work.
I'm not on the python mailing lists, but my impression is that python is in a different space from numpy. I mean, I have the impression (I may be wrong) that python already has a clear idea about how work gets done and how decisions are made. There's a mature PEP process and clear precedent for the process of working through difficult decisions. Numpy lacks this, and more fundamentally, does not appear to be sure to what extent it is a community project in the sense that I've understood it from other projects around us - like - say - IPython, sympy, and so on. So, it may not make sense to think in terms of a model that works for Python, or even, IPython. See you, Matthew _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
