Re: [mylyn-pmc] proposed changes to project structure

[David Green <david.green@xxxxxxxxxxx>]

I'm in favour of a more flat structure, however I'd like to understand how this relates to Git repository layout, project plans, builds etc.  

For example, would we be considering moving all sub-projects into a single Git repository?  If so would we be looking at a flat structure there?  There is some benefit to keeping projects with some structure in the Git repos with our current build system since that way (for example) Mylyn Intent can be built easily without also having to build other Mylyn docs projects.

Would the proposed change affect how project plans and release reviews are managed?  One of the goals of the current structure was to minimize overhead of these things.

As for "Projects with overlapping committers should be merged into one", I'm not sure if that makes sense.  What is the motivation?  How would this be affected as committers change over time?

David

On Thu, Nov 7, 2013 at 10:14 AM, Florian Thienel <florian@xxxxxxxxxxxxxxxxxxx> wrote:

Hi,

one of the main reasons for the Vex project to move from WTP to Mylyn was that Mylyn Docs provided a "home" for the topic of documentation. Since Vex is more about writing documents, this seemed to be a better fit for us.

The development of Vex runs mostly independent of the rest of Mylyn, so I don't have any strong feelings about the project structure. But I think the fact that there are some projects bothering with the topic of documentation should be reflected somehow. In contrast to the flattening of Docs into three sub-projects about the same topic, the Task Focused Interface sub-project will merge several topics.

But in general I am a fan of flat sturctures, so *+1* from my side for the elimination of one level.

Regards,

Florian


Am Donnerstag, 07. November 2013 10:05 CET, Steffen Pingel <steffen.pingel@xxxxxxxxxxx> schrieb:

> 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
>  https://bugs.eclipse.org/bugs/show_bug.cgi?id=404270
>
> 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

--
-----------------------------------------------------
<florian.thienel/>
Software - Entwicklung und Beratung
-----------------------------------------------------
       Lindenweg 6    Tel. +49 (0) 95 46 59 42 34
D-96138 Burgebrach    florian@xxxxxxxxxxxxxxxxxxx
           GERMANY    http://www.thienel-software.de
-----------------------------------------------------

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

--

David Green

VP of Architecture, Tasktop

Committer, Eclipse Mylyn

http://tasktop.com 

+1-778-588-6896 ext. 115