As per this page, these are the steps to enter KDE review:
- You can move your project in repo-metadata, see repo-metadata README or file a Sysadmin ticket asking for the move. *(How?)
- See the Sanity Checklist for some of the elements people will review.
- E-mail kde-core-devel and other relevant mailing lists with details of your project and what the expected destination is for the repo.
- Make fixes to issues people bring up or provide explanation why they are not (yet) fixed.
- Wait at least two weeks in kdereview.
- After two months in kdereview the repo should be moved back to playground or moved to unmaintained.
- See KDEReview page for current status of projects (feel free to help maintain this page and push reviews forwards).
We need to send the corresponding emails and ensure the repos comply with the following checklist:
- Have completed (or at least be going through) review in kdereview or Incubator.
- The REUSE Specification - Version 3.0 shall be applied when stating licenses and when adding license files to a project.
- Each source file either must contain SPDX identifiers or license headers to state under which terms the software may be used, modified, and redistributed.
- A Messages.sh file which extracts all the i18n() translations.
- An appinfo.xml or metainfo.xml file with AppStream data AppStream Guidelines.
- A screenshot in product-screenshots.
- Check KDE CI and other CIs such as KDE neon that it compiles successfully.
- Documentation appropriate to the project: API documentation, user documentation (including DocBook or other format documented by the Documentation team).