Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "IoT/M2MIWG/TLP Charter Draft"
Line 2: | Line 2: | ||
Note: "Eclipse M2M" is used as a temporary name for this top-level project | Note: "Eclipse M2M" is used as a temporary name for this top-level project | ||
− | |||
− | |||
This charter was developed in accordance with the Eclipse Development Process and outlines the mission, scope, organization, and development process for the Eclipse Runtime Project (RT). This document extends the Eclipse Standard Top-Level Charter v1.1, and includes the required content and overrides which follow. It is anticipated that as the standard charter is updated, this charter will incorporate the changes and make adjustments as seen fit by the PMC, and with approval from the EMO and board of directors. | This charter was developed in accordance with the Eclipse Development Process and outlines the mission, scope, organization, and development process for the Eclipse Runtime Project (RT). This document extends the Eclipse Standard Top-Level Charter v1.1, and includes the required content and overrides which follow. It is anticipated that as the standard charter is updated, this charter will incorporate the changes and make adjustments as seen fit by the PMC, and with approval from the EMO and board of directors. |
Revision as of 13:17, 28 June 2013
Note: "Eclipse M2M" is used as a temporary name for this top-level project
This charter was developed in accordance with the Eclipse Development Process and outlines the mission, scope, organization, and development process for the Eclipse Runtime Project (RT). This document extends the Eclipse Standard Top-Level Charter v1.1, and includes the required content and overrides which follow. It is anticipated that as the standard charter is updated, this charter will incorporate the changes and make adjustments as seen fit by the PMC, and with approval from the EMO and board of directors.
Contents
Overview
The Eclipse M2M Top-Level Project is xxx.
- Descriptive name: xxx
- Nickname: xxx
Mission
The mission of the project is to provide:
- x
- y
- z
This document describes the composition and organization of the project, roles and responsibilities of the participants, and development process for the project.
Scope
- x
- y
- z
Protocols Projects
The project will initially be structured into the following sub-projects, xxx
- Paho: xxx
- Ponte: xxx
- Incubator - New development in areas that are relevant to the other sub-projects.
Embedded runtimes Projects
xxx
Incubator Projects
The M2M Incubator will focus on xxx