commit e494731476443e0f105e854e82427750ed0a9ed7 Author: gus gus@torproject.org Date: Wed May 27 23:15:03 2020 -0400
Update dip.tpo to gitlab.tpo --- README.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/README.md b/README.md index 591645f..fc5b24c 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ or browse it [online](http://gitweb.torproject.org/project/web/community.git).
## How to report bugs or feedback
-First check if your issue wasn't already opened in [dip.torproject.org](https://dip.torproject.org/web/community/issues), then file a [trac ticket](https://trac.torproject.org/projects/tor/newticket) and choose the component: Webpages/Community. +First check if your issue wasn't already opened in [gitlab.torproject.org](https://gitlab.torproject.org/web/community/issues), then file a [trac ticket](https://trac.torproject.org/projects/tor/newticket) and choose the component: Webpages/Community.
## What is Lektor @@ -51,7 +51,7 @@ To just build the website once: ```$ lektor build -O <folder>```
#### How to develop on the website
-Check our [wiki pages](https://dip.torproject.org/web/community/wikis/How-to-develop-on-the-website). +Check our [wiki pages](https://gitlab.torproject.org/web/community/wikis/How-to-develop-on-the-webs...).
### Translations
@@ -67,14 +67,14 @@ If you want to contribute to the Community portal, we will be happy to help you.
This is the workflow that Tor Internal people should use when making changes on the Community Portal:
-1. When starting work on an issue or content, please assign the issue to yourself and move into the `Doing` column on the [Community Portal Project Board](https://dip.torproject.org/web/community/-/boards). You can follow the process outlined in ["How to send a merge request or propose a change"](https://dip.torproject.org/web/tpo/wikis/Git-flow-and-merge-requests#how-to-...) to work on your changes. -2. To view your changes on the website, you can [run lektor locally](https://dip.torproject.org/web/tpo/wikis/Compiling-a-local-version-of-the-we...). -3. Once you are happy with your work, push your changes to `develop` branch and move to `needs-review` column on the [Community Portal Project Board](https://dip.torproject.org/web/community/-/boards). +1. When starting work on an issue or content, please assign the issue to yourself and move into the `Doing` column on the [Community Portal Project Board](https://dip.torproject.org/web/community/-/boards). You can follow the process outlined in ["How to send a merge request or propose a change"](https://gitlab.torproject.org/web/tpo/wikis/Git-flow-and-merge-requests#how-...) to work on your changes. +2. To view your changes on the website, you can [run lektor locally](https://gitlab.torproject.org/web/tpo/wikis/Compiling-a-local-version-of-the...). +3. Once you are happy with your work, push your changes to `develop` branch and move to `needs-review` column on the [Community Portal Project Board](https://gitlab.torproject.org/web/community/-/boards). 4. Add a comment to the issue, tagging the reviewer, e.g. `@steph`, with: - Location of page on lektor-staging `develop` branch, e.g. https://lektor-staging.torproject.org/community/develop/. - - Contents file, containing your changes where it would be located on the **reviewer's repo**, e.g. `https://dip.torproject.org/steph/community/blob/develop/content/onion-servic.... + - Contents file, containing your changes where it would be located on the **reviewer's repo**, e.g. `https://gitlab.torproject.org/steph/community/blob/develop/content/onion-ser.... - For the review workflow, please see (Reviewer Workflow). -5. Once the work has been reviewed and any necessary changes and merge request has been made, a repo maintainer or team members with write access to gitweb master will then merge or cherry-pick these changes to master, following the workflow outlined in [How to use our git flow](https://dip.torproject.org/web/tpo/wikis/Git-flow-and-merge-requests#how-to-...). +5. Once the work has been reviewed and any necessary changes and merge request has been made, a repo maintainer or team members with write access to gitweb master will then merge or cherry-pick these changes to master, following the workflow outlined in [How to use our git flow](https://gitlab.torproject.org/web/tpo/wikis/Git-flow-and-merge-requests#how-...). 6. Merger should then move the the ticket to the `Closed` column.
### Reviewer Workflow @@ -88,10 +88,10 @@ This is the workflow that Tor Internal people should use when making changes on - Click on "Commit changes". 4. You will be sent to a new page to create your merge request: - Update "Title" with a short title to explain your changes. - - Update "Description", you can use the commit message you entered before additionally referencing the original issue you have reviewed, e.g. `https://dip.torproject.org/web/community/issues/3%60, and tagging one of the repo maintainers, e.g. `@pili`, so they know the change can be merged. + - Update "Description", you can use the commit message you entered before additionally referencing the original issue you have reviewed, e.g. `https://gitlab.torproject.org/web/community/issues/3%60, and tagging one of the repo maintainers, e.g. `@pili`, so they know the change can be merged. - Make sure that both "Delete source branch when merge request is accepted" and "Squash commits when merge request is accepted" are checked. - Click "Submit merge request". -5. Reviewer should comment on the original issue with a link to the merge request created, e.g. `https://dip.torproject.org/steph/community/merge_requests/2%60. +5. Reviewer should comment on the original issue with a link to the merge request created, e.g. `https://gitlab.torproject.org/steph/community/merge_requests/2%60.
### Volunteer Workflow