Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Budget/2017
Phase 1
The PolarSys steering committee selected the following Core Services which are mandatory for PolarSys in 2017:
- EMO and executive support
- Infrastructure: PolarSys IT support, LTS membership
- Marketing: marketing materials, Rover demo, PolarSys website
- Conferences: INCOSE, Euroforum
Phase 2
In this phase, each PolarSys member expresses his preferences to allocate the budget.
2.1. Each PolarSys member allocates a percentage between activities and each IC. Example: 40% for the activities, 30% for the two IC => 100% allocated.
2.2. Each PolarSys member sets the priority between the list of activities proposed by the steering committee. A member has 10 points to distribute between 3 activities. Example 1: Activity 1 = 3 points, Activity 2 = 7 points. Example 2: Activity 1 = 10 points.
The activities are the following:
- Establish product management infrastructure and services based on Tuleap
- Experimentation with a student show the integration between the PolarSys tools based on the Rover project (e.g., integration between Capella and Papyrus)
- Establish Polarsys release train to build products like in Eclipse with the Eclipse release train
- Evolutions for RCPTT
- Evolutions for SWTBOT (SWT native dialogs, SWTBot scenario generation)
Between 11/04/2017 and 18/04/2017, the PolarSys members express their allocation in this document.
Phase 3
The PolarSys Steering Committee finalizes the PolarSys budget.