Chris has seen more of these sorts of things than any of the other participants in this discussion.
His experience here is very valuable. On Thu, Aug 16, 2012 at 1:11 PM, Mattmann, Chris A (388J) < chris.a.mattm...@jpl.nasa.gov> wrote: > > Not sure that's the case, eg I think we all want to keep yarn in the > > same code repository, allow patches that update it along with other > > hadoop subprojects, co-design it with MR, test/release it together as > > well. That's not a sign of a distinct community. > > Keeping code in the same repository with a PMC with different sets of > permissions in that repository *is* the sign of a distinct community. > Doesn't matter if you want the code there together, and allowing patches, > and testing and releasing and whatever. Those are technical issues. > Having code with *different* rules for *the same* community members > is not what I know as "community over code" and the Apache way. > And ultimately it's the reason why this email thread won't die. There's > an elephant in the room here (pun intended). >
