Bug 399205

Summary:	Request to use Github as primary repository and bugtracker
Product:	[I don't know] kde	Reporter:	Fredrik Haikarainen <fredrik.haikarainen>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED NOT A BUG
Severity:	wishlist	CC:	fredrik.haikarainen, nate
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Fredrik Haikarainen 2018-09-29 09:47:00 UTC

As the title states. I'm sure this has probably been requested in the past, although I could not find a single issue for it. I think it deserves a place for discussion at least, which is why I open this as an issue.

I request that development of the KDE projects are moved to Github.

MY ARGUMENT
The current system for contributing to KDE can be a real hassle, both in terms of submitting issues as well as contributing patches. Moving development and bugtracking to Github would open up opensource-contributions to a much wider audience, which also includes a lot of skilled and experienced developers. Github has provided a platform that has become the de-facto standard for open-source development. Moving development to Github would greatly benefit both the KDE projects themselves as well as the community in terms of feedback and response on contributions. I believe that a lot of great developers are currently held back by the hassle and steps required to contribute to these projects.

ARGUMENTS AGAINST (AA) and COUNTER-ARGUMENTS (CA)

AA: A lot of tools are tightly integrated into the bugtracking-system and likewise. This makes it unfeasible to work on the Github platform
CA: While a move to the Github Platform would deprecate some tools, I think that many tools could be reworked to fit a new workflow. For example automatic bugtracking could be added to an internal list, that is then manually reviewed before public Github-issues are created.

AA: As an opensource project, it is important for KDE that development can happen only on open-source platforms. Github would break this requirement.
CA: I believe that this stance hurts KDE very much in terms of reaching its full potential. While there is nothing wrong with believing in GNU-like philosophies, I believe that putting much weight in a relatively radical standpoint while making big decisions in a huge project like this, only ends up limiting the project. Opensource doesn't always mean GPL. Sometimes opensource can mean zlib or MIT too, and that can also be beautiful and worth fighting for. Github is a platform that has literally revolutionized how opensource works, for the better, and I think its deserving of a project like KDE. I also believe the the community and the projects deserves better ways for users to contribute.

Feel free to add to the discussion. I would very much appreciate it if this issue would be allowed to exist for some time.

Comment 1 Nate Graham 2018-09-30 23:05:25 UTC

Indeed it has been requested in the past. :) Moving moving Git*Hub* is a nonstarter because GitHub is non-free software. The fact that it's now owned by Microsoft, which is one of our competitors

Comment 2 Nate Graham 2018-09-30 23:10:31 UTC

Whoops, my two-year-old hit the Submit button early while we were playing with a Seven of Nine doll. To continue:

The fact that it's now owned by Microsoft, which is one of our competitors, makes even less likely. It's a non-negotiable.

Git*Lab* is a more likely option, and there is a vocal contingent of KDE contributors who would prefer it. The best way to advance this position would be to become a KDE Contributor yourself and make the case. That case cannot be made here in the bug tracker since bug trackers are for small actionable bugs and feature requests, not for ongoing open-ended discussions. To find a more appropriate venue, please read https://community.kde.org/Get_Involved#Getting_in_touch_and_working_together

Regarding making the contribution process easier, it's one of our active goals. Please see https://phabricator.kde.org/T7116. We would definitely appreciate your input and contributions there!