The section that was added below has nothing to do with the rest of the document. It should be reverted, as it is basically nonsense as Jason has just pointed out.
Maven has lots of other problems. This really doesn't seem like one anyone should be spending any time or energy on. Stephen On 25 July 2013 14:16, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > There are two schools of thought amongst the current members of this > projects PMC. > > Without wanting to deliberately tip my hand and reveal where my opinion is, > we would like to solicit the opinions if the community that we serve. > > Please give us your thoughts. > > The topic is essentially: > > Do you want the members of the Maven PMC to be social leaders of the Maven > community, who's actions demonstrate the best community behaviour? > > The alternative is that members of the Maven PMC are here purely to > complete the legal requirements that an Apache TLP has delegated to PMCs > > This is not black and white... The answer can be grey... And everyone is > human so can make mistakes... > > So community, what are you expecting? > > - Stephen Connolly > > On Thursday, 25 July 2013, wrote: > >> Author: jdcasey >> Date: Wed Jul 24 23:21:58 2013 >> New Revision: 1506778 >> >> URL: http://svn.apache.org/r1506778 >> Log: >> Adding section on PMC standards of community commitment >> >> Modified: >> maven/site/trunk/content/markdown/project-roles.md >> >> Modified: maven/site/trunk/content/markdown/project-roles.md >> URL: >> http://svn.apache.org/viewvc/maven/site/trunk/content/markdown/project-roles.md?rev=1506778&r1=1506777&r2=1506778&view=diff >> >> ============================================================================== >> --- maven/site/trunk/content/markdown/project-roles.md (original) >> +++ maven/site/trunk/content/markdown/project-roles.md Wed Jul 24 >> 23:21:58 2013 >> @@ -176,6 +176,29 @@ The Project Management Committee has the >> * Voting on release artifacts. >> * <!-- TODO: get the rest of these --> >> >> +#### Standards for Community Commitment >> + >> +In the spirit of supporting the health of our community, Project >> +Management Committee members refrain from actions that subvert the >> +functioning of the committee itself. >> + >> +First, Project Management Committee members should not maintain >> long-running >> +forks of Maven code outside of the project itself. Making significant >> +changes to Maven code outside of the project displays a lack of >> +investment in the community. Additionally, attempting to re-integrate >> +a large number of code changes in bulk overwhelms the ability of >> +volunteers in the community to review (and potentially veto) the >> +changes. This effectively thwarts the policing function of the >> +PMC. >> + >> +Second, Project Management Committee members should not divert >> +work on redesigning, reimplementing, or improving Maven code to >> +alternative projects outside of this community for the purposes of >> +reintroducing them as replacement for existing Maven code. While there >> +is a danger here of falling into a Not Invented Here mentality, new >> projects >> +created by Maven PMC members strictly to replace Maven code should not be >> +allowed. >> + >> ### [Project Management Chair]( >> http://www.apache.org/foundation/how-it-works.html#pmc-chair) >> >> For various legal reasons, there are certain things that the Apache >> >> >> > > -- > Sent from my phone --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
