Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Runtime Top-Level Project Draft Charter"
| Line 1: | Line 1: | ||
The following is a '''draft''' charter for the contemplated runtime top-level project at Eclipse. The content is largely derived from the current Equinox project mission statement and has been expanded somewhat to capture the new work areas appearing and anticipated at Eclipse. | The following is a '''draft''' charter for the contemplated runtime top-level project at Eclipse. The content is largely derived from the current Equinox project mission statement and has been expanded somewhat to capture the new work areas appearing and anticipated at Eclipse. | ||
| − | '''This draft is intended to facilitate discussion. All aspects of the draft may change | + | '''This draft is intended to facilitate discussion. All aspects of the draft may change.''' |
=Draft Charter= | =Draft Charter= | ||
| − | This charter was developed in accordance with the [http://www.eclipse.org/projects/dev_process/proposal-phase.php Eclipse Development Process] and outlines the mission, scope, organization, and development process for the | + | This charter was developed in accordance with the [http://www.eclipse.org/projects/dev_process/proposal-phase.php Eclipse Development Process] and outlines the mission, scope, organization, and development process for the ''(Name TBD)'' 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. |
==Overview== | ==Overview== | ||
| Line 11: | Line 11: | ||
Since the creation of the Eclipse Rich Client Platform (RCP) in 2004, the interest in and use of Eclipse technologies in runtime scenarios has been steadily increasing. Initially, the focus of these runtimes was on desktop or client technologies, but the community has steadily found new and innovative uses for the technologies in areas such as [http://www.eclipse.org/ercp/ devices], [http://www.eclipse.org/rap/ rich internet applications] and [http://www.eclipse.org/equinox/server/ servers]. | Since the creation of the Eclipse Rich Client Platform (RCP) in 2004, the interest in and use of Eclipse technologies in runtime scenarios has been steadily increasing. Initially, the focus of these runtimes was on desktop or client technologies, but the community has steadily found new and innovative uses for the technologies in areas such as [http://www.eclipse.org/ercp/ devices], [http://www.eclipse.org/rap/ rich internet applications] and [http://www.eclipse.org/equinox/server/ servers]. | ||
| − | The Eclipse | + | The Eclipse ''(Name TBD)'' Top-Level Project is an open source collaborative software development project dedicated to providing a generic, extensible, standards-based runtime platform. |
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. | ||
==Mission== | ==Mission== | ||
| − | The | + | The ''(Name TBD)'' Top-Level Project is designed to foster, promote and house runtime efforts in the Eclipse community. These efforts strive towards the common goal of providing a uniform component model across a wide variety of computing environments. OSGi forms the basis of this infrastructure. ''(Name TBD)'' projects support embedded devices, desktops, and enterprise systems as well as clients and servers to provide commonly required infrastructure. It is the goal of ''(Name TBD)'' to provide those intermediate software services which enable applications to be more easily and concisely constructed. |
| − | It is the unique vision of | + | It is the unique vision of ''(Name TBD)'' to support a "tier-less" programming model where developers need not concern themselves with whether their application domain code is run on a device, a client or a server. By developing a consistent architecture, ''(Name TBD)'' effectively eliminates these tiers and enables developers to focus on the business problem at hand and still have many system architecture options available at deployment time. |
==Scope== | ==Scope== | ||
| − | Concretely, | + | Concretely, ''(Name TBD)'' is an implementation of the OSGi core framework specification, a set of bundles that implement various optional OSGi services and a collection of additional bundles that implement other infrastructure for running applications on OSGi-based systems. |
| − | The broad scope of the | + | The broad scope of the ''(Name TBD)'' project is to be a first class OSGi community with a mission to foster the vision of Eclipse as a landscape of bundles. This work includes: |
* Developing and delivering the OSGi framework implementation used for all of Eclipse. | * Developing and delivering the OSGi framework implementation used for all of Eclipse. | ||
| Line 33: | Line 33: | ||
* The implementation of middleware / runtime standards from organizations such as OMG, OASIS, JCP. | * The implementation of middleware / runtime standards from organizations such as OMG, OASIS, JCP. | ||
* Development of non-standard infrastructure deemed to be essential to the running and management of OSGi-based systems. | * Development of non-standard infrastructure deemed to be essential to the running and management of OSGi-based systems. | ||
| − | * Incidental tooling efforts to enable or facilitate particular | + | * Incidental tooling efforts to enable or facilitate particular runtime functions in conjunction with (e.g., as a component of) a sub-project. |
===Out of scope=== | ===Out of scope=== | ||
| − | * Major tooling efforts are | + | * Major tooling efforts are out of scope |
* Industry-specific vertical technologies | * Industry-specific vertical technologies | ||
Revision as of 17:26, 17 December 2007
The following is a draft charter for the contemplated runtime top-level project at Eclipse. The content is largely derived from the current Equinox project mission statement and has been expanded somewhat to capture the new work areas appearing and anticipated at Eclipse.
This draft is intended to facilitate discussion. All aspects of the draft may change.
Draft Charter
This charter was developed in accordance with the Eclipse Development Process and outlines the mission, scope, organization, and development process for the (Name TBD) 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
Since the creation of the Eclipse Rich Client Platform (RCP) in 2004, the interest in and use of Eclipse technologies in runtime scenarios has been steadily increasing. Initially, the focus of these runtimes was on desktop or client technologies, but the community has steadily found new and innovative uses for the technologies in areas such as devices, rich internet applications and servers.
The Eclipse (Name TBD) Top-Level Project is an open source collaborative software development project dedicated to providing a generic, extensible, standards-based runtime platform.
This document describes the composition and organization of the project, roles and responsibilities of the participants, and development process for the project.
Mission
The (Name TBD) Top-Level Project is designed to foster, promote and house runtime efforts in the Eclipse community. These efforts strive towards the common goal of providing a uniform component model across a wide variety of computing environments. OSGi forms the basis of this infrastructure. (Name TBD) projects support embedded devices, desktops, and enterprise systems as well as clients and servers to provide commonly required infrastructure. It is the goal of (Name TBD) to provide those intermediate software services which enable applications to be more easily and concisely constructed.
It is the unique vision of (Name TBD) to support a "tier-less" programming model where developers need not concern themselves with whether their application domain code is run on a device, a client or a server. By developing a consistent architecture, (Name TBD) effectively eliminates these tiers and enables developers to focus on the business problem at hand and still have many system architecture options available at deployment time.
Scope
Concretely, (Name TBD) is an implementation of the OSGi core framework specification, a set of bundles that implement various optional OSGi services and a collection of additional bundles that implement other infrastructure for running applications on OSGi-based systems.
The broad scope of the (Name TBD) project is to be a first class OSGi community with a mission to foster the vision of Eclipse as a landscape of bundles. This work includes:
- Developing and delivering the OSGi framework implementation used for all of Eclipse.
- Implementation of all aspects of the OSGi specification (including but not limited to the EEG, MEG and VEG work).
- Investigation and research related to future versions of OSGi specifications and related runtime issues.
- Implementation of key framework services and extensions needed for running Eclipse (e.g., the Eclipse Adaptor, Extension registry) and deemed generally useful to people using OSGi.
- All implementations must be based on OSGi and run on Equinox.
- The implementation of middleware / runtime standards from organizations such as OMG, OASIS, JCP.
- Development of non-standard infrastructure deemed to be essential to the running and management of OSGi-based systems.
- Incidental tooling efforts to enable or facilitate particular runtime functions in conjunction with (e.g., as a component of) a sub-project.
Out of scope
- Major tooling efforts are out of scope
- Industry-specific vertical technologies