ioos / governance

Processes and procedures for management of the U.S. IOOS GitHub Organization (https://github.com/ioos)
Creative Commons Zero v1.0 Universal
0 stars 3 forks source link

Ticket template for transferring ownership of repo to IOOS #1

Open MathewBiddle opened 1 year ago

MathewBiddle commented 1 year ago

@mwengren @ocefpaf I was just reviewing this discussion [1] and started thinking about our governance for IOOS taking ownership of existing repositories. Maybe we should think about this and draft up some guidelines and a template ticket?

[1] https://github.com/asascience-open/nextgen-dmac/discussions/10#discussioncomment-3817479

mwengren commented 1 year ago

Sure, here are a few questions that come to mind. I'm there's other info we probably need too.

  1. What is the github handle of the person who should perform the transfer (Q: is it still true that whomever it is needs to have temporary admin rights on both the destination GH org and the source GH org or repository?)
  2. Should the name of the repo change when transferred? If so, what is the new name?
  3. Which IOOS team should be given commit rights? If no existing team is appropriate, which IOOS members should have commit rights?
  4. What GH services/tokens/actions need to be configured once transfered?

etc...