uabrc / uabrc/devops-docs

Ways to update our community about changes to our platform

Open
#52 0 comments 0 reactions 0 assignees View on GitHub

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)

StatusCast

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.

      Image

  • 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.