I'd like to see the proposal discuss the alternatives to becoming a Struts subproject. A good role for a proposal is to summarize various threads. Becoming a subproject seems to be a foregone conclusion of the proposal, with no discussion of the alternatives.
In previous threads, Jakarta was mentioned, but not so much the Jakarta Commons. Why is it that we are not proposing to move Tiles to the Commons, as we did with the Validator, and others? Also, Tiles might be able to become a TLP by resolution of the board. The situation is not much different than Shale. The incubator is charged with "acceptance and oversight of new products submitted or proposed to become part of the Foundation". Tiles is already part of the foundation. Speaking of the Incubator, we might also note that Incubator podlings do have releases. Even without quantifying it as a "release", given the usual release plan, Tiles could still create a tagged test-build. Before deciding whether Tiles should be a subproject or not, I think I'd like to see the volunteers create a test-build that could be a release if the PMC gave the nod. Moving a code branch out the sandbox is a trivial task. What's not trivial is doing everything that's needed to turn a snapshot into a potential release. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
