Infrastructure/Git
<languages /> <translate> This is the hub page for all information about the use of Git by KDE.
KDE and Git
This section provides details on using the KDE Git infrastructure. This is intended for use by KDE developers to find out how KDE uses Git and how to set up Git for use with KDE.
The KDE Git System Administrators Manual is a useful resource for more details on the technical implementation of the KDE Git infrastructure.
For more information on how the KDE Git Repositories are organized, please see the Sources page or the KDE Git Projects page.
Please note that some KDE modules are still using SVN, for more details read the Using Subversion with KDE page.
KDE Git Configuration
How to configure Git for use with the KDE infrastructure.
Please see the Git Configuration page.
KDE Git Policies
KDE policies on Git. More generic development policies go elsewhere.
No formal workflow policy currently exists, but a number of draft proposals have been made:
- Infrastructure/Git/Simple_Workflow
- Infrastructure/Git/Feature_Branch_Workflow
- Infrastructure/Tutorials/Git/Feature_Development_Workflow
- http://community.kde.org/Frameworks/Git_Workflow
KDE Git Recipes
Short recipes for using Git with the KDE infrastructure.
Please see the Git Recipes page.
KDE Git Tutorials
More in-depth instructions in using Git.
Please help filling this section by
- checking the links at the bottom of the page and see which still have valid content
- write tutorials yourself
External Git Resources
Links to useful external sites about Git
Official Documentation
Git for SVN Users
Git books
- Pro Git - An easy to understand book on git (CC licensed).
- The git community book, also as a pdf
Tutorials
- Git Magic - A good intro to git (in several languages!)
- Essential reading if you want to truly understand git.
Cheat Sheets
(broken image, get it from Media:Zrusin-git-cheat-sheet-medium.png)
Documentation Changes
KDE Documentation Review
Existing Pages For Review
Existing KDE pages about Git, SVN, and/or buildinga KDE that need to be revised. When revising pages try to split the generic development and revision control policies separate from Git specific stuff. Do not refer to "the KDE Git Repository" but instead the "KDE Code Repository". Lots of small simple pages that are less daunting to newbies and can be linked to from multiple locations are preferred to massive walls of text.
Keep:
On community.kde.org:
On techbase.kde.org:
There are also numerous other pages referring to "the KDE SVN/subversion repositories" which should be replaced with the generic "KDE code repositories".
There are also numerous translated pages which will need to be updated once the original pages are completed.
New Page Structure
</translate>