openstack
/
contributor-guide
Code Issues Proposed changes

Follow OpenDev changes 

With the OpenDev changes a couple of URLs are changed, update them.

Change-Id: I5fa736eeb3977e354f8bbb4ecec42b475938f171
This commit is contained in:
Andreas Jaeger 2019-04-21 15:59:14 +02:00
parent 01d6f38764
commit a90b7024f5
11 changed files with 30 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/code-and-documentation/devstack.rst
View File

@ -40,7 +40,7 @@ repository under ``openstack-dev``.
.. code-block:: console
git clone https://git.openstack.org/openstack-dev/devstack
git clone https://opendev.org/openstack/devstack
It is recommended before proceeding further to set-up passwords and IP
addresses for the environment in which you are running DevStack. This is

2
doc/source/code-and-documentation/elastic-recheck.rst
View File

@ -89,7 +89,7 @@ job you're looking at, and already documented in a few places including:
Once you've identified a message in the logs that can be used for
fingerprinting you need to turn that into an elastic-search query. You can
use any of the existing fingerprints as an example:
`openstack-infra/elastic-recheck <https://git.openstack.org/cgit/openstack-infra/elastic-recheck/tree/queries>`_
`opendev/elastic-recheck <https://opendev.org/opendev/elastic-recheck/src/queries>`_
You should also check any elastic search queries using kibana at:
`Logstash Search <http://logstash.openstack.org/>`_

10
doc/source/code-and-documentation/patch-series-tutorial.rst
View File

@ -5,7 +5,7 @@ Tutorial: Developing Changes In A Series
This tutorial walks through a simple scenario of developing multiple change
sets in a series on the same branch. If you wish, you can follow along, using
the `sandbox repository
<http://git.openstack.org/cgit/openstack-dev/sandbox/>`_, executing the
<https://opendev.org/openstack-dev/sandbox/>`_, executing the
commands exactly as they're laid out.
If you are a visual learner, you may prefer
@ -104,14 +104,14 @@ confirm that I really want to push two commits at once.
remote: Processing changes: new: 2, refs: 2, done
remote:
remote: New Changes:
remote: https://review.openstack.org/635341 Add cyborg client to requirements
remote: https://review.openstack.org/635342 WIP: Cyborg PCI handling
remote: https://review.opendev.org/635341 Add cyborg client to requirements
remote: https://review.opendev.org/635342 WIP: Cyborg PCI handling
remote:
To ssh://review.openstack.org:29418/openstack-dev/sandbox.git
To ssh://review.opendev.org:29418/openstack-dev/sandbox.git
* [new branch] HEAD -> refs/for/master%topic=bp/nova-cyborg-interaction
Now if you go to either of those links - e.g.
https://review.openstack.org/#/c/635342/ - you'll see that the patches
https://review.opendev.org/#/c/635342/ - you'll see that the patches
are stacked up in series on the top right.
But oops, I made a mistake in my first commit. My lower constraint can't be

2
doc/source/code-and-documentation/sandbox-house-rules.rst
View File

@ -37,7 +37,7 @@ Git is a version control system that we use to track changes to our source code
and documentation.
You can find a `sandbox Git repository
<https://git.openstack.org/cgit/openstack-dev/sandbox>`_ where you can practice
<https://opendev.org/openstack-dev/sandbox>`_ where you can practice
the Git commands before you put together a patch to resolve a bug or implement
a new functionality.

8
doc/source/code-and-documentation/using-gerrit.rst
View File

@ -26,11 +26,11 @@ contribution:
To clone a copy of some repository::
git clone https://git.openstack.org/openstack/<PROJECT_NAME>
git clone https://opendev.org/openstack/<PROJECT_NAME>
.. note::
You can find the same respositories using the search function here:
`OpenStack git repository browser <https://git.openstack.org/cgit>`_
You can find the same repositories using the search function here:
`OpenDev git repository browser <https://opendev.org/explore/repos>`_
After you've completed the Setup and Learn GIT section, the following command
configures the repository to know about Gerrit and installs the ``Change-Id``
@ -80,7 +80,7 @@ Tracking your Changes
=====================
After proposing changes, you can track them at
`Code Review <https://review.openstack.org>`_. After logging in, you
`Code Review <https://review.opendev.org>`_. After logging in, you
will see a dashboard of "Outgoing reviews" for changes you have proposed,
"Incoming reviews" for changes you are reviewing, and "Recently
closed" changes for which you were either a reviewer or owner.

2
doc/source/common/git.rst
View File

@ -19,7 +19,7 @@ OpenStack community uses to manage changes to source code and documentation.
Git allows you to:
* Push and test `code, docs, infrastructure changes, and CI configurations <https://git.openstack.org/cgit>`_
* Push and test `code, docs, infrastructure changes, and CI configurations <https://opendev.org/explore/repos>`_
* Push `Specifications <https://specs.openstack.org>`_
* Push `Use cases for features <https://specs.openstack.org/openstack/openstack-user-stories/>`_

24
doc/source/common/setup-gerrit.rst
View File

@ -15,15 +15,15 @@ This is the review system the OpenStack community uses.
Gerrit allows you to review:
* `Code, docs, infrastructure changes, and CI configurations <https://git.openstack.org/cgit>`_
* `Code, docs, infrastructure changes, and CI configurations <https://opendev.org/explore/repos>`_
* `Specifications <https://specs.openstack.org>`_
* `Translations <https://git.openstack.org/cgit/openstack/i18n/tree/>`_
* `Translations <https://opendev.org/openstack/i18n/>`_
* `Use cases for features <https://specs.openstack.org/openstack/openstack-user-stories/>`_
Sign Up
=======
#. Visit `OpenStack's Gerrit page <https://review.openstack.org>`_ and click
#. Visit `OpenStack's Gerrit page <https://review.opendev.org>`_ and click
the **sign in** link.
#. You will be prompted to select a username. You can enter the same one you
did for Launchpad, or something else.
@ -48,7 +48,7 @@ What is it?
An agreement to clarify intellectual property rights granted with
contributions from a person or entity. `Preview the full agreement
<https://review.openstack.org/static/cla.html>`_.
<https://review.opendev.org/static/cla.html>`_.
Signing it
----------
@ -56,7 +56,7 @@ Signing it
Individual Contributors
^^^^^^^^^^^^^^^^^^^^^^^
#. In Gerrit's `settings <https://review.openstack.org/#/settings/agreements>`_
#. In Gerrit's `settings <https://review.opendev.org/#/settings/agreements>`_
click the **New Contributor Agreement** link and sign the
agreement. You need this to contribute code & documentation. You
will not be able to push patches to Gerrit without this.
@ -70,7 +70,7 @@ Contributors From a Company or Organization
If you are contributing on behalf of a company or organization.
#. In Gerrit's `settings <https://review.openstack.org/#/settings/agreements>`_
#. In Gerrit's `settings <https://review.opendev.org/#/settings/agreements>`_
click the **New Contributor Agreement** link and sign the agreement.
.. image:: /_assets/account-setup/3.png
@ -104,7 +104,7 @@ Setup SSH Keys
What are they?
--------------
In order to push things to `Gerrit <https://review.openstack.org>`_ we need to
In order to push things to `Gerrit <https://review.opendev.org>`_ we need to
have a way to identify ourselves. We will do this using SSH keys which allows
us to have our machine we're pushing a change from to perform
a `challenge-response authentication
@ -189,8 +189,8 @@ Finally you need to tell ssh what host(s) to associate SSH keys with. To do
this open "~/.ssh/config" in an editor, create the file if it doesn't exist
and add something like::
Host review.openstack.org review
Hostname review.openstack.org
Host review.opendev.org review
Hostname review.opendev.org
Port 29418
User <your_gerrit_username>
IdentityFile ~/.ssh/id_openstack_rsa
@ -216,7 +216,7 @@ Import Public Key Into Gerrit
-----------------------------
#. Go to `Gerrit's SSH Public Keys settings
<https://review.openstack.org/#/settings/ssh-keys>`_.
<https://review.opendev.org/#/settings/ssh-keys>`_.
#. Click the 'Add Key' button.
#. Paste the public key into the **Add SSH Public Key** text box and click
**Add**.
@ -234,7 +234,7 @@ additional sub-command to 'git' like so::
When you have changes in an OpenStack project repository, you can use this
sub-command to have the changes posted to
`Gerrit <https://review.openstack.org/>`__ so that they can be reviewed.
`Gerrit <https://review.opendev.org/>`__ so that they can be reviewed.
Installation
------------
@ -294,7 +294,7 @@ username. If it's not, you can tell it by setting this git config setting::
git config --global gitreview.username <username>
If you don't know what your Gerrit username is, you can check the `Gerrit
settings <https://review.openstack.org/#/settings/>`_.
settings <https://review.opendev.org/#/settings/>`_.
Preparing to Send a Review
--------------------------

4
doc/source/contributing/contributor-portal.rst
View File

@ -26,10 +26,10 @@ Proposing a Project Team Under Code & Documentation
===================================================
The project teams listed under the 'Code & Documentation' section come from
OpenStack's governance repository `project.yaml file
<http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml>`_.
<https://opendev.org/openstack/governance/src/reference/projects.yaml>`_.
This file is a list of projects that are recognized by the
`Technical Committee <https://governance.openstack.org/tc/>`_. Project teams
under this category should make sure their 'contributor' field is set to the
URL of their specific contributor guide. See the `project.yaml file
<http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml>`_
<https://opendev.org/openstack/governance/src/reference/projects.yaml>`_
file for examples.

2
doc/source/contributing/intro.rst
View File

@ -45,7 +45,7 @@ for getting started.
Once you've read through the guide, use git to clone the Contributor Guide
repository::
git clone https://git.openstack.org/openstack/contributor-guide
git clone https://opendev.org/openstack/contributor-guide
Content Guidelines

2
doc/source/operators/participate.rst
View File

@ -40,6 +40,6 @@ Share and Learn From Real Configurations
========================================
Example configurations for various OpenStack services are provided in the `openstack/osops-example-configs
repository
<https://git.openstack.org/cgit/openstack/osops-example-configs/tree/README.md>`_.
<https://opendev.org/x/osops-example-configs/src/README.md>`_.
Operators can share their configuration files to help others, and review how
others setup and tune their configurations.

2
doc/source/organizations/index.rst
View File

@ -101,7 +101,7 @@ Technical
Code
^^^^
* Access to review.openstack.org for code review and code submission.
* Access to review.opendev.org for code review and code submission.
* Port 29428/tcp is the Gerrit SSH API.
* Port 443/tcp is also available to access gerrit but only recommended if