mtdelgadoa
commented
1 month ago Hello all, the EMO is trying to avoid duplication of release records, so we will be providing our feedback and comments related to this release directly here.
EMO REVIEW CHECKLIST
EDP Review status: EMO Completed - Awaiting ballot results. @Azquelt please consider adding the Security file to your project repository.
EMO review checklist
PMI record: URL
EF Specification Process
- [x] Spec Committee Ballot completed
Intellectual Property Management
- [ ] All project code has copyright and license headers correctly applied. EMO will scan the code at their discretion
- [x] 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
- [x] PMC approval on the mailing list
General:
- [x] Project is operating within the mission and scope defined in its top-level project’s charter
- [x] Project is operating within the bounds of its own scope
- [x] Project is operating in an open and transparent manner
- [x] 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 The following applies when the project has a custom website. To the best of our knowledge:
- [x] Project content correctly uses Eclipse Foundation trademarks
- [x] 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:
- [x] License files in all repository roots
- [x] README
- [x] CONTRIBUTING (or equivalent)
Recommended files:
- [x] NOTICES or equivalent (you can use the Legal Documentation generator available under committer tools)
- [x] CODE_OF_CONDUCT
- [ ] SECURITY
See examples for Security file and Code of Conduct.
Required elements:
- [x] ECA is referenced/described
Recommended elements:
- [x] Build instructions provided
- [ ] Security policy is described
Metadata (PMI)
- [x] The formal name, e.g. "Eclipse Foo™", is used in the project title
- [x] The formal name including appropriate marks (e.g, "™") is used in the first mention in the text of the project description, and scope
- [x] The project description starts with a single paragraph that can serve as an executive summary
- [x] Source code repository references are up-to-date
- [x] Download links and information are up-to-date (see EF handbook for more information on how-to do this)
- [x] Communication channels listed in the PMI (i.e. public mailing list, forums, etc.)
njr-11
Specification issue template
When creating a specification project release review, create an issue in the MicroProfile-WG repository repo with the content defined as follows.
[x] Specification name and version
[x] Add the label
Release Review[x] Naming conventions for artifacts:
[x] The Nexus Staging links (orgeclipsemicroprofile-NNNN where NNNN is the staging repository id) (eg, https://oss.sonatype.org/content/repositories/orgeclipsemicroprofile-NNNN/org/eclipse/microprofile/config/) which contain all the binaries and relevant documentation:
[x] A link in the Eclipse downloads sections is still available for specs and apidocs:
[x] Summary that a Compatible Implementation is complete, passes the TCK, and that the TCK includes sufficient coverage of the specification.
[x] Release Review