technology.osgi Compendium 2021-10-13
The EMO is using this issue to track this review. Help regarding the process can be found in the Eclipse Foundation Project Handbook.
Project
The following OSGi Compendium specifications are included in this release:
- 1.2 Promises
- 1.2 Common Namespaces
- 1.1 Http Whiteboard
- 1.1 Repository Service
- 1.1 JPA Service
- 1.0 Device Abstraction Layer
- 1.0 Device Abstraction Layer Functions
- 1.0 USB Information Device Category
- 1.0 Resource Monitoring
- 1.0 Network Interface Information Service
- 1.0 REST Management Service
- 1.0 TR069 Connector Service
- 1.0 Service Loader Mediator
- 1.0 Serial Device Service
- 1.0 Asynchronous Service
- 1.0 Device Service EnOcean
- 1.0 Cluster Information
- 1.0 Log Stream Provider Service
- 1.0 Typed Event Service
- 1.0 Feature Service
- 1.0 XML Parser Service
- 1.0 Converter
- 1.0 Push Stream
- 1.0 TR157 Amendment 3 Software Module Guidelines
- 1.0 Residential Device Management Tree
- 1.0 Device Service ZigBee
- 1.0 Coordinator Service
- 1.0 Configurator
- 1.0 JAX-RS Whiteboard
- 1.0 Service Layer API for oneM2M
- 1.0 CDI Integration
- 1.0 Transaction Control Service
- 1.0 Web Applications
- 2.0 Dmt Admin Service
- 1.6 Configuration Admin Service
- 1.5 Declarative Services
- 1.4 Event Admin Service
- 1.4 Metatype Service
- 1.2 Device Service UPnP
- 1.2 Http Service
- 1.1 Preferences Service
- 1.1 Remote Services
- 1.1 User Admin Service
- 1.1 Device Access
- 1.1 Remote Service Admin Service
- 1.0 JNDI Services
- 1.0 Data Service JDBC
- 1.0 JTA Transaction Services
- 1.0 Wire Admin Service
What now?
If you have doubts about the Eclipse Development process, we suggest you read this paragraph of the Eclipse Handbook on Progress and Release Reviews: https://www.eclipse.org/projects/handbook/#release-review
Pre-requisites
Intellectual Property Management
To be completed by the EMO.
-
All project code has copyright and license headers correctly applied. ** EMO will scan the code at their discretion ** -
All distributed third-party content has been vetted by the IP Due Diligence process (i.e., IP Log has been approved)
Open Source Rules of Engagement
To be completed by the PMC in the case of Progress Reviews.
-
PMC approval on the mailing list
General:
-
Project is operating within the mission and scope defined in its top-level project’s charter -
Project is operating within the bounds of its own scope -
Project is operating in an open and transparent manner -
Overall the project is operating according to the Eclipse Development Process.
Things to check:
- Communication channels advertised
- Advertised communication channels used
- Committers are responding to questions
- Committers are responding to issues
- Committers are responding to pull/merge/review requests
Branding and Trademarks
To be completed by the EMO and PMC.
The following applies when the project has a custom website.
To the best of our knowledge:
-
Project content correctly uses Eclipse Foundation trademarks -
Project content (code and documentation) does not violate trademarks owned by other organizations
Things to check:
- Project website uses the project's formal name in first and all prominent references
- Project website includes a trademark attribution statement
- Project website footers contain all necessary elements
Legal Documentation
Required files:
-
License files in all repository roots -
README -
CONTRIBUTING (or equivalent)
Recommended files:
-
NOTICES (or equivalent) -
CODE_OF_CONDUCT -
SECURITY
Required elements:
-
ECA is referenced/described
Recommended elements:
-
Build instructions provided -
Security policy is described
Metadata (PMI)
To be completed by the EMO and PMC.
-
The formal name, e.g. "Eclipse Foo™", is used in the project title -
The formal name including appropriate marks (e.g, "™") is used in the first mention in the text of the project description, and scope -
The project description starts with a single paragraph that can serve as an executive summary -
Source code repository references are up-to-date -
Download links and information are up-to-date