+1 For the needs of Bountysource I am allowing pull requests and GitHub issues. Works well. (we I ser no equivalents of that within kde, btw, I mean easy pay-for-fix and fundraising) If someone pays or sends a fix, it can be via a pigeon or smoke signs, whatever works. :) That said, I make it clear that development is not happening on GitHub.
I am open to switch to repos collected within a 'KDE project' officially. Especially if GitHub promotes us as on of the largest collection of projects... why not. On Monday, 17 August 2015, Martin Graesslin <[email protected]> wrote: > Hi community, > > over the last months I observed the following: > * people not finding our git repositories > * people being surprised that our code is not on github > * some projects starting to use github in addition to our own infrastructure > > Whether we like it or not, github has become a place to look for free software > nowadays and if you are not on github your software just doesn't exist. Given > that we can say KDE doesn't produce source code because we are not on github. > > Other projects have an official mirror (see e.g. [1]) which solves the three > points I have listed above. > > I suggest that we: > * introduce an official mirror for all KDE repositories on github > * replace all existing (non-official) clones > * disallow pull-requests on github to not replace our development model by a > proprietary platform. > > Comments? > > Cheers > Martin > > > [1] https://github.com/GNOME -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org Calligra Suite: : A graphic art and office suite - http://calligra.org Kexi: : A visual database apps builder - http://calligra.org/kexi Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
_______________________________________________ kde-community mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-community
