Actually, Martin, I read that too a while ago, and I can't regard it as anything else but just a viewpoint expressed by someone who is reacting to a posting of someone else....
Such an expression neither makes it a policy of the ASF, nor justifies why the board, when voting on a podling wishing graduating to TLP, keep something going on that is considered by some as disgusting or as adding no value by others. If it were as simple as some regard this aspect of doing the right thing, then a simple vote would solve it (for the time being) and both board and Incubator could adjust their procedures and instructions to all accordingly. Best regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Mon, Jul 6, 2015 at 5:52 PM, Marvin Humphrey <mar...@rectangular.com> wrote: > On Mon, Jul 6, 2015 at 12:51 AM, Branko Čibej <br...@apache.org> wrote: > > > I find myself disgusted by this widespread assumption that each project > > needs its own bylaws. WTF for? Are not ASF policies and practices enough > > for everyone? What sort of bylaws could you possibly invent that are > > both a useful extension of these policies and practices /and/ are not > > applicable to other projects? > > Here's the historical rationale for per-project bylaws, which explains > why it's in the TLP resolution template: > > http://s.apache.org/why-project-bylaws > > Apache doesn't have a single set of project bylaws/guidelines because > we want projects to be self-governing... > > Speaking with the benefit of hindsight not available to those who > blazed the trail, my assessment is that while the idea of making > projects think about governance is laudable, drafting bylaws is too > difficult a problem to be tackled by each new TLP. Minute drafting > errors cause large problems. > > Marvin Humphrey >
