My $0.02 on this. It's always better to agree on the rules before you start arguing about them. I don't think you need to spend a bunch of time crafting legalese. But having guidelines of how you vote for what is valuable. This is especially true on contentious issues like when (if ever) you can ask dormant members to go emeritus.
Alan. On Nov 19, 2013, at 7:24 AM, Kevin Minder wrote: > I agree that > 1) this should not gate graduation > 2) that we should avoid creating our own legalese > 3) that we should link to something that outlines the guidelines under which > we operate > > On 11/19/13 9:58 AM, larry mccay wrote: >> My understanding is that it isn't required that we have our own by-laws and >> that most projects don't bother. >> It is assumed that you adopt the httpd by-laws (guidelines) in the absence >> of your own. >> If we can avoid crafting, interpreting and discussing our own legalese - I >> think that would be best. >> >> That said - all contributors should be aware of the voting policy in place >> for our project. >> A link to an authoritative definition of it - either in the httpd project >> (or ant for that matter) or to the glossary for definitions of consensus, >> etc would be good to have on our site. >> >> >> On Tue, Nov 19, 2013 at 8:08 AM, Kevin Minder >> <[email protected]>wrote: >> >>> Hi Everyone, >>> Several interesting threads occuring on general@incubator. One of them >>> is about bylaws/voting. We probably need some more documentation like this >>> for graduation. From that thread, I thought the Ant bylaws ( >>> http://ant.apache.org/bylaws.html) were a good example. >>> Kevin. >>> >>> -- >>> CONFIDENTIALITY NOTICE >>> NOTICE: This message is intended for the use of the individual or entity >>> to which it is addressed and may contain information that is confidential, >>> privileged and exempt from disclosure under applicable law. If the reader >>> of this message is not the intended recipient, you are hereby notified that >>> any printing, copying, dissemination, distribution, disclosure or >>> forwarding of this communication is strictly prohibited. If you have >>> received this communication in error, please contact the sender immediately >>> and delete it from your system. Thank You. >>> > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader of > this message is not the intended recipient, you are hereby notified that any > printing, copying, dissemination, distribution, disclosure or forwarding of > this communication is strictly prohibited. If you have received this > communication in error, please contact the sender immediately and delete it > from your system. Thank You. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
