-
-| Component |
-RST syntax |
-
-
-| Code blocks |
-
+Our repositories typically use the **develop** branch an integration branch for new code so, when
+making a PR, target this branch.
-```rst
-
-.. code-block:: language-name
-
- My code block.
+When creating a PR, use the following process. Note that each repository may include additional,
+project-specific steps. Refer to each repository's PR process for any additional steps.
+* Identify the issue you want to fix
+* Target the **develop** branch for integration
+* Ensure your code builds successfully
+* Each component has a suite of test cases to run; include the log of the successful test run in your PR
+* Do not break existing test cases
+* New functionality is only merged with new unit tests
+ * If your PR includes a new feature, you must provide an application or test so we can ensure that the
+ feature works and continues to be valid in the future
+* Tests must have good code coverage
+* Submit your PR and work with the reviewer or maintainer to get your PR approved
+* Once approved, the PR is brought onto internal CI systems and may be merged into the component
+ during our release cycle, as coordinated by the maintainer
+* We'll inform you once your change is committed
+```important
+By creating a PR, you agree to allow your contribution to be licensed under the
+terms of the LICENSE.txt file in the corresponding repository. Different repositories may use different
+licenses.
```
- |
-
-
-| Cross-referencing internal files |
-
+You can look up each license on the [ROCm licensing](./docs/about/licensing.md) page.
-```rst
+### New feature development
-:doc:`Title <../path/to/file/filename>`
+Use the [GitHub Discussion forum](https://github.com/ROCm/ROCm/discussions)
+(Ideas category) to propose new features. Our maintainers are happy to provide direction and
+feedback on feature development.
-```
+### Documentation
- |
-
-
-| External links |
-
+Submit ROCm documentation changes to our
+[documentation repository](https://github.com/ROCm/ROCm). You must update
+documentation related to any new feature or API contribution.
-```rst
+Note that each ROCm project uses its own repository for documentation.
-`link name `_
+## Future development workflow
-```
-
- |
-
-
-
-| Headings |
-
-
-```rst
-
-******************
-Chapter title (H1)
-******************
-
-Section title (H2)
-===============
-
-Subsection title (H3)
----------------------
-
-Sub-subsection title (H4)
-^^^^^^^^^^^^^^^^^^^^
-
-
-```
-
- |
-
-
-| Images |
-
-
-```rst
-
-.. image:: image1.png
-
-```
-
- |
-
-
-| Internal links |
-
-
-```rst
-
-1. Add a tag to the section you want to reference:
-
-.. _my-section-tag: section-1
-
-Section 1
-==========
-
-2. Link to your tag:
-
-As shown in :ref:`section-1`.
-
-```
-
- |
-
-
-
-| Lists |
-
-
-```rst
-
-# Ordered (numbered) list item
-
-* Unordered (bulleted) list item
-
-```
-
- |
-
-
-
-| Math (block) |
-
-
-```rst
-
-.. math::
-
- A = \begin{pmatrix}
- 0.0 & 1.0 & 1.0 & 3.0 \\
- 4.0 & 5.0 & 6.0 & 7.0 \\
- \end{pmatrix}
-
-```
-
- |
-
-
-| Math (inline) |
-
-
-```rst
-
-:math:`2 \times 2 `
-
-```
-
- |
-
-
-| Notes |
-
-
-```rst
-
-.. note::
-
- My note here.
-
-```
-
- |
-
-
-| Tables |
-
-
-```rst
-
-.. csv-table:: Optional title here
- :widths: 30, 70 #optional column widths
- :header: "entry1 header", "entry2 header"
-
- "entry1", "entry2"
-
-```
-
- |
-
-
-
-## Language and style
-
-We use the
-[Google developer documentation style guide](https://developers.google.com/style/highlights) to
-guide our content.
-
-Font size and type, page layout, white space control, and other formatting
-details are controlled via
-[rocm-docs-core](https://github.com/RadeonOpenCompute/rocm-docs-core). If you want to notify us
-of any formatting issues, create a pull request in our
-[rocm-docs-core](https://github.com/RadeonOpenCompute/rocm-docs-core) GitHub repository.
-
-## Building our documentation
-
-
-To learn how to build our documentation, refer to
-[Building documentation](./building.md).
+The current ROCm development workflow is GitHub-based. If, in the future, we change this platform,
+the tools and links may change. In this instance, we will update contribution guidelines accordingly.
diff --git a/GOVERNANCE.md b/GOVERNANCE.md
new file mode 100644
index 000000000..b985d57da
--- /dev/null
+++ b/GOVERNANCE.md
@@ -0,0 +1,60 @@
+
+
+
+| Component |
+RST syntax |
+
+
+| Code blocks |
+
+
+```rst
+
+.. code-block:: language-name
+
+ My code block.
+
+
+```
+
+ |
+
+
+| Cross-referencing internal files |
+
+
+```rst
+
+:doc:`Title <../path/to/file/filename>`
+
+```
+
+ |
+
+
+| External links |
+
+
+```rst
+
+`link name `_
+
+```
+
+ |
+
+
+
+| Headings |
+
+
+```rst
+
+******************
+Chapter title (H1)
+******************
+
+Section title (H2)
+===============
+
+Subsection title (H3)
+---------------------
+
+Sub-subsection title (H4)
+^^^^^^^^^^^^^^^^^^^^
+
+
+```
+
+ |
+
+
+| Images |
+
+
+```rst
+
+.. image:: image1.png
+
+```
+
+ |
+
+
+| Internal links |
+
+
+```rst
+
+1. Add a tag to the section you want to reference:
+
+.. _my-section-tag: section-1
+
+Section 1
+==========
+
+2. Link to your tag:
+
+As shown in :ref:`section-1`.
+
+```
+
+ |
+
+
+
+| Lists |
+
+
+```rst
+
+# Ordered (numbered) list item
+
+* Unordered (bulleted) list item
+
+```
+
+ |
+
+
+
+| Math (block) |
+
+
+```rst
+
+.. math::
+
+ A = \begin{pmatrix}
+ 0.0 & 1.0 & 1.0 & 3.0 \\
+ 4.0 & 5.0 & 6.0 & 7.0 \\
+ \end{pmatrix}
+
+```
+
+ |
+
+
+| Math (inline) |
+
+
+```rst
+
+:math:`2 \times 2 `
+
+```
+
+ |
+
+
+| Notes |
+
+
+```rst
+
+.. note::
+
+ My note here.
+
+```
+
+ |
+
+
+| Tables |
+
+
+```rst
+
+.. csv-table:: Optional title here
+ :widths: 30, 70 #optional column widths
+ :header: "entry1 header", "entry2 header"
+
+ "entry1", "entry2"
+
+```
+
+ |
+
+
+
+## Language and style
+
+We use the
+[Google developer documentation style guide](https://developers.google.com/style/highlights) to
+guide our content.
+
+Font size and type, page layout, white space control, and other formatting
+details are controlled via
+[rocm-docs-core](https://github.com/RadeonOpenCompute/rocm-docs-core). If you want to notify us
+of any formatting issues, create a pull request in our
+[rocm-docs-core](https://github.com/RadeonOpenCompute/rocm-docs-core) GitHub repository.
+
+## Building our documentation
+
+
+To learn how to build our documentation, refer to
+[Building documentation](./building.md).
diff --git a/docs/sphinx/_toc.yml.in b/docs/sphinx/_toc.yml.in
index 86cf107fe..af672769c 100644
--- a/docs/sphinx/_toc.yml.in
+++ b/docs/sphinx/_toc.yml.in
@@ -7,8 +7,7 @@ root: index
subtrees:
- entries:
- file: what-is-rocm.md
- - file: about/release-notes.md
- title: Release notes
+ - file: about/whats-new/whats-new.md
subtrees:
- entries:
- file: about/CHANGELOG.md
@@ -85,7 +84,7 @@ subtrees:
- file: conceptual/compiler-disambiguation.md
title: Compiler disambiguation
- file: about/compatibility/openmp.md
- title: OpenMP
+ title: OpenMP
- file: conceptual/file-reorg.md
title: File structure (Linux FHS)
- file: conceptual/gpu-isolation.md
@@ -104,15 +103,19 @@ subtrees:
- caption: Contribute
entries:
- file: contribute/index.md
- title: Contribute to ROCm docs
+ title: Contribute to ROCm
subtrees:
- entries:
- - file: contribute/toolchain.md
- title: Documentation tools
- - file: contribute/building.md
- title: Building documentation
- - file: contribute/feedback.md
- title: Provide feedback
+ - file: contribute/contribute-docs.md
+ title: Contribute to ROCm docs
+ subtrees:
+ - entries:
+ - file: contribute/toolchain.md
+ title: Documentation tools
+ - file: contribute/building.md
+ title: Building documentation
+ - file: contribute/feedback.md
+ title: Provide feedback
- file: about/license.md
title: ROCm license