-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update New Project Playbook #61
base: main
Are you sure you want to change the base?
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
|
||
- [ ] 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for improving the workflow Daniel!
No description provided.