incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joseph Schaefer <>
Subject Re: Apache project bylaws
Date Thu, 03 Oct 2013 16:51:38 GMT
The definitions are in a glossary somewhere, the more
we denormalize the locations of our common understandings
the harder it will be to maintain sanity over discussions.

Projects don't need to be encouraged to write their own
bylaws, most don't bother and that's proper.  We don't need
to spell every possible decision making process out in detail
because they should have experienced the normal processes during
incubation under competent mentorship.

In other words I agree with Marvin that widespread changes
to documents that have been widely referenced are not a good
idea, no matter what the board happens to think today.  Just
clarify the actual issues before us, e.g. how to vote properly
on personnel issues, and that should entirely suffice. Even Greg
doesn't seem to know what consensus voting means in this context,
so there's surely room for improvement.

On Oct 3, 2013, at 12:44 PM, Alex Harui <> wrote:

> On 10/3/13 8:48 AM, "Joseph Schaefer" <> wrote:
>> Good Lord man all you need to add is a one-sentence
>> statement that personnel votes are consensus votes not
>> procedural (simple majority) votes.
> Hmm. Maybe I'm reaching too far, but my hope was to put in this document a
> definition of consensus and a set of defaults for by-laws so that other
> new projects don't have as much if any work to do in defining their
> project-specific by-laws.
> -Alex
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message