> > Bylaws have gone out of fashion and it’s generally recommend that podlings > (and TLP) don’t have them and use the “default”. >
Really? I didn't notice. > As the default is often unclear I've created a default simple set that > graduating projects can use, [1] Legal and board have reviewed this. > That's a good starting point. What I struggle with is that every project works slightly different in things like: Commit-then-review or review-then-commit or whether ReviewBoard needs to be used or patches need to be attached to Jira etc. These rules are often not written down which makes it hard to contribute. This might be a particular pet-peeve of mine because I do - nature of the job - lots of "drive by" contributions but I'd still love a clearly defined set of rules on how we want to operate. This includes - and I don't actually know what works there these days and what doesn't - the Github use. If anyone knows what's allowed and possible it'd be great if you could share. > Thanks, > Justin > > 1. https://wiki.apache.org/incubator/DefaultProjectGuidelines
