Differences between revisions 1 and 2
Revision 1 as of 2014-01-23 16:54:03
Size: 2764
Editor: EwaJodlowska
Comment:
Revision 2 as of 2014-01-23 16:55:37
Size: 2813
Editor: EwaJodlowska
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from BylawsWG/Agenda_Jan_24

Bylaws WG Agenda for January 24, 2014

Adding a Reporting Rule to the Bylaws

Given the recent discussions on the members list, I think we *do* have to add a reporting rule to the bylaws to address the communication problems, so I think that we should add this wording back into the bylaws WG section. Proposed by M.A.L.

Transitioning Associate Members

Apart from the WG policy change request below, I think we also need to think about how to transition the existing associate members into the new model. The natural choice would be the "Supporting Member" class, but we do need to formalize this in some way, by getting their written consent. Some may prefer to turn their membership into the basic membership or apply for managing/contributing member status. Proposed by M.A.L.

Higher Mem Levels Inheriting Membership Rights

We need to add wording that all higher membership levels also inherit the basic membership rights, e.g. the ability to attend meetings. Proposed by M.A.L.

Section 4.2

Section 4.2: ... voting privileges revoked pursuant to Section 4.11. This needs to be fixed to read "Section 4.12". We should do a final review of the section references before going final. Proposed by M.A.L.

Rewording Section 4.8

All, I took a glance at the draft PSF bylaws, and I found myself slightly confused about some of the material in Section 4.8 (Contributing Members). That section reads as follows: > To be eligible for membership as a Contributing Member […] such person must > commit to spending at least five hours per month working on projects relating > to the creation or maintenance of open source software available to the > public at no charge." This section seems extraordinarily broad. On my initial read I expected that this section applied only to those who contribute to the nebulous set of projects I'd call "core Python projects": python-core itself, pip, etc. However, not only does that section not say that, it doesn't even seem to require that the open-source project in question be written-in or related to Python. I wanted to know whether this section was actually intended to be that broad, or if there was a plan to restrict the scope of that section. Proposed by Cory Benfield

Section 4.9

Section 4.9: ... Fellowship does not continue during any extension of life by non-natural means, such as zombification or vampirism. ...Should we leave this in ? Proposed by M.A.L.

Committing Section 5.9

Forgot a check-in from the discussions we had about section 5.9 in out conf call last week: the section still reads "one (1) or more directors", but we agreed to have this read "three (1) or more directors". Proposed by M.A.L.

BylawsWG/BylawsAgenda (last edited 2014-01-24 16:11:03 by MarcAndreLemburg)

Unable to view page? See the FrontPage for instructions.