On Tue, Oct 1, 2013 at 5:28 PM, Ross Gardler <rgard...@opendirective.com> wrote: > +1 to Marvin's "I hope that most projects won't bother" although there > needs to be something a little more than a blank piece of paper. > > The best approach, IMHO, is to simply make it official that the project > adopts the same byelaws as project x, y or z. Pick an established project > that has a minimal set of stable byelaws and go on from there. Some > projects like to refer to the original project pages, others make a local > copy. Both approaches have their advantages.
At Wicket we didn't bother to pick bylaws and from what I have seen in other communities we are better for it. Graduation from the incubator is a testament that the community acts as a meritocracy, and the bylaws of the foundation should be good for all graduated projects. As a community I think that Wicket developers never even bothered to look at the bylaws and just follow the established processes and guidances that trickle down from board@. Looking at httpd, they don't have explicit bylaws either–my google fu did not unearth any document at httpd.apache.org that constitutes bylaws. Martijn --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
