[Numpy-discussion] Numpy governance update

Benjamin Root ben.root@ou....
Thu Feb 16 14:28:34 CST 2012


On Thu, Feb 16, 2012 at 2:13 PM, Nathaniel Smith <njs@pobox.com> wrote:

> On Thu, Feb 16, 2012 at 5:17 PM, Travis Vaught <travis@vaught.net> wrote:
> > On Feb 16, 2012, at 10:56 AM, Nathaniel Smith wrote:
> >
> >> Travis's proposal is that we go from a large number of self-selecting
> >> people putting in little bits of time to a small number of designated
> >> people putting in lots of time.
> >
> >
> > That's not what Travis, or anyone else, proposed.
>
> Maybe I was unclear -- all I mean here is that if we suddenly have a
> few people working full-time on numpy (as Travis proposed), then that
> will cause two things:
>  -- a massive increase in the total number of person-hours going into numpy
>  -- a smaller group of people will be responsible for a much larger
> proportion of those person-hours
> (and this is leaving aside the other ways that it can be difficult for
> full-time developers and volunteers to interact -- the volunteers
> aren't in the office, the full-timers may not have the patience to
> wait for a long email-paced conversation before making a decision,
> etc.)
>
> I think Travis' proposal is potentially a great thing, but it's not as
> simple as just saying "hey we hired some people now our software will
> be better". Ask Fred Brooks ;-)
>
> -- Nathaniel
>

Just a thought I had.

>From the perspective of any company, they do not want to devote developer
resources to an open-source project if the features are going to get
rejected (either by the core-devs or by community backlash).  Maybe the
governance structure could be more along the lines of an advise/consent
process for NEPs.  This way, a company puts together a plan of action for
some features and submits it to the central body (however that is
defined).  Comments and revisions are done.  Finally, if the plan is
approved, the company can feel confident that their efforts and resources
won't get rejected after committing to the changes.

Small changes and bugfixes are not effected by this.  Large changes need
planning and commentary anyway.  This allows some official representation
of the community to have some sort of light-handed control over the vision
of the project.

Ben Root
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20120216/c59e4c04/attachment.html 


More information about the NumPy-Discussion mailing list