| Hi, Kenn,
Thanks for your prompt input. That has been my understanding, too.
Perhaps the name of this review mechanism is problematic: it should be called the "Please-help-Eclipse-to-decide-what-to-do-with-this-project Review." :-)
I shall work up some slides, then, for termination reviews of these components and send them out for feed-back before asking the EMO to schedule the reviews. These slides will make it clear that there is, in my opinion, sufficient interest to re-boot these components with new committers under new leadership and that this should be the recommended course of action. As I understand it, the interested parties will have an opportunity to collaborate on the new road-map, committer team, and leadership for these components.
Thanks!
Christian
On 12-Mar-09, at 8:50 AM, Kenn Hussey wrote: Christian, The process for “vaulting of individuals into committer positions” IS the Termination Review, AFAIK. To be clear, a Termination Review does not automatically mean the project/component will be terminated/archived; it gives the community the chance to step up and potentially do a reboot. I don’t think we can/should replace all of the committers (only one in this case) with new ones via the usual voting process unless we can justify the new committers based on meritocracy… Cheers, Kenn Hussey
Program Manager, Modeling and Design Solutions From: emf-dev-bounces@xxxxxxxxxxx [mailto:emf-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian W.Damus
Sent: Thursday, March 12, 2009 8:40 AM
To: PMC members mailing list
Cc: MDT OCL mailing list; Eclipse Modelling Framework
Subject: [emf-dev] Re: [mdt-ocl.dev] Transition Plan for MDT OCL and EMF"QTV" Components? Hi, Thanks to Anthony, Cédric, and Bernd for expressing willingness to commit to the continued vitality of these components! It's great to see such support. Just to be clear, again: as I understand it, Termination Review is the only process by which a project's committer team might be changed en masse on events such as this, and the preferred outcome for all stakeholders is always that the project continue under new leadership with a new committer team. If there is another mechanism available, or if the Modeling PMC can direct a transition, please let me know! I prefer a smooth transition of these components into willing and capable hands. For example, if the PMC can approve the vaulting of individuals into committer positions that they would not, under normal circumstances, yet have earned, then that works for me. Kenn? Ed? What is your recommendation as PMC reps for the projects involved? On 11-Mar-09, at 5:30 PM, Christian W. Damus wrote:
Hello, my PMC, As most of you already know, I have been unemployed for some time now. That interval is now coming to an end, to my great relief. However, in my new employment, the job description does not include time to spend on development of the Eclipse Modeling components on which I am currently a committer. Nor would I expect it to, as the work is quite removed from the MDD sphere. I would not be able to contribute as a committer on these components to the standard expected of the Eclipse community, and certainly not my own standard, on my own personal time. Therefore, I shall need to relinquish my committer rights on the MDT OCL component and the EMF Query, Transaction, and Validation components as of next week. The problem is, of course, that I am the only committer on these components. As I understand the Eclipse process, a Project that finds itself without any committers proceeds to Termination Review in the hope that the project can be re-staffed. Is the same true of Components? Can we assume that the rules of the new process (in which these components that are still Components would be Projects) should apply? Please advise. Thanks, Christian _______________________________________________ mdt-ocl.dev mailing list mdt-ocl.dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev _______________________________________________ mdt-ocl.dev mailing list mdt-ocl.dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
|
