Attract existing FLOSS software projects to KDE and incorporate their members into our community: List of Advantages
Open, NormalPublic

Description

While it is true each project is different, and many will have unique needs, to convince other projects to join KDE, there must be tangible advantages to doing so. In this task we will be brainstorming those advantages so we have a unified set of arguments when we approach other projects.

Please list your ideas in the comments, discuss each of their merits, and we will then draw them up and use them to achieve our goals.

As reference of existing advantages, see:

https://manifesto.kde.org/benefits.html

Being part of the international KDE community conveys certain benefits:

  • To stand on the shoulders of giants
    • Make use of KDE infrastructure for project hosting
    • Benefit from the experience of the KDE sysadmins
    • Get support from the larger community with development, documentation, translation, testing, bug handling, etc.
    • Use opportunities to integrate with a large ecosystem of end-user products
    • Interaction with teams that have common values, leading to the cross-pollination of ideas and innovations
  • Enjoy representation and support by KDE e.V.
    • Participate in Akademy and other KDE events
    • Receive financial and organizational support
    • Know that your trademarks can be secured
    • Know that your licensing wishes can be protected via the Fiduciary Licensing Agreement
  • Increase your visibility through the reputation of the KDE community and KDE promotion tools such as:
    • pushing project announcements to the Dot and employing other KDE promotion channels
    • having your project reachable through a subdomain under kde.org
    • having a #kde-<projectname> IRC channel on the Freenode network
    • using KDE as an umbrella brand to associate with the KDE community for communication on web sites and other channels
paulb created this task.Mar 6 2019, 10:19 PM
paulb triaged this task as Normal priority.
thiagosueto updated the task description. (Show Details)Nov 25 2019, 2:08 PM

For starters, we could elaborate on each specific point shown in the manifesto. Especially these ones:

Make use of KDE infrastructure for project hosting

During first contact with developers, it might be more attractive for them to see that we have file sharing for discussion over share.kde.org, have a gitlab instance over invent.kde.org, currently have (partially?) unified account management with identity.kde.org, an infrastructure for building packages for Windows and Android, etc.

Use opportunities to integrate with a large ecosystem of end-user products

Maybe it should be more clear to the potential incubating project that this does not mean the project cannot have a certain independency, and that it does not necessarily mean it must be a Qt project?

Receive financial and organizational support

Of what kind?

Receive financial and organizational support

Of what kind?

To organise and travel to events, for starters. For merch, for hosting, ...