Jump to: navigation, search

IoT/M2MIWG/TLP Charter Draft

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 this top-level project

The following names have been proposed in recent discussions


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.

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:

  1. Protocols implementations that can easily be consumed by third-party
  2. Runtimes that abstract the complexity of direct hardware and communication stack manipulation
  3. 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

  • x
  • y
  • z

Protocols

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

The project will initially be structured into the following sub-projects, xxx

  • Mihini

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.