Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
jami-project
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
savoirfairelinux
jami-project
Commits
9e4a117a
Commit
9e4a117a
authored
9 years ago
by
Alexandre Lision
Browse files
Options
Downloads
Patches
Plain Diff
add CONTRIBUTING file
Change-Id: I52a988bc02021c2d90c586801fbe811e602196d7 Tuleap:
#451
parent
e2ff05c7
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CONTRIBUTING.md
+27
-0
27 additions, 0 deletions
CONTRIBUTING.md
with
27 additions
and
0 deletions
CONTRIBUTING.md
0 → 100644
+
27
−
0
View file @
9e4a117a
# How to contribute
Ring loves external contributions. But we do not use Github PR system.
Instead we host a public gerrit server.
https://gerrit-ring.savoirfairelinux.com
More documentation on Gerrit:
https://www.gerritcodereview.com/
In each Ring modules there is a .gitreview file. It contains all the
necessary info to send a patchset to our gerrit.
After you commited your changes (one or multiple commits) you only
need to submit them with:
git-review
## Making Changes
*
[Optionnal] Create a ticket in our Tuleap bug tracker https://tuleap.ring.cx/projects/ring
*
Make commits of logical units.
*
Check for unnecessary whitespace with
`git diff --check`
before committing.
*
Make sure your commit messages are in the proper format
-
50 chars title
-
80 chars message width
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment