Attract existing FLOSS software projects to KDE and incorporate their members into our community: Convince Design/Creativity Applications to join KDE
Open, Needs TriagePublic

Description

In this task we will work on designing and implementing a strategy that will help convince independent FLOSS design/creativity-related projects to become part of KDE.

The three projects we initially would like to target are:

  • Scribus, an application used for layout and publishing
  • Natron, a node-based post-production and VFX application similar to Nuke
  • Enve, a fledgling 2D vector-based animation application

Steps

  • Develop (brainstorm) convincing arguments to relay to the people working on these projects (started in T10577 -- maybe brainstorm more specific stuff for each project)
  • Develop in detail what we want to achieve by having these projects join KDE
  • Find contacts within these projects we can talk to, preferably people we already have a relationship with
  • Approach contacts and relay our goals and the reasons why it would be advantageous for their projects
  • Invite projects to a meeting with people from design/creativity-centric projects already part of KDE (Kdenlive, Krita, ...), maybe by having a "Kreativity" track at Akademy or working together at a sprint
  • Hand over the rest of the task to the people in charge of inducting projects into KDE

Rationale

The are several reasons to carry out this task. The most obvious is that it directly addresses Promo's "Help attract existing FLOSS software projects to KDE and incorporate their members into our community" goal, but it also addresses many other of Promo's goals as explained below:

  • By adding these projects to KDE, we also increase the number of developers from different backgrounds and expertises to the Community.
  • The number of KDE users would increase as the userbase for each project will be added to that of KDE.
  • The collaboration between these projects will increase the usefulness of each project individually, by, for example, helping implement compatibility between their native file formats, allowing Scribus to open native Krita images into a layout, Enve files to be opened in Krita, Natron files in Kdenlive, etc..
  • Further coordination between these projects can help increase the userbase for all of them (a la Adobe Creative Suite), as it would be an attractive suite for media artists and companies.
  • It would reinforce's KDE's brand.
paulb updated the task description. (Show Details)Mar 10 2020, 12:17 PM

Possible immediate advantage for Scribus: @afarid mentioned Scribus uses Transifex. If I understand this right, this is proprietary subscription-based service. By joining KDE, Scribus could take advantage of our already existing translated corpus plus translator teams for more specific stuff

By what I can see, all could do with better documentation. The e.V. is investing in this area and all three projects could take advantage of this investment.

I think this would be interesting for everybody working on the "All about the Applications" goal also.

Some information for enve:

Positive points:

  • Enve is very young project and doesn't have yet an translations infrastucture set, so it would be easy for them to adopt the KDE localizations infra.
  • Enve use github but it is easy to migrate to gitlab
  • Enve could need some help with their website and promotion, something that the KDE web and promo team can help with

Negative points

  • Enve use github issue for bug tracking, KDE use Bugzilla for this. Using gitlab for bug tracking is very controversial in the community.
  • Enve use qmake for building the project, KDE use cmake. Either we migrate Enve to cmake or we agree that this is not a problem.
  • Enve use travis for the CI, we could replace it with Jenkins but we can't build AppImages yet with it.

Some information for Scribus:

Positive points

  • Scribus is slowy migrating to gitlab so then their migration is done it shouldn't be difficult to migrate to KDE gitlab
  • Scribus is using Transifex (proprietary software) and with using the kde infra they could move to Free Software for their translations
  • They use CMake to build their project
  • We have a contact point: @thiagosueto

Negative points

  • They plan to use gitlab issues for bugtracking. Very controversiol in the KDE community
  • They still use SVN for the development
tymond added a subscriber: tymond.Mar 10 2020, 5:36 PM
  • Enve use travis for the CI, we could replace it with Jenkins but we can't build AppImages yet with it.

Krita uses Jenkins to build appimages for both nightlies (both stable and from master) and for all releases and beta versions: https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/ - I don't know technical details though.

rodlie added a subscriber: rodlie.Mar 27 2020, 3:12 PM
paulb added a comment.Jul 25 2020, 9:59 AM

From discussion on Promo group, some advantages for joining KDE:

  • Subsidised travel to events
  • Free "advertising agency/copywriting service"
  • Translators
  • Instant community (which leads to...)
  • ... Evangelists
  • Season of KDE/GSoC: Students willing to work on jobs that otherwise would probably be put off indefinitely
  • Other developers willing to contribute to your projects

There are additional ones listed here: https://manifesto.kde.org/benefits.html

There are additional ones listed here: https://manifesto.kde.org/benefits.html

We should definitely update this page: some of the information is outdated or missing (e.g. service provided include Matrix, NextCloud (with LibreOffice online), gitlab, ...).

vkrause added a subscriber: vkrause.Sep 6 2020, 6:59 AM

What's the status of this engagement, has anyone from the KDE e.V. reached out to these developers?

paulb added a comment.Mar 14 2021, 1:47 AM

More like "projects", not necessarily developers, as many have teams with people that do different things. Some we are talking to. But this is a delicate topic. Often we have to find how to approach project maintainers to reach a mutually beneficial outcome. It is slow work.