Ways to update our community about changes to our platform
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Open On-Demand (OOD) Announcement and Message of the Day (MOTD)
- For OOD main page announcements, make changes to: https://gitlab.rc.uab.edu/rc/rc-ood-message/announcement.md
- Bootstrap alerts and other features are allowed
>=1.6: https://getbootstrap.com/docs/5.3/components/alerts/#examples - Markdown emoji are allowed
>=2.0: https://github.com/ikatyang/emoji-cheat-sheet - Test these first!
- Bootstrap alerts and other features are allowed
- For SSH MOTD, make changes to: https://gitlab.rc.uab.edu/rc/rc-ood-message/motd
- More details here: https://osc.github.io/ood-documentation/release-2.0/customization.html#announcements
StatusCast
- To view the RC StatusCast information go to: https://uabstatus.statuscast.com/?componentId=34990
- To add a new incident
- Start at: https://status.uab.edu/admin
- Click "Incidents" in the left panel
- Follow the prompts. Plain text is used.
- Make note of the incident URL for future updating
- To add information to an incident:
- Use the incident URL from when it was created, or search at https://status.uab.edu/admin, to find the incident page.
- Click "Add New Post"
- Follow the prompts.
- To resolve an incident
- Use the incident URL from when it was created, or search at https://status.uab.edu/admin, to find the incident page.
- Click "Resolve"
HPC Announce Email List
-
Send an email to hpc-announce@listserv.uab.edu
-
Ensure that the "reply-to" address is set to
support@listserv.uab.edu, that way researcher replies are directed to ServiceNow as service requests, rather than to the person making the announcement.
-
-
Manage the listserv at https://listserv.uab.edu
-
Will be sent to all Cheaha accounts!
-
This is a high-noise operation, please reserve for incidents impacting all users, or the entire RC platform.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files; start by locating the documentation page where community-update procedures belong and compare it with the OOD, StatusCast, and HPC Announce steps listed here. Done means those procedures are documented accurately, including the links and reply-to requirement.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100