How do we provide infrastructure to person(s) affiliated with the project? #3
Labels
No Label
Kind/Community
Kind/Documentation
Kind/Enhancement
Kind/Event
Kind/Feature
Kind/Security
Meeting
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: rocky-linux/board#3
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We have a number of tickets in the Infrastructure team asking for resources of some kind--either for development work related to Rocky, or otherwise be support for some infrastructure they are looking to run in support of Rocky (e.g., automation around Peridot).
We need to be not blocking these, but also be good stewards of the resources we are given by our sponsors, and also heavily balance the security of the rest of our infrastructure. We should have guidelines as an organization on how we leverage our infrastructure--which is a tricky subject given that RL Infra is RESF Infra, by design and necessity.
I will work on a document which lays out what infrastructure Rocky provides in what situations