Skip to content

Commit d432a69

Browse files
committed
rearrange pages
1 parent 45c8505 commit d432a69

File tree

2 files changed

+8
-5
lines changed

2 files changed

+8
-5
lines changed

docs/rocky/support.md docs/rocky/bu_support.md

+4-1
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,9 @@ title: Getting Community Help & Support
44

55
The Rocky Linux Project has several places where users can find community support, depending on the nature of issue.
66

7+
!!! note
8+
This is for general support of Rocky Linux and is not meant for bug reporting. Please see our [Reporting Bugs and RFE's page](bugs.md) for more information.
9+
710
## Rocky Linux (core distribution)
811

912
Core distribution community support can be obtained at the following locations:
@@ -16,7 +19,7 @@ Core distribution community support can be obtained at the following locations:
1619

1720
## Rocky Linux Infrastructure and Services
1821

19-
Rocky Linux Infrastructure have responsibility over several areas. Support or questions can be asked at any of the following:
22+
Rocky Linux Infrastructure have responsibility over several areas, such as mirror manager and Mattermost. Support or questions that pertain only to the infrastructure managed by the project can be asked at any of the following:
2023

2124
* [Mattermost](https://chat.rockylinux.org/rocky-linux/channels/infrastructure)
2225
* [IRC (Libera)](https://libera.chat) (`#rockylinux-infra`)

docs/rocky/bugs.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -8,18 +8,18 @@ The Rocky Linux Project has several ways of reporting issues or requesting enhan
88

99
### Bugs
1010

11+
!!! note
12+
The bug tracker is **not** meant for general support questions. Do not be surprised if a maintainer closes the bug report immediately if it's found to be a general question rather than an actual bug report.
13+
1114
Bugs are an inevitable part of any Linux distribution. Users may find problems and want a way to report the bug.
1215

13-
All bug reports (which includes some packages from Special Interest Groups) should be reported at our [Bug Tracker](https://bugs.rockylinux.org).
16+
All bug reports should be reported at our [Bug Tracker](https://bugs.rockylinux.org).
1417

1518
When reporting bugs, ensure you have read the [Bug Tracker Guidelines](../guidelines/bug_tracker_guidelines.md) so you can make a proper bug report.
1619

1720
!!! note
1821
You may be asked to reproduce the issue on Red Hat Enterprise Linux. If the issue is reproducible on RHEL, you are encouraged to also open a bug report at the [Red Hat Jira](https://issues.redhat.com). The assignee on your bug report can do this for you also if you wish.
1922

20-
!!! note
21-
The bug tracker is not meant for general support questions. Do not be surprised if a maintainer closes the bug report immediately if it's found to be a general support question rather than an actual bug report.
22-
2323
### RFE (Request for Enhancement)
2424

2525
Requests for Enhancements to packages[^1] are typically handled at the [Bug Tracker](https://bugs.rockylinux.org). In some cases, this may not apply. A Special Interest Group may ask that an RFE be submitted elsewhere. See the SIG section later in this page.

0 commit comments

Comments
 (0)