Infrastructure/Git/GitHub Mirror: Difference between revisions
m →GitHubMirror: real easy peasy |
|||
Line 10: | Line 10: | ||
Our central repositories are handled by our awesome sysadmins over on kde.org where we have full control and tighter integration within our services. | Our central repositories are handled by our awesome sysadmins over on kde.org where we have full control and tighter integration within our services. | ||
If we | If we started using multiple repositories and making developers look in two places that gets even more complicated and unfair on the maintainers. | ||
Also as an open source project, it's very important for us to keep to using open source tools. Github does not meet that requirement. | Also as an open source project, it's very important for us to keep to using open source tools. Github does not meet that requirement. Also, GitHub is subject to policy changes without notice, which can be less of a pleasant surprise. | ||
==How do I submit "Pull Requests"?== | ==How do I submit "Pull Requests"?== |
Revision as of 07:41, 11 March 2019
GitHubMirror
KDE is managing a read-only mirror of quickgit.kde.org on Github. It's located at https://github.com/KDE .
We want to make KDE sources easy to find, share and build upon; and most importantly we want your contributions to count towards your github profile :-) but of course, if you e.g. search "ECM" , you find nothing on GitHub. Easy, no?
FAQ
Why don't you enable pull requests?
Our central repositories are handled by our awesome sysadmins over on kde.org where we have full control and tighter integration within our services. If we started using multiple repositories and making developers look in two places that gets even more complicated and unfair on the maintainers.
Also as an open source project, it's very important for us to keep to using open source tools. Github does not meet that requirement. Also, GitHub is subject to policy changes without notice, which can be less of a pleasant surprise.
How do I submit "Pull Requests"?
- Fork and commit your changes in your fork as before
- Create an account on http://identity.kde.org
- Run
git format-patch HEAD~1
to create a diff
- Head to https://git.reviewboard.kde.org and click "New Review Request".
The maintainer for this software will then comment and merge your request.
Alternatively you can use the command "rbt post" from reviewboard-tools to streamline the process.
TODO: explain usage of phabricator for reviews
How do I submit "Issues"?
Please file a bug report or wish at http://bugs.kde.org