Give admin access to the captains on their own repositories

[bjohansebas]

When the transfer of iconv-lite was made, the question arose again whether captains should have admin access to their own repositories.
This is something that really should be given to captains, since a captain should be able to manage their repository’s settings without depending on a TC member. configuring branch rules, tag rules, and accessing the security reports for the repository they maintain.

If there is concern that a captain could delete or change the visibility of the repository, there are configurations that prevent those actions for admins and give them only to owners (I believe this is already applied in the three organizations):

Furthermore, the idea of captains is to delegate authority over the package to them. If there is worry about the potential damage a captain could do, they already have access to the package on npm. Allowing them to modify branch rules and view security reports in the repository shouldn’t be a big issue, Also, becoming a captain takes time, and the existing captains of the package need to believe that it’s time for the person to become a captain

I’m opening this so it isn’t forgotten in the meeting and to help captains depend less on TC members, until today, this is the first time a package has captains outside of the TC

[wesleytodd]

Just discussed on the working session. All good on this, it is what it was supposed to be all along. @UlisesGascon was doing an audit at one point, so lets just make sure he hasn't already been working on fixing these permissions. If not, I will go ahead and fix all the captain team permissions. We can close this when we address that.

[wesleytodd]

Everything good on this. We can do it as needed, or if someone wants to do a full audit they can. Do we need to leave this open or can we close it since it is agreed this is what it should have been?