Hi Gilles,
Gilles wrote: > On Sat, 18 Jun 2016 11:00:34 -0700, Ted Dunning wrote: >> On Sat, Jun 18, 2016 at 4:29 AM, Gilles [snip] >> You can never go home. No project stays the same. > > Well, some people in CM for years did their best to avoid change. > I didn't like that view and argue with them because they were > important contributors to CM. > > I still have to argue, but now with non-contributors. > *This* makes no sense. [snip] >> This was your assertion in the long email thread. It seemed that >> there was >> significant counter-positions. > > By non-contributors, using arguments that do not fit the CM history. Since this is now the second time in two weeks that you indirectly state that I should keep my mouth, I simply refer here a mail of Phil in January 2015 on the PMC list about the "PMC member responsibilities". As such a Commons PMC member you are responsible for *all* of the components, all its users and the health of the ecosystem these components live. You seem to care currently for 20% of the code of one component only ignoring any impact on the ecosystem your action with the other 80% may have. >>> I'm OK to go through the incubator to do that; but I don't see that >>> it >>> is an easier path. Surely it looks longer. And it seems that even >>> the >>> incubator people doubt that it will lead anywhere. >>> >> >> The incubator is for building community and adapting to Apache. If >> you >> don't have a seed community, then incubator is the wrong place. You >> need to >> have more than just you. > > That's fair, but there are a few others; that was mentioned. Right. And therefore incubation is a good way to build an own community for this one component only (although it is big). >>> Given the uncertain outcome, going through the incubator would be an >>> attempt at rethinking the development of the currently unsupported >>> code. See e.g. >>> https://issues.apache.org/jira/browse/MATH-172 >>> [Or is that out of scope for an incubation proposal?] >> >> >> Incubator is not a place to rethink code. It is primarily for >> building >> community. > > I thought so. > So, that leaves us with TLP. Back to square one. Just because the way *you* like to act with CM is no option for a Commons component. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
