< Policies KDE is a friendly community which hosts hundreds of projects. Any project which follows the KDE manifesto and KDE Vision is welcome to join us. The term "application" is used here to mean any project hosted in KDE Git and includes programming libraries and development tools but not typically infrastructure tools or projects with other end product outputs. Contents 1 playground 2 Incubator 3 kdereview 4 Releasing 5 Unmaintained 6 Translations playground playground is a Git module for projects starting development You will need a Git write account which needs a referral from another KDE contributor, see Get_a_Developer_Account You will need to ask sysadmin to create a module Projects can start in scratch repos without asking for a repo, see Git KDE.org manual Projects can make alpha releases and can put them on download.kde.org unstable Projects can ask for translations for their master branch only Incubator Projects which started life outside of KDE are welcome to join us if you feel our community makes a good fit through the KDE Incubator. A sponsor will guide you through the process and check your project complies with the needs of the KDE community kdereview Projects move into kdereview when they are ready to start making beta or stable releases. It allows for the KDE community to check over for minimum standards. You can move your project in repo-metadata, see repo-metadata README or file a Sysadmin ticket asking for the move 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) Releasing Your project is now active and can make beta or stable releases. Find the best home for your project based on contents and release process wanted. After two weeks in kdereview you can move it in repo-metadata, file a Sysadmin ticket if unsure. These projects should depend only on stable released software or software known it will get a stable release before the project does. It may use unstable or unreleased software only as an optional build dependency. Add your project to automated builds: Update kde-build-metadata to add it to kdesrc-build Ping the sysadmins to help get it added to KDE CI Ping distributions to add it to their builds ([email protected]) KDE Frameworks are programmer libraries They have strict quality requirements Get released monthly Ask on kde-frameworks-devel if you want to be considered for inclusion Version numbers are made by release person, there are no stable branches Plasma is a cross device work environment where trust is put on the users' capacity to best define her own workflow and preferences. It is typically released 3 times a year Projects released as part of Plasma must fit well together and be a useful part of the user's work experience. They would not be useful to users of other desktops. Version numbers and stable branches are made by release person Ask on plasma-devel for consideration of inclusion release service Released typically 3 times a year en-masse Includes a range of libraries, applications and developer tools External version numbers (projects often have their own internal version numbering scheme) and stable branches are made by release person Ask release-team for inclusion Self Released - Many projects take care of their own release process Also called Extragear They can use whatever version number scheme they want and can release in their own timeframe Use releaseme to make releases, see Releasing Software Unmaintained If a project is no longer useful you can move it to unmaintained. It can move here from any stage in the lifecycle. Consider suggesting to KDE Gardening team to maintain it if there are still valid use cases. You can move your project in repo-metadata, see repo-metadata README or file a Sysadmin ticket asking for the move Projects can move back to playground if they are picked up for maintenance again. Translations All projects with user-visible strings must have translations. Whenever moving projects between Git modules or when you make a new stable branch you must tell kde-i18n-doc mailing list to update the translation branches. See i18n wiki pages. Retrieved from "https://community.kde.org/index.php?title=Policies/Application_Lifecycle&oldid=87985" This page was last edited on 6 April 2020, at 16:02. Content is available under Creative Commons License SA 4.0 unless otherwise noted.