You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, if a maintainer is added to a GitHub repo or removed, buttons are pushed by one of the GH InstructLab project owners and a script can be run to update our project wide Maintainers.md file. However, this does not update settings on other project infrastructure, e.g. mailing lists (run via Google Groups).
We need to document the procedural bits for when someone is added or steps down as a maintainer. The contributor ladder is a great start but lacks these nuts and bolts details.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity within 90 days. It will be automatically closed if no further activity occurs within 30 days.
Right now, if a maintainer is added to a GitHub repo or removed, buttons are pushed by one of the GH InstructLab project owners and a script can be run to update our project wide Maintainers.md file. However, this does not update settings on other project infrastructure, e.g. mailing lists (run via Google Groups).
We need to document the procedural bits for when someone is added or steps down as a maintainer. The contributor ladder is a great start but lacks these nuts and bolts details.
The text was updated successfully, but these errors were encountered: