Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-docs.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEvan Read <eread@gitlab.com>2023-02-15 15:20:28 +0300
committerDiana Logan <dlogan@gitlab.com>2023-02-15 15:20:28 +0300
commit65830490a6ed03d2a5daae8c6e69e1b2f947edee (patch)
tree8c1e1134e3ea3b3aed7b6b27553680df5b07a00e /CONTRIBUTING.md
parentfee9465af4a94bec07aa14df7a0cf4021687c21d (diff)
Update CONTRIBUTING.md file for current processes
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md35
1 files changed, 17 insertions, 18 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 670aac13..32e9a62c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -13,28 +13,27 @@ terms.
## Ownership
-The [Editor group](https://about.gitlab.com/handbook/product/categories/#editor-group)
-in the DevOps Create stage is the team responsible for developing and
-maintaining this project with the Technical Writing team.
-
-[Jacques Erasmus](https://gitlab.com/jerasmus) is in charge of scheduling work
-from this project in the [Editor group](https://about.gitlab.com/handbook/product/categories/#editor-group),
-and the DRI is [Susan Tacker](https://gitlab.com/susantacker), Senior Manager,
-Technical Writing.
+[Susan Tacker](https://gitlab.com/susantacker), Director, Technical Writing, is the DRI for this project.
## Contribution process
-The DRI and the EM will prioritize and schedule improvements to the docs
-site. Workflow labels (`docs-site::*` and `workflow::*`), as well as priority
-labels `P*` should be handled **exclusively** by them.
+When creating issues, merge requests, and epics related to <https://docs.gitlab.com>:
+
+1. Add the label ~"Category:Docs Site".
+1. Add the labels ~frontend, ~backend, or ~UX as required.
-When creating issues, merge requests, and epics related to <https://docs.gitlab.com>,
-add the label ~"Category:Docs Site" plus ~frontend, and/or ~backend, and/or
-~UX, accordingly.
+See the available [issue templates](https://gitlab.com/gitlab-org/gitlab-docs/-/tree/main/.gitlab/issue_templates) and
+[merge request templates](https://gitlab.com/gitlab-org/gitlab-docs/-/tree/main/.gitlab/merge_request_templates).
### Code review guidelines
-You're very welcome to contribute to this project. Once you've verified that
-your code is working, assign the MR to a [reviewer](https://about.gitlab.com/handbook/engineering/projects/#gitlab-docs)
-of the changed subject. Once the review is complete, assign a maintainer to
-merge your changes.
+You're very welcome to contribute to this project.
+
+When contributing:
+
+- Code, assign merge requests to a [code owner](CODEOWNERS) for review.
+- Global navigation updates, assign merge requests to the
+ [assigned technical writer](https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments) for the
+ relevant group or project for review. At mention [Suzanne Selhorn](https://gitlab.com/sselhorn), Staff Technical Writer.
+
+For any other updates, assign to any technical writer for review.