Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-pmc] proposed changes to project structure
Hi All,

Just because Mylyn Intent becomes a project under the top-level project doesn’t mean it’s dependency on Wikitext has to be removed. A project structure at Eclipse is not intended to follow the actual dependency tree of any single project. Otherwise we would see many more complicated structures in other top-level projects. I’ve been part of the RT and Technology PMC and both have a flat structure. It’s easier to maintain long-term. BTW, a lot places already dropped the hierarchy. Thus, no changes would be necessary to the website and forums for VEX and Intent.

As for the aggregation, I highly suggest participating in the release train and using the release train repository. Building and maintaining a separate aggregation repo is a lot effort, not to mentioning the promotion of it within the community. Participating in the release train shares the aggregation and release load onto the shoulders of each project.

-Gunnar

Am 07.11.2013 um 03:12 schrieb Steffen Pingel <steffen.pingel@xxxxxxxxxxx>:

Hi,

my thinking in regard to Mylyn Docs is that it has its own integrator community (such as Intent)  and is used independently of the task-focused interface so that it makes sense to keep it as an independent project. I would even consider reversing dependencies on the code level and moving the 2 bundles in Mylyn Docs that have dependencies on Tasks and Context into TFI to decouple targets, builds etc. but that's a separate discussion.

My initial thought was to leave the Mylyn Docs structure untouched and keep Intent and Vex as sub-sub projects. That would require fewer changes and as you point out makes sense in terms of reflecting dependencies. On the other hand, having a flat structure makes it a bit easier for users to discover Intent (at least in the PMI) and would provide more consistency.

I don't have a strong opinion on whether Mylyn Docs should be restructured. It's decoupled from merging the other sub-projects and we could always do it later if it makes sense and proceed with the creation of the TFI project (which is the key driver).

Great to hear that Intent has plans to mature. I agree that we should revive the discussion around creating a Mylyn repository that aggregates all components under the top-level project.

Does anyone else have thoughts on the structure of Mylyn Docs?

Steffen


On Thu, Nov 7, 2013 at 10:15 AM, Alex Lagarde <alex.lagarde@xxxxxxx> wrote:
Hi Steffen,

sure I understand the fact that you want to regroup the projects that you lead, it makes cense.

However, I do not get, if Mylyn docs remains a top-level component and is not pulled-up in the Task Focus Interface, why should its sub-projects (which are Intent & VEX) be moved out of it ?

According to me, it still makes a lot of cense to have Intent inside Mylyn doc as we strongly rely on Wikitext (and are about to pull up some of Mylyn Intent features inside Wikitext, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=411880 ).

Just my opinion about this, of course I'll be OK with the project structure you propose.

BTW, we want to provide a 1.0 release Mylyn Intent out of incubation for the release after Luna (Luna will embed the latest incubation version of Intent, 0.9). I will contact you to see what are all the requirements to be directly part of Mylyn (should I use the same download area/ update site / builds / Target Platforms...).

Best regards,
Alex

Le 07/11/2013 10:05, Steffen Pingel a écrit :
Hi,

I would like to bring everyone's attention to a proposal posted by Gunnar. We are proposing to flatten the structure of the top-level project by promoting all sub-sub projects to sub-projects and consolidating some of them. We would end up with the following structure under the top-level project:

- Task Focused Interface (unifies Builds, Commons, Context, Reviews, Tasks, and Versions)
- Docs (as it is today)
- Intent (move out of docs)
- VEX (move out of docs)
- Incubator (as it is today)
- Model Focusing Tools (move out of sub-structure, discuss future with committers)
- R4E (move out of sub-structure, discuss future with committers)

Please join the discussion on this task:

 404270: create Mylyn m4 project proposal

And maybe we can even revamp the website this time around :).

Steffen

--
Steffen Pingel
Principal Software Engineer, Eclipse Mylyn
Mylyn Tasks Lead
http://tasktop.com 


_______________________________________________
mylyn-pmc mailing list
mylyn-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylyn-pmc


_______________________________________________
mylyn-pmc mailing list
mylyn-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylyn-pmc




--
Steffen Pingel
Principal Software Engineer, Eclipse Mylyn
Mylyn Tasks Lead
http://tasktop.com
_______________________________________________
mylyn-pmc mailing list
mylyn-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylyn-pmc

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxx







-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx





Back to the top