Difference between revisions of "Incubator"

Jump to: navigation, search
m
 
(8 intermediate revisions by 6 users not shown)
Line 1: Line 1:
Welcome to the home page of the KDE Incubator. Here you can find our [[Incubator/Incubation Process|incubation process]] and the list of currently [[Incubator/Incubated Projects|incubated projects]].
+
[[File:Mascot konqi-dev-kde.png|thumbnail|right|[[Konqi]] welcomes you to KDE project!]]
 +
Welcome to the home page of the KDE Incubator!
 +
There are many benefits to becoming a KDE project: https://manifesto.kde.org/benefits.html
  
The incubator is not active yet and still needs some work to be functional. You can also find the [[Incubator/Notes|notes]] which led to the current process.
+
[[Incubator/Incubated Projects|List of currently incubated projects]].
  
What do we provide to a project which got through the joining process?
 
* FLA availability
 
* Infrastructure (repos, ml, forums) (use [http://sysadmin.kde.org/tickets/ sysadmin ticket system] to request)
 
* Support (forums staff, promotion)
 
* Translations
 
* Rest of the community aware of the coming projects (likely a mailing list)
 
* GSoC/GCI slots
 
* KDE Trademark
 
* Be invited to events
 
  
What we require from a successfully integrated project
+
== Requirements ==
* Culture
+
* Compliance with the [http://manifesto.kde.org KDE Manifesto]
** Complies with the [http://manifesto.kde.org manifesto]
+
* Governance similar to the other KDE projects
** Governance similar to the other KDE projects
+
* Clear product vision
** Healthy team (metrics needed)
+
* Healthy team (healthy proportion of volunteers, inclusive towards new contributors, ideally more than one developer)
*** Bus number
+
* Uses English for code and communication
*** Volunteer/paid proportions
+
* Continuity agreement must be in place with KDE e.V. for domains and trademarks if the authors disappear
*** Community issues (on-going? regularly?)
+
* Recommended to attend [[Akademy]]
*** Learn how to teach/mentor
+
 
*** Clear product vision
+
 
*** Visited/contributed to other related projects
+
== Process ==
*** Uses English for code and communication
+
=== Candidate ===
* Domains/trademarks transferred to KDE e.V. (?)
+
First, send an email to [email protected] requesting a sponsor. This email must provide a description of the project to be incubated, include a list of the people committing to the project, and have a plan to be in compliance with the [https://manifesto.kde.org/index.html KDE manifesto]. For example, it must be hosted using Free Software tools (e.g. not on Github).
* Be present at events
+
 
 +
=== Incubating ===
 +
During this phase, the sponsor actively works toward getting the project set up by doing the following:
 +
* Make sure the project developers have developer accounts
 +
* Contact sysadmin to get git repos (in the playground area) set up for the developers
 +
* Keep on top of the process to make sure it's going in the right direction and not getting stalled
 +
 
 +
During this phase, the project cannot yet use the KDE brand or have a top level website on kde.org. If project becomes stalled or does not conform to the manifesto, it gets archived (see below).
 +
 
 +
=== Active ===
 +
During the Active phase, the project enters "KDEReview" and follows the process from there (see also [[Policies/Application_Lifecycle|Application Lifecycle]] and [[KDEReview]]. The project team is assumed and expected to behave like other KDE teams and respect the KDE manifesto.
 +
 
 +
=== Stalled & Archived ===
 +
A project is considered stalled when for one year, there is no release, no commits, and no mailing-list activity. Current maintainers are contacted to check what's happening. If there is no activity or no reply from existing maintainers, after a month then a call to new maintainers is done. If a new maintainer shows up he or she gets a six month trial. If after a month no new maintainer showed up, the project gets archived.
 +
 
 +
When a project gets archived, the source repo gets closed, the mailing list disabled, and only last download is available. If someone wants to pick it up, it goes back to the candidate phase.
 +
 
 +
=== Notes ===
 +
Here are [[Incubator/Notes|notes]] which led to the current process.

Latest revision as of 17:55, 9 November 2019

Konqi welcomes you to KDE project!

Welcome to the home page of the KDE Incubator! There are many benefits to becoming a KDE project: https://manifesto.kde.org/benefits.html

List of currently incubated projects.


Requirements

  • Compliance with the KDE Manifesto
  • Governance similar to the other KDE projects
  • Clear product vision
  • Healthy team (healthy proportion of volunteers, inclusive towards new contributors, ideally more than one developer)
  • Uses English for code and communication
  • Continuity agreement must be in place with KDE e.V. for domains and trademarks if the authors disappear
  • Recommended to attend Akademy


Process

Candidate

First, send an email to [email protected] requesting a sponsor. This email must provide a description of the project to be incubated, include a list of the people committing to the project, and have a plan to be in compliance with the KDE manifesto. For example, it must be hosted using Free Software tools (e.g. not on Github).

Incubating

During this phase, the sponsor actively works toward getting the project set up by doing the following:

  • Make sure the project developers have developer accounts
  • Contact sysadmin to get git repos (in the playground area) set up for the developers
  • Keep on top of the process to make sure it's going in the right direction and not getting stalled

During this phase, the project cannot yet use the KDE brand or have a top level website on kde.org. If project becomes stalled or does not conform to the manifesto, it gets archived (see below).

Active

During the Active phase, the project enters "KDEReview" and follows the process from there (see also Application Lifecycle and KDEReview. The project team is assumed and expected to behave like other KDE teams and respect the KDE manifesto.

Stalled & Archived

A project is considered stalled when for one year, there is no release, no commits, and no mailing-list activity. Current maintainers are contacted to check what's happening. If there is no activity or no reply from existing maintainers, after a month then a call to new maintainers is done. If a new maintainer shows up he or she gets a six month trial. If after a month no new maintainer showed up, the project gets archived.

When a project gets archived, the source repo gets closed, the mailing list disabled, and only last download is available. If someone wants to pick it up, it goes back to the candidate phase.

Notes

Here are notes which led to the current process.


This page was last edited on 9 November 2019, at 17:55. Content is available under Creative Commons License SA 4.0 unless otherwise noted.