On Thu, Mar 17, 2016 at 2:55 PM, Cody Koeninger <c...@koeninger.org> wrote:
> Why would a PMC vote be necessary on every code deletion? > Certainly PMC votes are not necessary on *every* code deletion. I dont' think there is a very clear rule on when such discussion is warranted, just a soft expectation that committers understand which changes require more discussion before getting merged. I believe the only formal requirement for a PMC vote is when there is a release. But I think as a community we'd much rather deal with these issues ahead of time, rather than having contentious discussions around releases because some are strongly opposed to changes that have already been merged. I'm all for the idea of removing these modules in general (for all of the reasons already mentioned), but it seems that there are important questions about how the new packages get distributed and how they are managed that merit further discussion. I'm somewhat torn on the question of the sub-project vs independent, and how its governed. I think Steve has summarized the tradeoffs very well. I do want to emphasize, though, that if they are entirely external from the ASF, the artifact ids and the package names must change at the very least.
