Open Stack

On Fri, Mar 16, 2012 at 10:55 AM, Jim Jagielski <jimjag at gmail.com> wrote:

> >
> >
> > There are a lot of different ways to contribute to a big project like
> this.
> > Over at the PSF we have found it very useful to have a separate
> foundation
> > and board made up of people from the community who have an interest in
> > supporting the general python community in ways that go beyond writing
> code.
> > The skills (and interests) needed to organize events such as hack days,
> > meetups, and conferences and especially deal with subjects like copyright
> > and trademark enforcement do not overlap 100% with the skills (and
> > interests) of the core developers. The PSF, and its board, provide a
> focus
> > for soliciting and receiving contributions of all sorts from *everyone*
> in
> > the Python community. I would expect the OpenStack Foundation to serve a
> > similar purpose in this community.
> >
> > Doug
> >
>
> As I recall, the bylaws of the Python Foundation were heavily based on
> those from the ASF, but with an eye on allowing corporations as
> "members"...
>

I wasn't involved at the time, but I believe that is correct. For
reference, the current bylaws are available at
http://www.python.org/psf/bylaws/

The tl;dr version: "nominated" members are individuals selected by existing
members and may vote on PSF business, including selecting board members.
"sponsor" members pay to support the foundation and among the benefits they
receive is a single member vote. The PSF has no say over what the
python-dev team does with Python itself, except to the degree that there is
some overlap in membership.


> But what is crucial with TPF is that the board is derived from the
> community and the members... the control and direction still is
> derived from the community.
>

I agree 100%. The technical direction should be set by contributors, and
the foundation and board should support the implementation effort.

Doug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/foundation/attachments/20120316/a6a0a5f1/attachment-0003.html>