That sounds great. Lowering the barrier of entry is always good! One thing that I am working on with the TODO Group is a tool for ensuring compliance to repo rules (like Copyright headers): https://github.com/todogroup/repolinter Might be useful here if we could tie it in somehow.
On Wed, Jun 21, 2017 at 3:47 AM, Daniel Dekany <ddek...@apache.org> wrote: > Currently we strictly require a CLA (by which I mean an ICLA or CCLA) > for any contributions to be accepted, as > http://freemarker.org/contribute.html says. > > This practice was inherited from the pre-ASF times, when without > lawyers available, we tried to be on the safe side. But based on > https://issues.apache.org/jira/browse/LEGAL-156 and > https://wiki.apache.org/couchdb/CommitPolicy and some other mails we > can make things simpler for contributors (not to be confused with > committers). > > So I propose that we say that: > > - People sending contributions with GitHub pull requests need no CLA. > But, before merging, we must check that: > - The mail about the pull request was received to > notificati...@freemarker.incubator.apache.org, so that there's > a record of this even in the ASF infrastructure. > - The files in the pull request has the standard ASF copyright > headers, or no copyright headers in files where that's normally > not present. There's no other conflicting copyright information > included either (like a such LICENSE file). > - People sending in patches as attachment to FreeMarker Jira issues > need no CLA. But, before merging, we must check that: > - It's clear from the wording of the issue that the user wishes to > contribute (as opposed to, for example, just showing an example). > - Copyright headers are in order, just as with GitHub pull request. > > If someone contributes a bigger feature, yet they isn't a committer, > we might still ask a CLA though. But that can be dealt with when such > thing happens. > > -- > Thanks, > Daniel Dekany > -- Trevor Lalish-Menagh about.me/trevmex