Skip to content

Change references to "ROCm Library/Libraries" to "ROCm Systems" in various .md files. #3245

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pbhandar-amd wants to merge 3 commits into
base: develop
Choose a base branch
from
Open

Change references to "ROCm Library/Libraries" to "ROCm Systems" in various .md files. #3245

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b091047
Update CONTRIBUTING.md
pbhandar-amd Feb 12, 2026
864f46b
Update gardening.md
pbhandar-amd Feb 12, 2026
7c6879f
Update README.md
pbhandar-amd Feb 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Contributing to the ROCm Libraries
# Contributing to the ROCm Systems

Thank you for contributing! This guide outlines the development workflow, contribution standards, and best practices when working in the super-repo.

Expand Down Expand Up @@ -44,7 +44,7 @@ This keeps your working directory clean and fast, as you won't need to clone the

- `.github/`: CI workflows, scripts, and configuration files for synchronizing repositories during the migration period.
- `docs/`: Documentation, including this guide and other helpful resources.
- `projects/<name>/`: Each folder corresponds to a ROCm library that was previously maintained in its own GitHub repository and released as distinct packages.
- `projects/<name>/`: Each folder corresponds to a ROCm systems component that was previously maintained in its own GitHub repository and released as distinct packages.
- `shared/<name>/`: Shared components that existed in their own repository, used as dependencies by multiple libraries, but do not produce distinct packages in previous ROCm releases.

Further changes to the structure may be made to improve development efficiency and minimize redundancy.
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ projects/

- Enable unified build and test workflows across ROCm libraries.
- Facilitate shared tooling, CI, and contributor experience.
- Improve integration, visibility, and collaboration across ROCm library teams.
- Improve integration, visibility, and collaboration across ROCm Systems teams.

## Getting Started

Expand Down
4 changes: 2 additions & 2 deletions docs/gardening.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# ROCm Libraries Gardeners
# ROCm Systems Gardeners

This documents the mechanics of
[gardening](https://github.com/ROCm/TheRock/blob/main/docs/rfcs/RFC0002-MonoRepo-Gardener-Rotations.md)
for the ROCm Libraries. If you haven't read the above doc, please start there.
for the ROCm Systems. If you haven't read the above doc, please start there.

## Becoming a member

Expand Down
Loading