Incubator: Difference between revisions

From KDE Community Wiki
No edit summary
mNo edit summary
Line 8: Line 8:
* Support (forums staff, promotion)
* Support (forums staff, promotion)
* Translations
* Translations
* Rest of the community aware of the coming projects (likely a ML)
* Rest of the community aware of the coming projects (likely a mailing list)
* GSoC/GCI slots
* GSoC/GCI slots
* KDE Trademark
* KDE Trademark
* Be invited to events
* Be invited to events


What we require from a successfuly integrated project
What we require from a successfully integrated project
* Culture
* Culture
** Complies to the [http://manifesto.kde.org manifesto]
** Complies with the [http://manifesto.kde.org manifesto]
** Governance similar to the other KDE projects
** Governance similar to the other KDE projects
** Healthy team (metrics needed)
** Healthy team (metrics needed)
Line 24: Line 24:
*** Clear product vision
*** Clear product vision
*** Visited/contributed to other related projects
*** Visited/contributed to other related projects
*** Uses english for code and communication
*** Uses English for code and communication
* Domains/trademarks transferred to KDE e.V. (?)
* Domains/trademarks transferred to KDE e.V. (?)
* Be present at events
* Be present at events

Revision as of 21:16, 30 December 2013

Welcome to the home page of the KDE Incubator. Here you can find our incubation process and the list of currently incubated projects.

The incubator is not active yet and still needs some work to be functional. You can also find the notes which led to the current process.

What do we provide to a project which got through the joining process?

  • FLA availability
  • Infrastructure (repos, ml, forums) (use 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

  • Culture
    • Complies with the manifesto
    • Governance similar to the other KDE projects
    • Healthy team (metrics needed)
      • Bus number
      • Volunteer/paid proportions
      • Community issues (on-going? regularly?)
      • Learn how to teach/mentor
      • Clear product vision
      • Visited/contributed to other related projects
      • Uses English for code and communication
  • Domains/trademarks transferred to KDE e.V. (?)
  • Be present at events