uabrc / uabrc/uabrc.github.io

Upcoming buy-in model

Open
#1,189 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

style: article/section 📝
Dominant language
Python
Stars
24
Forks
15
Avg merge
10d 3h
Merged PRs (30d)
1

Description

What would you like to see added?

We anticipate Research Computing to be certified as a UAB Service Center, enabling us to sell compute and storage on a fine-grained basis through annual contracts. More details to come.

Below are some notes about what will be needed:

  • Distinction between the prepaid tier (what we have now) and buy-in tier (upcoming). Specifically, we want to use the phrase "prepaid" instead of "no-charge" or "free".
  • Expectations and responsibilities around the buy-in tier. This is per-platform.
    • User experience expectations and differences (this is potentially far reaching, and may involve very fine-grained changes to, e.g., Slurm changes)
    • Responsibilities around administrative obligations (financial, security, data management, etc)
    • Who pays for what? What does my payment get me?
    • more TBD
  • A menu of what is available for purchase. This is per-platform.
  • A documented procedure for requesting buy-in purchases.

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

No file, test, or entry point is named. Start by turning the listed buy-in requirements into a scoped documentation plan, resolving the prepaid/buy-in terminology, per-platform offerings, responsibilities, payment scope, and purchase-request procedure; done means these details are agreed and documented.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.