Difference between revisions of "Talk:MDT/Papyrus-Proposal"

From Eclipsepedia

Jump to: navigation, search
Line 7: Line 7:
  
 
* [Kenn] : I’ll take a closer look at the proposal soon, but in the meantime note that we need to more consistently use “component” instead of “project”, and that we should identify one lead for this component (instead of two or three).
 
* [Kenn] : I’ll take a closer look at the proposal soon, but in the meantime note that we need to more consistently use “component” instead of “project”, and that we should identify one lead for this component (instead of two or three).
 +
 +
* [raphaël] : in fact we need 5 components and two levels.
 +
Papyrus is the UML tool and the final deliverable for UML end users (higl level component with a dedicated roadmap)
 +
Papyrus is composed of several lower-level components (each of them having a roadmap):
 +
  a) backbone (the diagram container) with an API to integrate diagrams into,
 +
  b) MTD diagram adaptor : a layer on top of MDT diagrams to make them conform to the backbone API
 +
  c) other UML diagrams outside of MDT : contributions of other diagrams that will be developed directly in Papyrus Eclipse component
 +
  d) facilities (EMFCompare, outline, properties...) : all things to integrate to have full-featured tool
 +
  e) XMIDI reference implementation, with import and export commands.

Revision as of 09:33, 21 April 2008

  • Precise the content of the initial contribution
  • Refine the component architecture
  • Choose an organization and a leader: a kind of PMC + one leader ? Due to the relative investment of the developers (to be detailed ?), I suggest to choose Sébastien to lead the component, with the other candidates in this committee.
  • Detail the planning
  • Change "project" into "component"


  • [Kenn] : I’ll take a closer look at the proposal soon, but in the meantime note that we need to more consistently use “component” instead of “project”, and that we should identify one lead for this component (instead of two or three).
  • [raphaël] : in fact we need 5 components and two levels.

Papyrus is the UML tool and the final deliverable for UML end users (higl level component with a dedicated roadmap) Papyrus is composed of several lower-level components (each of them having a roadmap):

 a) backbone (the diagram container) with an API to integrate diagrams into, 
 b) MTD diagram adaptor : a layer on top of MDT diagrams to make them conform to the backbone API
 c) other UML diagrams outside of MDT : contributions of other diagrams that will be developed directly in Papyrus Eclipse component
 d) facilities (EMFCompare, outline, properties...) : all things to integrate to have full-featured tool
 e) XMIDI reference implementation, with import and export commands.