2018 activities

From Wiki
Jump to: navigation, search

Polarsys Members can propose activities they would like to propose as activities for 2018.

Each year: Selection of funded activities will be operated during budget allocation per Steering Committee and each member choices.

During the year: TBD a light process to vote about activities (by SC only, by all members? / with one vote per person or with a number of token?)

You can provide small activities (bug fixing, small feature requests) or large activities (new projects or set of features).

Template:

NAME OF ACTIVITY

  • Name of relevant objectives: [NAME AND URL of relevant goals]
  • Description:
  • Work to do:
  • Why is it relevant for Polarsys:
  • Which projects and solutions could be interested:
  • Bugs:


EMF maintenance

  • Name of relevant objectives: Insure a mid term support of Polarsys solutions
  • Description: Contract is at a fixed price. Funding should be used for bugs and questions from any users of EMF, but requests from Polarsys member should be answered with a higher priority.
  • Work to do: fix bugs, animation on newsgroup, bugzilla, gerrit for EMF Core and EMF Services.
  • Why is it relevant for Polarsys: EMF is the core of a large part of Polarsys projects. So, it is critical to insure a good maintenance and vitality of EMF.
  • Which projects and solutions could be interested: papyrus, safety architect, capella, papyrus rt, etc.
  • Bugs:

EMF improvements

  • Name of relevant objectives: Make some improvements in existing common frameworks
  • Description: Funding should be used only for bugs from Polarsys member. Contract is workload based, with a tracking of spent days for each bug.
  • Work to do: improvements and new features for EMF Core and EMF Services.
  • Why is it relevant for Polarsys: EMF is the core of a large part of Polarsys projects. So, it is critical to insure a good
  • Which projects and solutions could be interested: papyrus, safety architect, capella, papyrus rt, etc.
  • Bugs:

Create a configurable modern Activity Explorer

  • Name of relevant objectives: Create a modeling stack of frameworks for cloud and web modeling
  • Description: The goal is to refactore the existing Activity Explorer to be easily customizable by engineers without dev skills and to rely on web technologies.
  • Work to do: Create a web based front end, Create a JSON/Java bridge, Create a configuration environment, Create a Java server engine, Create bridge to several tools (Sirius, Papyrus, M2T, M2M, Validation, ...)
  • Why is it relevant for Polarsys: it will provide a way for Polarsys members to describe their engineering process at the solution level and at the enterprise level. For end users, it will help them to follow a process and activities across several tools. It will dramatically improve the ramp up for new users and help them to use a guidance to respect a high quality process. The configurability will improve the autonomous of engineers to adapt it to their own methodology.
  • Which projects and solutions could be interested: as it is at the methodological level, it is not dedicated to one project. It could be relevant to Capella, Papyrus UML, Papyrus SysML, Safety Architect
  • Bugs:


EMF.ts

  • Name of relevant objectives: Create a modeling stack of frameworks for cloud and web modeling
  • Description: Create a TypeScript native implementation of EMF. TypeScript better fits our expectation than Javascript as it is strongly typed.
  • Work to do: create a native implementation (not with GWT, but with all native specific pattern) of EMF core and reflective framework
  • Why is it relevant for Polarsys: EMF is the core of a large part of Polarsys projects. So, it is the first piece of work to do to go the web.
  • Which projects and solutions could be interested: papyrus, safety architect, capella, papyrus rt, etc.
  • Bugs:

CDO maintenance

  • Name of relevant objectives: Insure a mid term support of Polarsys solutions
  • Description: Contract is at a fixed price. Funding should be used for bugs and questions from any users of CDO, but requests from Polarsys member should be answered with a higher priority.
  • Work to do: fix bugs, animation on newsgroup, bugzilla, gerrit for CDO.
  • Why is it relevant for Polarsys: CDO fits expectation for several Polarsys members to deploy on large teams
  • Which projects and solutions could be interested: papyrus, safety architect, capella, papyrus rt, etc.
  • Bugs:

Provide a rich text widget in JFace or Nebula

  • Name of relevant objectives: Make some improvements in existing common frameworks
  • Description: Several tools need rich text editing for SWT and several have to re-implement it as it is not provide out of the shelf by Eclipse Platform
  • Work to do: select an existing implementation, move it to JFace (or Nebula), improve its quality
  • Why is it relevant for Polarsys: it help to merge initiatives
  • Which projects and solutions could be interested: kit alpha, ?
  • Bugs: