openstack
/
puppet-openstack-guide
Code Issues Proposed changes

Remove duplicate contents 

The way to contact the team is already explained in a different page
(contributor/talk-to-us.html).

Change-Id: Ic81e014de1f3fcc4d6ae7a6a10743015ee671277
This commit is contained in:
Takashi Kajinami 2022-01-22 23:37:05 +09:00
parent d004968ac6
commit 5e2b6be665
1 changed files with 0 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/source/contributor/coding-style.rst
View File

@ -119,16 +119,3 @@ Documentation
- Any change in interface (like new parameters, deprecations, and etc) or
fundamental behavior should be documented in a release note. In Puppet OpenStack,
we use `reno <https://docs.openstack.org/reno/latest/>`__ to maintain release notes.
Asking for review
=================
Different ways to get reviewsː
- Go on IRC ``#puppet-openstack`` (OFTC) and gently ask for
reviews. If you need to discuss about already reviewed code, you can
ping the reviewers.
- Add your patch on the Puppet OpenStack `meeting <meetings.html>`_ Agenda (in Open Discussion section).
- Use the `Mailing list <mailing-list.html>`_.