On 09/19/2015 04:04 PM, Vishesh Handa wrote: > This is the part of your email I really like. Though this is not what > you meant: If projectX choose to also use Github, it is not affecting > your project in anyway. Just ignore it and move on.
You keep reiterating this, but it's simply not true: * Disagreement on whether to use GitHub or not can extend into the sub-community around a given project and cause strife there. * Some of our project sub-communities have many maintainers for smaller sub-projects that comprise the larger project, and these sub-projects need to collaborate for consistency. The topology of 'project' is not a match to our repository topology, which is incidental and an implementation detail. It's not possible to cleanly turn GitHub on or off along the - ever-shifting - social boundaries involved. * Different per-project tooling definitely creates pressures on projects to provide the same tooling as other projects. We've got practical experiences with this from our trial runs with gerrit and Phabricator. * 'Common ownership' in the Manifesto is a core value that e.g. begats shared workflows like our shared developer account application process and our shared repository access model. This stuff is important. It's hard to main- tain the idea of common ownership if we create barriers for people moving within the project by fragmenting our core workflows. If someone doesn't want to work with Git- Hub they're barred from stepping up and maintaining project X that's using GitHub by a previous maintainer's decision, unless they do the work to reverse that decision, which can get us back to the first bullet. Cheers, Eike _______________________________________________ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community