[kde-community] Bikeshedding - our strength apparently *sigh*

Michael Pyne mpyne at kde.org
Sat Sep 19 14:58:09 UTC 2015


On Sat, September 19, 2015 16:42:54 Riccardo Iaconelli wrote:
> If somebody happened to send me some material for WikiToLearn through the
> Facebook page (it has happened), I don't reject it asking him/her to resend
> it to the mailing list, because that would never work. I accept the
> material, thank the person, and point out they can also subscribe to the
> mailing list, if they are interested to keep an eye on it.
> 
> And this is exactly how we got one of our now most important contributors.
> Did I loose my soul or my values? The project just grew stronger.

Is anyone actually arguing this point in the way you ask? No one's asking to 
prevent "one offs" entirely, the core of the issue is that KDE development 
should happen *within* KDE-the-whole-community, not *apart from* KDE.

The way we know best to do this is to prefer the use of the infrastructure we 
as a community have setup for that purpose, and to avoid diluting that 
infrastructure (which has its own positive network effects). If you've ever 
licensed software under a GPL instead of BSD license then you agree with the 
logic, even if you don't realize it's the same here. ;)

Maybe there's a way to integrate pull requests into a KDE community workflow 
that meets the intent of what we're trying to do without subsuming the 
existing workflow completely (Github can't be allowed to subsume the whole 
deal because it's proprietary). But IMHO we're not at a stage where that's 
been clearly described how that could work.

My personal feeling is that opting to go the actual-development-on-Github 
route would simply introduce a schism in development workflow, despite the 
best intentions of any party. And if you think *these* threads are filled with 
bikeshedding, just wait until that break occurs...



More information about the kde-community mailing list