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
(Added new name suggestion) |
|||
| (26 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | + | ''' | |
| − | + | The Eclipse IoT Top Level project has been created.''' | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | |||
| − | |||
= Overview = | = Overview = | ||
| + | This charter was developed in accordance with the [https://www.eclipse.org/projects/dev_process/development_process.php Eclipse Development Process] and will outline the mission, scope, organization, and development process for the Eclipse Internet of Things Project. This document extends the [https://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. | ||
| − | + | * Descriptive name: Eclipse Internet of Things | |
| − | + | * Nickname: Eclipse IoT | |
| − | * Descriptive name: | + | |
| − | * Nickname: | + | |
= Mission = | = Mission = | ||
| − | The mission of the project is to provide: | + | The mission of the top-level project is to provide open source technology that will be used to build IoT solutions for industry and consumers. It will focus on: |
| − | # '''Protocols''' implementations that can easily be consumed by end solution developers as well as framework developers | + | # '''Standards and Protocols''' implementations that can easily be consumed by end solution developers as well as framework developers |
| − | # ''' | + | # '''Frameworks and Services''' that abstract the complexity of hardware, communication and data 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 33: | Line 23: | ||
= Scope = | = Scope = | ||
| − | The scope of '''Eclipse | + | 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. It is expected these low-level services will enable cross-domain connectivity between different vertical/industry solutions. For example, the ability to connect vehicles on the road with homes, homes with energy services, energy services with wind mills, wind mills with weather forecast, etc. | ||
| + | * 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 these building blocks | ||
| − | The | + | The projects under this top-level project will be implemented in a variety of programming languages. These projects will also target many different hardware and OS environments that are commonly used in different industries, such as embedded, SCADA, manufacturing, etc. However, all projects will be encourage to ensure their software is available for open hardware (ex. BeagleBone) and easily accessible hardware environments (ex. Raspberry Pi). |
| − | = | + | = Licensing = |
| − | + | Projects under the IoT Top-Level Project are permitted to use one of the following two options: | |
| + | # Eclipse Public License v1.0 | ||
| + | # Eclipse Public License v1.0 and Eclipse Distribution License v1.0 | ||
Latest revision as of 10:54, 21 January 2016
The Eclipse IoT Top Level project has been created.
Contents
Overview
This charter was developed in accordance with the Eclipse Development Process and will outline the mission, scope, organization, and development process for the Eclipse Internet of Things 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.
- 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 for industry and consumers. It will focus on:
- Standards and Protocols implementations that can easily be consumed by end solution developers as well as framework developers
- Frameworks and Services that abstract the complexity of hardware, communication and data 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 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. It is expected these low-level services will enable cross-domain connectivity between different vertical/industry solutions. For example, the ability to connect vehicles on the road with homes, homes with energy services, energy services with wind mills, wind mills with weather forecast, etc.
- 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 these building blocks
The projects under this top-level project will be implemented in a variety of programming languages. These projects will also target many different hardware and OS environments that are commonly used in different industries, such as embedded, SCADA, manufacturing, etc. However, all projects will be encourage to ensure their software is available for open hardware (ex. BeagleBone) and easily accessible hardware environments (ex. Raspberry Pi).
Licensing
Projects under the IoT Top-Level Project are permitted to use one of the following two options:
- Eclipse Public License v1.0
- Eclipse Public License v1.0 and Eclipse Distribution License v1.0