github.com/compliance-trestle estate

[butler54]

Early on in the project I grabbed github.com/compliance-trestle to minimise risk of conflicting / confusing projects.

Currently the org is used to host compliance-trestle.github.io that redirects to the former home of compliance-trestle: https://github.com/ibm/compliance-trestle.

Given that compliance-trestle is the largest project on this org I recommend the followowing:

1. Repoint from https://github.com/ibm/compliance-trestle to https://github.com/oscal-compass/compliance-trestle.
2. Transfer ownership to the either the maintainers of the oscal-compass or or the oscal-compass/community project.
3. Update the community org to reflect the governance requirements.

Alternatives:

• I delete organisation completely with the associated risk of squatting
• I retain ownership (which I think is not the best practice medium term).

[jpower432]

Hi @butler54 - I agree with your recommendation. Thanks for submitting this issue. I will allow the other reviewers to weigh in to see if there are differing perspectives.

[jflowers]

Hi @butler54 I too agree. We have it on the agenda for our next oversight committee meeting.

[butler54]

Okay i'll add the redirect now, however, if we could get some comms out on who should be org-owners it would be appreciated.

[butler54]

Updated: compliance-trestle/compliance-trestle.github.io@66508ae

[jpower432]

@butler54 We were not able to cover this in the last committee meeting, but I think org owners could probably mirror the org admins here. Do you agree @mrgadgil @jflowers @vikas-agarwal76? I think it may be worth checking with the folks at CNCF to see if the organization would need to be added to the Enterprise Account.

[butler54]

i can add people, however, it might make sense just to trigger the migration to the CNCF