|Re: [technology-pmc] Candidates for Termination/Continuation reviews
I find myself wrestling with the purpose of a continuation review.
he purpose of a Continuation Review is to verify that a Proposal or Project continues to be a viable effort and a credit to Eclipse. The Project team will be expected to explain the recent technical progress and to demonstrate sufficient adopter, developer, and user support for the Project. The goal of the Continuation Review is to avoid having inactive projects looking promising but never actually delivering extensible frameworks and exemplary tools to the ecosystem.Asking for a continuation review seems like a pretty obvious thing to do for both projects. Frankly, there's no way that it can happen until Q1 anyway. FWIW, I'd rather work with the projects on this issue than simply tell them what they need to do. I'll plan to discuss this directly with the project leads next week.
Wayne Eric Rizzo wrote:
On Dec 3, 2009, at 3:29 PM, Konstantin Komissarchik wrote:Does the dev process specify the frequency of continuation reviews forincubating projects? If not, it seems to me that it would make sense to wait until after Q1 to take any actions as the situation would resolve or changeby then such that concrete actions could be taken. It seems to me that acontinuation review at this stage would not actually accomplish anything. Wealready know that they are stuck and why they are stuck.That makes way too much sense, Konstantin. :-)Seriously, I think that is a good idea and one that would address the concerns I expressed earlier about m2e.Eric _______________________________________________ technology-pmc mailing list technology-pmc@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/technology-pmc
Back to the top