On Mon, Aug 17, 2015 at 7:05 PM, John Layt <[email protected]> wrote: > On 17 August 2015 at 07:54, Jos Poortvliet <[email protected]> wrote: > >> I'd say the main benefit of Github is that it makes it easy for the many >> developers used to it to do a pull request - effectively widening our >> potential contributor base. Some might send in one or two minor pull >> requests, not being interested in becoming regular contributors, others might >> be convinced, after a few patches, to join KDE and then get on our >> infrastructure. >> >> Why make people first join a mailing list and/or go through other hoops >> before we allow them to help make KDE better? >> >> Of course, you can leave it up to individual sub projects if they're >> interested in more contributions or not. > > I'll address this separately while I decide if the main topic is a > good thing or not. Given how hard it is to just build a KDE app or > Framework, and the efforts potential contributors have to go to just > to get a working build, then I think making them go through the normal > submission channels is the least of our worries. If they were by some > miracle able to build something and create a patch, then it's really > not much harder to create and upload a patch to Bugzilla or > Reviewboard (we could script it). I'm hoping Phabricator solves this > by allowing a push like Gerrit does? is so then even easier then...
Please see https://secure.phabricator.com/T8092 for more information on the future of this. > > We need to solve the build problem first. > > John. Regards, Ben > _______________________________________________ > kde-community mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/kde-community _______________________________________________ kde-community mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-community
