-
Notifications
You must be signed in to change notification settings - Fork 139
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
Remove automation teams and archive the automation repo #488
Comments
+1 on deleting these teams and on creating a ncu team |
+1 |
1 similar comment
+1 |
Should https://github.com/nodejs/node-auto-test be archived as well? |
I think we should keep it. I believe @mmarchini has used it recently to try out some GitHub Actions related things and it would be the ideal place to trial any work towards a commit queue. |
+1 on keeping node-auto-test |
nodejs/node-core-utils has been created a while back. I have archived the automation and deleted the automation teams. |
As explained in nodejs/Release#547 (comment)
The automation team was created so that we can ping a group of people for work/reviews/ideas about automation, but it is too big and rarely used at this point. Instead we tend to just open issues/PRs in https://github.com/nodejs/node-core-utils (which is somewhat like a mono repo now where new tools are being added) where the we talk about more concrete ideas and work on actual code.
I think it's time to remove the following teams
And just assign collaborators to different projects when necessary - or when the team grows big enough, create teams for each project. So in addition I propose to create
To manage https://github.com/nodejs/node-core-utils
In addition I think it's also time to archive https://github.com/nodejs/automation - it was good for what we tried to do back then but now most of the activities happen in node-core-utils.
cc @nodejs/tsc
The text was updated successfully, but these errors were encountered: