Following up today’s call, here is what we propose as the final naming of the framework projects and their common acronyms:
* Tasks: CM, QM, TM, …
* Contexts: TFI
* Versions: SCM, CVS, DVCS, DRCS, RCS
* Builds: CI, BM
* Reviews: QM, QA
* Docs: …
* Commons: …
If you have any feedback, please yell now or forever hold your peace, as we plan on initiating the provisioning shortly.
Dr. Mik Kersten
Tasktop CEO, Mylyn Lead
From: mylyn-dev-bounces@xxxxxxxxxxx [mailto:mylyn-dev-bounces@xxxxxxxxxxx] On Behalf Of Steffen Pingel
Sent: September-23-10 1:15 PM
To: Mylyn developer discussions
Subject: [mylyn-dev] Project restructuring progress
we made good progress on today's call on how to proceed with the provisioning of the Mylyn sub-projects. To summarize, I suggested to reconsider creating sub-sub-projects for reference implementations and instead manage them in their parent framework projects. Essentially this is what we outlined in the original restructuring proposal: http://wiki.eclipse.org/Mylyn/Restructuring .
It lowers overhead by reducing the number of projects and still leaves the option to split out components into separate projects as needed in the future. Committers would potentially end up with commit rights on a larger number of bundles but we have successfully used social conventions in the past to manage write access.
The next step is to finalize the naming of the sub-projects before we can go ahead and move CVS directories and Bugzilla bugs to their new locations.
Everyone, please feel free to chime in if you have any thoughts on the proposed structure.