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.
Difference between revisions of "IoT/M2MIWG/TLP Charter Draft"
(→Scope) |
(→Services) |
||
| Line 47: | Line 47: | ||
* '''Ponte''': xxx | * '''Ponte''': xxx | ||
| − | === Services === | + | === Services and Runtimes === |
The project will initially be structured into the following sub-projects, xxx | The project will initially be structured into the following sub-projects, xxx | ||
Revision as of 04:43, 1 July 2013
This page is currently under construction. Community members are encouraged to maintain the page, and make sure the information is accurate.
In this document, "Eclipse M2M" is used as a temporary name for the top-level project
The following names have been proposed in recent discussions:
- Connecting
- Connect
- Connecto
-
Connected World(probably not a good idea, see http://www.connectedworldmag.com/) - Hono
This charter was developed in accordance with the Eclipse Development Process and outlines the mission, scope, organization, and development process for the Eclipse M2M Top-Level Project. 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 an open source collaborative software development project dedicated to providing extensible, standards-based protocol, runtimes and tools for M2M and the Internet of Things.
- Descriptive name: xxx
- Nickname: xxx
Mission
The mission of the project is to provide:
- Protocols implementations that can easily be consumed by third-party
- Runtimes that abstract the complexity of direct hardware and communication stack manipulation
- Tools that xxx
This document describes the composition and organization of the project, roles and responsibilities of the participants, and development process for the project.
Scope
The scope of Eclipse M2M is as follows:
- Implementation of communication protocols applicable to M2M communications due to their nature (bandwidth efficiency, security, ...)
- Investigation and research related to future protocols
- Implementation of services needed for operating fleets of things (application management, device management, ...)
- Tooling for supporting the development and the operation of such fleets
Protocols
The project will initially be structured into the following sub-projects, xxx
- Paho: xxx
- Ponte: xxx
Services and Runtimes
The project will initially be structured into the following sub-projects, xxx
- Mihini
- Ponte (?)
Tooling
- x
Incubator Projects
The Incubator will focus on new developments that are relevant to the other Eclipse M2M sub-projects, which because of their nature would not be appropriate for direct inclusion in the effected sub-project. This could be because the work is still experimental, will have a longer timeline than can be contained within a single release, has dependencies on external IP that has not yet cleared the Eclipse Foundation IP process, or is simply potentially too destabilizing in nature.
Out of scope
- x
- x