Conversation
# Conflicts: # README.md
|
@cunla and @tim-schilling these look like great changes! It makes the process a little more clear and does a great job of calling out who needs to do what, and in what order 💯 |
| ### Pre Transfer Steps | ||
|
|
||
| - [ ] Check if the repository meets [inbound requirements][3]. | ||
| - [ ] Confirm who will be the admins and maintainers for the repository |
There was a problem hiding this comment.
Extra thoughts from my notes
- Consider removing any admins that are no longer active
- Make sure the current contributors with some form of write access are members of Django Commons. Alternatively, they can apply for membership later and be added to the repository again.
There was a problem hiding this comment.
Removing admins/collaborators manually no longer needed, it will be done as part of the terraform import process - see this PR: django-commons/membership#98
| ### Make GitHub repository managed by terraform | ||
|
|
||
| - [ ] Terraform changes to add project to organization | ||
| - [ ] Terraform changes to add project to organization, should be included in the issue opened to transfer the project. |
There was a problem hiding this comment.
I have written in my notes to discuss our use of Terraform. For example, most changes normally done through the GitHub UI should now be done using Terraform. Adding new members for example.
Co-authored-by: Storm Heg <[email protected]>
tim-schilling
left a comment
tim-schilling
left a comment
There was a problem hiding this comment.
Thank you for improving the workflow Daniel!
Stormheg
left a comment
Stormheg
left a comment
There was a problem hiding this comment.
Thanks Daniel - happy with this 👍
5 participants
No description provided.