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

I like the proposed changes.

The name of the "Task Focused Interface" project is a weird.  It's really the Context project that provides the focusing, the other projects are all about a task-oriented integration of Agile/ALM systems.  So I think we need a new name for that project.  Some ideas:
1) Platform: This really is the Mylyn platform.  It might be overly confusing with Eclipse Platform.
2) M4: New activity in this project will be directed by the way that we're thinking about M4
3) ALM: The closest we have to an industry standard name for this stuff.  For example, Microsoft divides Visual Studio into IDE stuff and ALM stuff (

Much as I dislike acronyms, I'm leaning towards ALM.


Dr. @mik_kersten, CEO, 
Assistant: jill.charlton@xxxxxxxxxxx, +1-778-588-6896

On 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
>> And maybe we can even revamp the website this time around :).
>> Steffen
>> -- 
>> Steffen Pingel
>> Principal Software Engineer, Eclipse Mylyn
>> Mylyn Tasks Lead
> -- 
> -----------------------------------------------------
> <florian.thienel/>
> Software - Entwicklung und Beratung
> -----------------------------------------------------
>       Lindenweg 6    Tel. +49 (0) 95 46 59 42 34
> D-96138 Burgebrach    florian@xxxxxxxxxxxxxxxxxxx
>           GERMANY
> ----------------------------------------------------- 
> _______________________________________________
> mylyn-pmc mailing list
> mylyn-pmc@xxxxxxxxxxx

Back to the top