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"
< IoT
m (Webmaster.eclipse.org moved page Iot/M2MIWG/TLP Charter Draft to IoT/M2MIWG/TLP Charter Draft) |
(Change M2M to IoT, add "Solutions") |
||
| Line 1: | Line 1: | ||
{{:DocumentationGuidelines/DraftHeader}} | {{:DocumentationGuidelines/DraftHeader}} | ||
| − | {{Note|Naming| In this document, "Eclipse | + | {{Note|Naming| In this document, "Eclipse IoT" is used as a temporary name for the top-level project |
The following names have been proposed in recent discussions: | The following names have been proposed in recent discussions: | ||
| + | * IoT | ||
| + | * M2M | ||
* Connecting | * Connecting | ||
* Connect | * Connect | ||
| Line 9: | Line 11: | ||
* Hono (Connect in Maori) | * Hono (Connect in Maori) | ||
* kupu (talk/speak in Maori) | * kupu (talk/speak in Maori) | ||
| − | |||
}} | }} | ||
| − | + | This charter was developed in accordance with the Eclipse Development Process and outlines the mission, scope, organization, and development process for the Eclipse IoT Top-Level Project. This document extends the [http://www.eclipse.org/projects/dev_process/Eclipse_Standard_TopLevel_Charter_v1.1.php 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 | + | |
= Overview = | = Overview = | ||
| − | + | The '''Eclipse IoT''' Top-Level Project is an open source collaborative software development project dedicated to providing extensible, standards-based protocols, runtimes and tools and solutions for enabling a connected world. | |
| − | The '''Eclipse | + | |
* Descriptive name: xxx | * Descriptive name: xxx | ||
| Line 29: | Line 28: | ||
# '''Runtimes''' that abstract the complexity of direct hardware and communication stack manipulation | # '''Runtimes''' that abstract the complexity of direct hardware and communication stack manipulation | ||
# '''Tools''' that facilitate the development of connected systems | # '''Tools''' that facilitate the development of connected systems | ||
| + | # '''Solutions''' that build ready-to-run solutions based on the other building blocks | ||
This document describes the composition and organization of the project, roles and responsibilities of the participants, and development process for the project. | This document describes the composition and organization of the project, roles and responsibilities of the participants, and development process for the project. | ||
| Line 34: | Line 34: | ||
= Scope = | = Scope = | ||
| − | The scope of '''Eclipse | + | The scope of '''Eclipse IoT''' is as follows: |
| − | * Implementation of communication protocols applicable to | + | * Implementation of communication protocols applicable to IoT communications due to their nature (bandwidth efficiency, security, ...) |
* Investigation and research related to future protocols | * Investigation and research related to future protocols | ||
* Implementation of low-level services (application management, device management, ...) needed for enabling and simplifying the connection of systems with each other, using the aforementioned protocols implementations | * Implementation of low-level services (application management, device management, ...) needed for enabling and simplifying the connection of systems with each other, using the aforementioned protocols implementations | ||
| Line 42: | Line 42: | ||
* Tooling for supporting the use of the aforementioned protocols and services in order to enable the development and the operation of connected systems | * Tooling for supporting the use of the aforementioned protocols and services in order to enable the development and the operation of connected systems | ||
* (Marco) Provide default builds for popular open hardware platforms | * (Marco) Provide default builds for popular open hardware platforms | ||
| + | * Providing complete software solutions based on the up the these building blocks | ||
=== Protocols === | === Protocols === | ||
| Line 54: | Line 55: | ||
* '''Mihini''': Mihini delivers a Linux based runtime enabling application development in programming languages such as Lua and C, and providing services such as Application Management and Device Management. | * '''Mihini''': Mihini delivers a Linux based runtime enabling application development in programming languages such as Lua and C, and providing services such as Application Management and Device Management. | ||
| − | * '''Ponte''' (?): Ponte provides a server runtime for bridging | + | * '''Ponte''' (?): Ponte provides a server runtime for bridging IoT protocols to REST. |
=== Tooling === | === Tooling === | ||
* '''Koneki Target Management''' | * '''Koneki Target Management''' | ||
| + | |||
| + | === Solutions === | ||
| + | |||
| + | * '''Eclipse SmartHome''' | ||
| + | * '''Eclipse SCADA''' | ||
=== Incubator Projects === | === Incubator Projects === | ||
| − | The Incubator will focus on new developments that are relevant to the other '''Eclipse | + | The Incubator will focus on new developments that are relevant to the other '''Eclipse IoT''' 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. |
Note that as per the Eclipse Development Process, existing projects that are ''mature'' and would like to work on exploratory features are highly encouraged to maintain their own Incubator (see [http://www.eclipse.org/projects/dev_process/development_process_2011.php#4_9_Incubators EDP Section 4.9]) | Note that as per the Eclipse Development Process, existing projects that are ''mature'' and would like to work on exploratory features are highly encouraged to maintain their own Incubator (see [http://www.eclipse.org/projects/dev_process/development_process_2011.php#4_9_Incubators EDP Section 4.9]) | ||
Revision as of 09:39, 12 May 2014
Draft Content
This page is currently under construction. Community members are encouraged to maintain the page, and make sure the information is accurate.
This page is currently under construction. Community members are encouraged to maintain the page, and make sure the information is accurate.
Naming
In this document, "Eclipse IoT" is used as a temporary name for the top-level project
In this document, "Eclipse IoT" is used as a temporary name for the top-level project
The following names have been proposed in recent discussions:
- IoT
- M2M
- Connecting
- Connect
- Connecto
-
Connected World(probably not a good idea, see http://www.connectedworldmag.com/) - Hono (Connect in Maori)
- kupu (talk/speak in Maori)
This charter was developed in accordance with the Eclipse Development Process and outlines the mission, scope, organization, and development process for the Eclipse IoT 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 IoT Top-Level Project is an open source collaborative software development project dedicated to providing extensible, standards-based protocols, runtimes and tools and solutions for enabling a connected world.
- Descriptive name: xxx
- Nickname: xxx
Mission
The mission of the project is to provide:
- Protocols implementations that can easily be consumed by end solution developers as well as framework developers
- Runtimes that abstract the complexity of direct hardware and communication stack manipulation
- Tools that facilitate the development of connected systems
- Solutions that build ready-to-run solutions based on the other building blocks
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 IoT is as follows:
- Implementation of communication protocols applicable to IoT communications due to their nature (bandwidth efficiency, security, ...)
- Investigation and research related to future protocols
- Implementation of low-level services (application management, device management, ...) needed for enabling and simplifying the connection of systems with each other, using the aforementioned protocols implementations
- Implementation of high-level services that enable vertical applications whose primary goal is to connect things
- Tooling for supporting the use of the aforementioned protocols and services in order to enable the development and the operation of connected systems
- (Marco) Provide default builds for popular open hardware platforms
- Providing complete software solutions based on the up the these building blocks
Protocols
The project will initially be structured into the following sub-projects:
- Paho: Paho delivers reference implementations for the MQTT protocol
Services and Runtimes
The project will initially be structured into the following sub-projects, xxx
- Mihini: Mihini delivers a Linux based runtime enabling application development in programming languages such as Lua and C, and providing services such as Application Management and Device Management.
- Ponte (?): Ponte provides a server runtime for bridging IoT protocols to REST.
Tooling
- Koneki Target Management
Solutions
- Eclipse SmartHome
- Eclipse SCADA
Incubator Projects
The Incubator will focus on new developments that are relevant to the other Eclipse IoT 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.
Note that as per the Eclipse Development Process, existing projects that are mature and would like to work on exploratory features are highly encouraged to maintain their own Incubator (see EDP Section 4.9)
Out of scope
- TBD