Difference between revisions of "IoT/M2MIWG/TLP Charter Draft"

From Eclipsepedia

< IoT
Jump to: navigation, search
(Overview)
(Incubator Projects)
(24 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{:DocumentationGuidelines/DraftHeader}}  
 
{{:DocumentationGuidelines/DraftHeader}}  
  
{{Note|Naming| In this document, "Eclipse M2M" is used as a temporary name for this top-level project
+
{{Note|Naming| 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  
+
The following names have been proposed in recent discussions:
 
* Connecting
 
* Connecting
 
* Connect
 
* Connect
 
* Connecto
 
* Connecto
 
* <s>Connected World</s> (probably not a good idea, see http://www.connectedworldmag.com/)
 
* <s>Connected World</s> (probably not a good idea, see http://www.connectedworldmag.com/)
* Hono
+
* Hono (Connect in Maori)
 +
* kupu (talk/speak in Maori)
 +
* IoT
 
}}
 
}}
  
Line 16: Line 18:
  
  
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.
+
The '''Eclipse M2M''' Top-Level Project is an open source collaborative software development project dedicated to providing extensible, standards-based protocols, runtimes and tools for enabling a connected world.
  
 
* Descriptive name: xxx
 
* Descriptive name: xxx
Line 24: Line 26:
  
 
The mission of the project is to provide:
 
The mission of the project is to provide:
# x
+
# '''Protocols''' implementations that can easily be consumed by end solution developers as well as framework developers
# y
+
# '''Runtimes''' that abstract the complexity of direct hardware and communication stack manipulation
# z
+
# '''Tools''' that facilitate the development of connected systems
  
 
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 32: Line 34:
 
= Scope =
 
= Scope =
  
* x
+
The scope of '''Eclipse M2M''' is as follows:
* y
+
* z
+
  
==== Protocols ====
+
* Implementation of communication protocols applicable to M2M 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
  
The project will initially be structured into the following sub-projects, xxx
+
=== Protocols ===
  
* '''Paho''': xxx
+
The project will initially be structured into the following sub-projects:
* '''Ponte''': xxx
+
* '''Incubator''' - New development in areas that are relevant to the other sub-projects.
+
  
==== Embedded runtimes ====
+
* '''Paho''': Paho delivers reference implementations for the MQTT protocol
 +
 
 +
=== 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
  
* '''Mihini'''
+
* '''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 M2M protocols to REST.
 +
 
 +
=== Tooling ===
 +
 
 +
* '''Koneki Target Management'''
 +
 
 +
=== 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.
 +
 
 +
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])
  
==== Incubator Projects ====
+
= Out of scope =
  
The M2M Incubator will focus on xxx
+
* TBD

Revision as of 14:31, 2 July 2013

Warning2.png
Draft Content
This page is currently under construction. Community members are encouraged to maintain the page, and make sure the information is accurate.


Note.png
Naming
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 (Connect in Maori)
  • kupu (talk/speak in Maori)
  • IoT


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 protocols, runtimes and tools for enabling a connected world.

  • Descriptive name: xxx
  • Nickname: xxx

Mission

The mission of the project is to provide:

  1. Protocols implementations that can easily be consumed by end solution developers as well as framework developers
  2. Runtimes that abstract the complexity of direct hardware and communication stack manipulation
  3. Tools that facilitate the development of connected systems

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 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

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 M2M protocols to REST.

Tooling

  • Koneki Target Management

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.

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