-
-
Notifications
You must be signed in to change notification settings - Fork 232
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
Transfer ownership of infrastructure #481
Comments
@zmitchell we should list what infrastructure we're talking about. |
I moved the list to the issue description. I also removed the |
Done! |
The reasoning is: - domenkozar has transferred ownership of the infrastructure #481 - unless someone is a team lead (as is the case for zmitchell), we (people with write access to nix.dev) should all be able to merge PRs
@domenkozar as shown by the linked PR, the transfer is still not 100% complete 😅 |
The reasoning is: - domenkozar has transferred ownership of the infrastructure #481 - unless someone is a team lead on a specific sub-team (as is the case for zmitchell), we (people with write access to nix.dev) should all be able to merge PRs
I don't think it's related to the transfer, but it you want to keep it open that's fine. |
You're right, I'll close this and open a separate issue for the |
The reasoning is: - domenkozar has transferred ownership of the infrastructure #481 - All the doc team members should get pinged for changes, let's see how it goes for some time, we can make it more specific later Co-Authored-By: @infinisil, @fricklerhandwerk, @proofconstruction
The reasoning is: - domenkozar has transferred ownership of the infrastructure #481 - All the doc team members should get pinged for changes, let's see how it goes for some time, we can make it more specific later Co-Authored-By: @infinisil, @fricklerhandwerk, @proofconstruction
If we want to implement new infrastructure or make changes we need to transfer ownership of the infrastructure. We also need to decide who to transfer ownership to.
Depends on: #262
The text was updated successfully, but these errors were encountered: