8.41 KB
Newer Older
1 2 3 4
# GitLab Contributing Process

## Purpose of describing the contributing process

5 6 7 8 9
Below we describe the contributing process to GitLab for two reasons. So that
contributors know what to expect from maintainers (possible responses, friendly
treatment, etc.). And so that maintainers know what to expect from contributors
(use the latest version, ensure that the issue is addressed, friendly treatment,

11 12
- [GitLab Inc engineers should refer to the engineering workflow document](

## Common actions

15 16 17 18 19
### Issue triaging

Our issue triage policies are [described in our handbook]. You are very welcome
to help the GitLab team triage issues. We also organize [issue bash events] once
every quarter.

21 22
The most important thing is making sure valid issues receive feedback from the
development team. Therefore the priority is mentioning developers that can help
on those issues. Please select someone with relevant experience from
[GitLab team][team]. If there is nobody mentioned with that expertise
25 26 27 28
look in the commit history for the affected files to find someone. Avoid
mentioning the lead developer, this is the person that is least likely to give a
timely response. If the involvement of the lead developer is needed the other
core team members will mention this person.

30 31
[described in our handbook]:
[issue bash events]:

### Merge request coaching

35 36
Several people from the [GitLab team][team] are helping community members to get
their contributions accepted by meeting our [Definition of done][].
Mark Pundsack's avatar
Mark Pundsack committed

38 39 40
What you can expect from them is described at

## Workflow labels
Sid Sijbrandij's avatar
Sid Sijbrandij committed

Labelling issues is described in the [GitLab Inc engineering workflow].

[GitLab Inc engineering workflow]:

46 47 48 49
## Assigning issues

If an issue is complex and needs the attention of a specific person, assignment is a good option but assigning issues might discourage other people from contributing to that issue. We need all the contributions we can get so this should never be discouraged. Also, an assigned person might not have time for a few weeks, so others should feel free to takeover.

50 51
## Be kind

52 53 54
Be kind to people trying to contribute. Be aware that people may be a non-native
English speaker, they might not understand things or they might be very
sensitive as to how you word things. Use Emoji to express your feelings (heart,
55 56 57 58
star, smile, etc.). Some good tips about code reviews can be found in our
[Code Review Guidelines].

[Code Review Guidelines]:

60 61
## Feature Freeze

On the 7th of each month, the stable branches for the upcoming release will
63 64 65 66 67 68 69 70
be frozen for major changes. Merge requests may still be merged into master
during this period. By freezing the stable branches prior to a release there's
no need to worry about last minute merge requests potentially breaking a lot of

What is considered to be a major change is determined on a case by case basis as
this definition depends very much on the context of changes. For example, a 5
line change might have a big impact on the entire application. Ultimately the
decision will be made by the maintainers and the release managers.

During the feature freeze all merge requests that are meant to go into the upcoming
74 75 76 77
release should have the correct milestone assigned _and_ have the label
~"Pick into Stable" set. Merge requests without a milestone and this label will
not be merged into any stable branches.

78 79 80 81
## Copy & paste responses

### Improperly formatted issue

Thanks for the issue report. Please reformat your issue to conform to the \[contributing guidelines\]\(
83 84 85

### Issue report for old version

Robert Schilling's avatar
Robert Schilling committed
Thanks for the issue report but we only support issues for the latest stable version of GitLab. I'm closing this issue but if you still experience this problem in the latest stable version, please open a new issue (but also reference the old issue(s)). Make sure to also include the necessary debugging information conforming to the issue tracker guidelines found in our \[contributing guidelines\]\(
87 88 89

### Support requests and configuration questions

90 91 92 93 94
Thanks for your interest in GitLab. We don't use the issue tracker for support
requests and configuration questions. Please check our
\[getting help\]\( page to see all of the available
support options. Also, have a look at the \[contribution guidelines\]\(
for more information.
95 96 97 98 99 100 101

### Code format

Please use ``` to format console output, logs, and code as it's very hard to read otherwise.

### Issue fixed in newer version

Thanks for the issue report. This issue has already been fixed in newer versions of GitLab. Due to the size of this project and our limited resources we are only able to support the latest stable release as outlined in our \[contributing guidelines\]\( In order to get this bug fix and enjoy many new features please \[upgrade\]\( If you still experience issues at that time please open a new issue following our issue tracker guidelines found in the \[contributing guidelines\]\(

### Improperly formatted merge request

Robert Schilling's avatar
Robert Schilling committed
Thanks for your interest in improving the GitLab codebase! Please update your merge request according to the \[contributing guidelines\]\(
107 108 109

### Inactivity close of an issue

Robert Schilling's avatar
Robert Schilling committed
It's been at least 2 weeks (and a new release) since we heard from you. I'm closing this issue but if you still experience this problem, please open a new issue (but also reference the old issue(s)). Make sure to also include the necessary debugging information conforming to the issue tracker guidelines found in our \[contributing guidelines\]\(

### Inactivity close of a merge request

Robert Schilling's avatar
Robert Schilling committed
This merge request has been closed because a request for more information has not been reacted to for more than 2 weeks. If you respond and conform to the merge request guidelines in our \[contributing guidelines\]\( we will reopen this merge request.

116 117
### Accepting merge requests

118 119 120
Is there an issue on the
\[issue tracker\]\( that is
similar to this? Could you please link it here?
Please be aware that new functionality that is not marked
\[accepting merge requests\]\(
might not make it into GitLab.
124 125 126

### Only accepting merge requests with green tests

Jeroen van Baarsen's avatar
Jeroen van Baarsen committed
127 128 129 130
We can only accept a merge request if all the tests are green. I've just
restarted the build. When the tests are still not passing after this restart and
you're sure that is does not have anything to do with your code changes, please
rebase with master to see if that solves the issue.
131 132 133 134

### Closing down the issue tracker on GitHub

We are currently in the process of closing down the issue tracker on GitHub, to
prevent duplication with the issue tracker.
Since this is an older issue I'll be closing this for now. If you think this is
137 138 139 140
still an issue I encourage you to open it on the \[ issue tracker\]\(

[contribution acceptance criteria]:
["Implement design & UI elements" guidelines]:
[Thoughtbot code review guide]: