Jignesh Patel wrote on 6/1/16 6:42 PM: > Thanks Julian! > > This is very helpful and I’d like to suggest a perhaps having a good > “default” policy in place that all incubators inherit on inception. > They may choose to change the default if needed, but this approach > installs some rail guards in place right away.
I would love to see the IPMC have an easy-to-understand set of default project bylaws/procedures that are offered to each new podling to consider for their use. Not a requirement, but for some projects it would really help to both get started and to have a better edited set of these guidelines (that our projects have probably re-created dozens of times by now). > > As you and Roman have suggested, the Spark guidelines are crisp and a > great start. Perhaps we could (with the permission of the Spark PMC) > generalize that and make that the default for all incubators? I’m > willing to help on that front as we need a crisp policy for > Quickstep. While it's polite to ask, it's not required to get permission - everything is under the Apache license. 8-) It's certainly a good idea to ask, because that might spur more folks to collaborate on a really solid IPMC-suggested version. > Apologies in advance if this suggestion blows against some well > established principle. This is all new and a learning opportunity for > all of us in the recently incubated Quickstep project. No, this is just a good idea long overdue for coordinated action. Obviously, not every podling will use all the guidelines, and occasionally podlings come in from existing communities who might have their own well-understood rules already. The ASF requires a certain set of minimum rules (voting, CLAs, IP provenance, branding, etc.) but beyond that it's up to each group. > Cheers, > Jignesh > > >> On Jun 1, 2016, at 3:03 PM, Julian Hyde <jh...@apache.org> wrote: >> >> A couple of projects I am mentoring have raised very similar questions >> recently: >> * Do contributions via github PRs require a CLA? >> * Do PRs require a JIRA case? >> >> I know the answers to these questions, but I was unable to find them clearly >> documented. All committers, including those in podlings, need to be very >> clear on IP policy. I looked in the Committers’ FAQ[1] and Guide for New >> Committers[2] but neither of them explicitly answered the questions. >> Searching for answers, I found legal JIRAs [3], [4] but we can’t expect all >> committers to find these. I applaud the care and thoughtfulness you used to bring this issue up, and completely agree with you. Nice research too! - Shane >> >> Now, maybe the answer is “Every project must write its own set of committer >> guidelines.” But if so, we as the IPMC should be helping podlings do that. >> >> Julian >> >> [1] http://www.apache.org/dev/committers.html >> <http://www.apache.org/dev/committers.html> >> >> [2] http://www.apache.org/dev/new-committers-guide.html >> <http://www.apache.org/dev/new-committers-guide.html> >> >> [3] https://issues.apache.org/jira/browse/LEGAL-156 >> <https://issues.apache.org/jira/browse/LEGAL-156> >> >> [4] https://issues.apache.org/jira/browse/LEGAL-249 >> <https://issues.apache.org/jira/browse/LEGAL-249> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
