Files
ROCm/docs/contribute/feedback.md
spolifroni-amd f86f275cf1 Restructured the contributions section. (#3715)
* testing if this file is editable

* changed 'kebob-case' to 'dash-case'

* Restructured the page to be more straightforward and provide additional repo information

* forgot to save

* Moved the topic sentence

* Wrong accent on the a in diataxis

* Removed the feedback info from contributing and moved it to Feedback

* fixed spelling errors

* fixed some wording and removed second person text

* consolidated Build and Structure into Contribute; edited toolchai to (hopefully) conform to style guide; updated toc

* updated the titles in the toc

* made changes based on feedback

* it's better when you save

* removed structure and build; fixed something for the linter

* added rst to wordlist

* added customizations to wordlist
2024-10-01 13:59:51 -04:00

1.5 KiB

<head> </head>

Providing feedback about the ROCm documentation

Feedback about the ROCm documentation is welcome. You can provide feedback about the ROCm documentation either through GitHub Discussions or GitHub Issues.

Participating in discussions through GitHub Discussions

You can ask questions, view announcements, suggest new features, and communicate with other members of the community through GitHub Discussions.

Submitting issues through GitHub Issues

You can submit issues through GitHub Issues.

When creating a new issue, follow the following guidelines:

  1. Always do a search to see if the same issue already exists. If the issue already exists, upvote it, and comment or post to provide any additional details you might have.
  2. If you find an issue that is similar to your issue, log your issue, then add a comment that includes a link to the similar issue, as well as its issue number.
  3. Always provide as much information as possible. This helps reduce the time required to reproduce the issue.

After creating your issue, make sure to check it regularly for any requests for additional information.

For information about contributing content to the ROCm documentation, see Contributing to the ROCm documentation.