| ~P1 | Urgent Priority | The current release + potentially immediate hotfix to GitLab.com | |
| ~P2 | High Priority | The next release | |
| ~P3 | Medium Priority | Within the next 3 releases (approx one quarter) | |
| ~P4 | Low Priority | Anything outside the next 3 releases (approx beyond one quarter) | The issue is prominent but does not impact user workflow and a workaround is documented |
| ~S2 | Many users or multiple paid customers impacted (but not apocalyptic)| The issue is (almost) guaranteed to occur in the near future |
| ~S3 | A few users or a single paid customer impacted | The issue is likely to occur in the near future |
| ~S4 | No paid users/customer impacted, or expected impact within 30 days | The issue _may_ occur but it's not likely |
Severity levels can be applied further depending on the facet of the impact; e.g. Affected customers, GitLab.com availability, performance and etc. The below is a guideline.
| ~S1 | >50% users affected (possible company extinction level event) | Significant impact on all of GitLab.com | |
| ~S2 | Many users or multiple paid customers affected (but not apocalyptic)| Significant impact on large portions of GitLab.com | Degradation is guaranteed to occur in the near future |
| ~S3 | A few users or a single paid customer affected | Limited impact on important portions of GitLab.com | Degradation is likely to occur in the near future |
| ~S4 | No paid users/customer affected, or expected to in the near future | Minor impact on on GitLab.com | Degradation _may_ occur but it's not likely |
### Label for community contributors
...
...
@@ -729,6 +732,24 @@ reported by emailing `contact@gitlab.com`.
This Code of Conduct is adapted from the [Contributor Covenant][contributor-covenant], version 1.1.0,
available at [http://contributor-covenant.org/version/1/1/0/](http://contributor-covenant.org/version/1/1/0/).
## Contribution Flow
When contributing to GitLab, your merge request is subject to review by merge request maintainers of a particular specialty.
When you submit code to GitLab, we really want it to get merged, but there will be times when it will not be merged.
When maintainers are reading through a merge request they may request guidance from other maintainers. If merge request maintainers conclude that the code should not be merged, our reasons will be fully disclosed. If it has been decided that the code quality is not up to GitLab’s standards, the merge request maintainer will refer the author to our docs and code style guides, and provide some guidance.
Sometimes style guides will be followed but the code will lack structural integrity, or the maintainer will have reservations about the code’s overall quality. When there is a reservation the maintainer will inform the author and provide some guidance. The author may then choose to update the merge request. Once the merge request has been updated and reassigned to the maintainer, they will review the code again. Once the code has been resubmitted any number of times, the maintainer may choose to close the merge request with a summary of why it will not be merged, as well as some guidance. If the merge request is closed the maintainer will be open to discussion as to how to improve the code so it can be approved in the future.
GitLab will do its best to review community contributions as quickly as possible. Specially appointed developers review community contributions daily. You may take a look at the [team page](https://about.gitlab.com/team/) for the merge request coach who specializes in the type of code you have written and mention them in the merge request. For example, if you have written some JavaScript in your code then you should mention the frontend merge request coach. If your code has multiple disciplines you may mention multiple merge request coaches.
GitLab receives a lot of community contributions, so if your code has not been reviewed within 4 days of its initial submission feel free to re-mention the appropriate merge request coach.
When submitting code to GitLab, you may feel that your contribution requires the aid of an external library. If your code includes an external library please provide a link to the library, as well as reasons for including it.
When your code contains more than 500 changes, any major breaking changes, or an external library, `@mention` a maintainer in the merge request. If you are not sure who to mention, the reviewer will add one early in the merge request process.
=link_to_('Delete'),[:admin,group],data: {confirm: _("Are you sure you want to remove %{group_name}?")%{group_name: group.name}},method: :delete,class: 'btn btn-remove'
msgid "404|Please contact your GitLab administrator if you think this is a mistake."
msgstr ""
msgid "<strong>%{group_name}</strong> group members"
msgstr ""
msgid "<strong>Removes</strong> source branch"
msgstr ""
...
...
@@ -283,6 +289,12 @@ msgstr ""
msgid "Add todo"
msgstr ""
msgid "Add user(s) to the group:"
msgstr ""
msgid "Add users to group"
msgstr ""
msgid "AdminArea|Stop all jobs"
msgstr ""
...
...
@@ -484,6 +496,9 @@ msgstr ""
msgid "Are you sure you want to delete this pipeline schedule?"
msgstr ""
msgid "Are you sure you want to remove %{group_name}?"
msgstr ""
msgid "Are you sure you want to remove this identity?"
msgstr ""
...
...
@@ -1666,9 +1681,6 @@ msgstr ""
msgid "Copy commit SHA to clipboard"
msgstr ""
msgid "Copy file name to clipboard"
msgstr ""
msgid "Copy file path to clipboard"
msgstr ""
...
...
@@ -1708,6 +1720,9 @@ msgstr ""
msgid "Create file"
msgstr ""
msgid "Create group"
msgstr ""
msgid "Create group label"
msgstr ""
...
...
@@ -1756,6 +1771,9 @@ msgstr ""
msgid "Created by me"
msgstr ""
msgid "Created on:"
msgstr ""
msgid "Cron Timezone"
msgstr ""
...
...
@@ -1962,6 +1980,9 @@ msgstr ""
msgid "Description"
msgstr ""
msgid "Description:"
msgstr ""
msgid "Details"
msgstr ""
...
...
@@ -2058,6 +2079,9 @@ msgstr ""
msgid "Edit files in the editor and commit changes here"
msgstr ""
msgid "Edit group: %{group_name}"
msgstr ""
msgid "Edit identity for %{user_name}"
msgstr ""
...
...
@@ -2456,15 +2480,27 @@ msgstr ""
msgid "Group CI/CD settings"
msgstr ""
msgid "Group Git LFS status:"
msgstr ""
msgid "Group ID"
msgstr ""
msgid "Group Runners"
msgstr ""
msgid "Group avatar"
msgstr ""
msgid "Group info:"
msgstr ""
msgid "Group maintainers can register group runners in the %{link}"
msgstr ""
msgid "Group: %{group_name}"
msgstr ""
msgid "GroupSettings|Prevent sharing a project within %{group} with other groups"
msgstr ""
...
...
@@ -2898,6 +2934,9 @@ msgstr ""
msgid "Locked to current projects"
msgstr ""
msgid "Manage access"
msgstr ""
msgid "Manage all notifications"
msgstr ""
...
...
@@ -3084,6 +3123,9 @@ msgstr ""
msgid "Name your individual key via a title"
msgstr ""
msgid "Name:"
msgstr ""
msgid "Nav|Help"
msgstr ""
...
...
@@ -3099,6 +3141,9 @@ msgstr ""
msgid "New"
msgstr ""
msgid "New Group"
msgstr ""
msgid "New Identity"
msgstr ""
...
...
@@ -3386,6 +3431,9 @@ msgstr ""
msgid "Paste your public SSH key, which is usually contained in the file '~/.ssh/id_rsa.pub' and begins with 'ssh-rsa'. Don't use your private SSH key."
msgstr ""
msgid "Path:"
msgstr ""
msgid "Pause"
msgstr ""
...
...
@@ -3746,6 +3794,9 @@ msgstr ""
msgid "Projects"
msgstr ""
msgid "Projects shared with %{group_name}"
msgstr ""
msgid "ProjectsDropdown|Frequently visited"
msgstr ""
...
...
@@ -3872,6 +3923,9 @@ msgstr ""
msgid "Read more"
msgstr ""
msgid "Read more about project permissions <strong>%{link_to_help}</strong>"