Revision as of 10:07, 29 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 charter was developed in accordance with the Eclipse Development Process and outlines the mission, scope, organization, and development process for the Eclipse Internet of Things (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.

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: Eclipse Internet of Things
• Nickname: Eclipse IoT

Mission

The mission of the top-level project is to provide open source technology that will be used to build IoT solutions. It will focus on:

1. Standards and Protocols implementations that can easily be consumed by end solution developers as well as framework developers
2. Frameworks and Services that abstract the complexity of direct hardware, communication and data stack manipulation
3. Tools that facilitate the development of connected systems
4. 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 standards and protocols applicable to IoT communications due to their nature (bandwidth efficiency, security, ...) This will include investigation and research related to future IoT standards and protocols.
• Implementation of low-level services (application management, device management, data management...) needed for enabling and simplifying the connection of systems with each other.
• Implementation of high-level services that enable vertical applications whose primary goal is to connect devices, sensors and actuators.
• Tooling to enable the development and the operation of connected systems. Some of the tooling will be specific to the standards, protocols, frameworks and services but some tooling will also be specific to the requirements of embedded software development, ex (remote debug, deployment, test)
• Provide default builds for popular open hardware platforms
• Providing complete industry-oriented software solutions based on the up the these building blocks

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