Become a KDE app member
There are 3 stages in the process of becoming a KDE app member. Projects move into KDE Review when they are ready to make beta or stable releases. The KDE community checks for minimum standards.
Stages in becoming a KDE member
|
- "Candidate" Phase:
- Create a project on KDE GitLab and import the existing code. This can be in a personal space on KDE Invent.
- You might need to ask a sysadmin to import the code.
- "Incubating" Phase:
- During this phase, the sponsor actively works toward getting the project set up.
- "Active" Phase:
- During the Active phase, your project enters Playground. When it is nearing a beta release, it can be moved to KDE Review.
- The project team is assumed and expected to behave like other KDE teams and respect the KDE manifesto.
Create a GitLab project
Back to top
|
The process of becoming a KDE app member
|
| Projects move into KDE Review when they are ready to make beta or stable releases. The KDE community checks for minimum standards. If translations are involved, notify the kde-i18n-doc mailing list.
Steps to become a KDE app member:
- File an issue in your KDE Invent project and label it "KDE Review Request". Paste the requirements list into the issue without checking any items.
- Change the project path in repo-metadata by editing metadata.yaml or file a Sysadmin ticket for the move.
- Email the kde-core-devel and other relevant mailing lists with project details and the expected destination for the repository.
- Make fixes based on feedback or explain why certain issues are not (yet) fixed.
- Wait at least two weeks in KDE Review.
- After two months in KDE Review, the repository should either:
- Be moved back to Playground, or
- Be marked as unmaintained.
Back to top
|
Back to top
