1,285
edits
Changes
Activity Team/Git Introduction (view source)
Revision as of 22:36, 9 December 2014
, 22:36, 9 December 2014→Commit message guidelines
== Gitorious ==
== Gitorious ==
Gitorious provides open source infrastructure for hosting open source projects that use Git. The central entity in Gitorious is the project, which contains one or more top-level repositories and any repositories managed by the project's contributors.
'''Gitorious''' provides open source infrastructure for hosting open source projects that use Git. The central entity in Gitorious is the project, which contains one or more top-level repositories and any repositories managed by the project's contributors.
This allows you, as a project administrator, to keep an eye on what people are working on in their individual clones of your repositories. It also lets you merge or provide feedback on their contributions.
This allows you, as a project administrator, to keep an eye on what people are working on in their individual clones of your repositories. It also lets you merge or provide feedback on their contributions.
Likewise, as a project contributor, you get a place to host your contributions and provide feedback back into the projects ecosystem and easily collaborate with others on the same project. You get your own personal clone of the project on the site that you can work freely in and a way to package up your changes and notify the other project members about your changes.
Likewise, as a project contributor, you get a place to host your contributions and provide feedback back into the projects ecosystem and easily collaborate with others on the same project. You get your own personal clone of the project on the site that you can work freely in and a way to package up your changes and notify the other project members about your changes.
== Commit message guidelines ==
These are guidelines to enhance the readability of the commit messages and the release notes which are made with [http://www.kernel.org/pub/software/scm/git/docs/git-shortlog.html git-shortlog]. Please try to follow them as much as possible and make suggestions in the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar devel mailing list] if you find things missing, the guidelines completely insane or just want to demonstrate your appreciation.
* The commit message should start with a single short line summarizing the change (less than 50 characters), followed by a blank line and then a more thorough description (wrapped to 72 characters per line). This is because tools that turn commits into email, for example, use the first line on the Subject: line and the rest of the commit in the body. Also, the git-shortlog command that we use to write the release notes will strip the more detailed description.
* If your commit does fix a certain bug make sure that the summarizing line contains the bug number prepended by a '#' at the '''end''' of the line (e.g. #14). Please prepend an identifier indicating the bug tracker, e.g. [http://bugs.sugarlabs.org/ticket/342 SL#342], [http://dev.laptop.org/ticket/9358 OLPC#9358], [https://bugzilla.redhat.com/show_bug.cgi?id=482949 RH#482949], [http://bugs.debian.org/555965 Debian#555965], [https://bugs.launchpad.net/sugar/+bug/480407 Ubuntu#480407].
* Start your commit message with a capital letter.
* Suffix no dot at the end of the summarizing line.
* Fixes for typing errors and pylint fixes happen quite often. Just mark them _Typo and respectively _Pylint for easier reading.
----
[[Category:Activity Team]]
[[Category:Activity Team]]