extra-enforcer-rules is just there for a number of use cases: * Rules that have non-ASLv2 compatible licenses * Rules that are somewhat experimental (such rules should not be put in the "default" package) until they are considered developed well enough to migrate to enforcer-rules * Rules being developed by people who have not got a Maven project commit bit *yet* but would like to demonstrate that they deserve one after getting the *easier to get* codehaus mojo commit bit. (Mojo's commit bit is got by standing up and asking... the devs then vote and there you go... Maven's commit bit is got by demonstrating to the PMC that you are "worthy" and then the PMC deciding to invite you... different members of the PMC have different views on what counts as "worthy" - which is the way it should be ;-) )
On 28 May 2014 21:19, Mirko Friedenhagen <[email protected]> wrote: > Hello everybody, > > there is an outstanding MENFORCER-193[0] request for a new standard > rule, which will allow to ban repositories. What is your opinion about > adding new standard rules in enforcer vs. adding to Mojo's > extra-enforcer-rules? > > Regards Mirko > [0] https://jira.codehaus.org/browse/MENFORCER-193 > -- > http://illegalstateexception.blogspot.com/ > https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) > https://bitbucket.org/mfriedenhagen/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
