Disclaimer: I don't have experience with @namusyaka's contributions outside of x/net/html.

As for x/net/html, please correct me if https://go-review.googlesource.com/q/owner:namusyaka%2540gmail.com+project:net+html is missing any of your contributions.

How will gaining the approver bit change things, in practice? Code changes (in the Go main repo and under x) still need to be reviewed before being committed. Currently, those reviewers (i.e. me for substantial changes, @bradfitz and maybe others for small changes or rollbacks) can approve and submit as soon as they're happy from a code review perspective. Conversely, even if you had the approver bit, you'd still have to wait for a code reviewer to sign off.

Also, the approval bit generally implies familiarity with the code they're approving for. On the other hand, https://go-review.googlesource.com/c/net/+/94838 is a recent change of yours, which had lots of review comments. I'm not saying that you're a bad programmer. Even good programmers miss some things when modifying unfamiliar code. Not every nuance is captured in the code itself, its nearby comments and the test suite, and sometimes you just need to know what far-away documentation is relevant (or missing!). I'm just saying that you're not yet completely familiar with the subtleties of the x/net/html package. That familiarity will surely grow over time, the more you work with it, but I don't think you're there yet, now.

Sorry to sound negative. I appreciate the work you're doing in x/net/html, and I would like to see it continue. I'm just concious of the risk, in terms of operational security or otherwise, of handing out approver bits, and we don't have the technical capability to limit the approval bit to subsets of the repos, e.g. "just x/net/html".

I'll repeat that I'm not familiar with your other work, such as in cmd/compile and net/http, which may very well be in favor of us granting you the approval bit. I'm only just one opinion on this issue, specifically for you and generally in terms of policy, and am happy for other people to have different opinions.

@nigeltao I appreciate your comment.

Please let me supplement some.

How will gaining the approver bit change things, in practice?

Currently, the parser of the x/net/html package contains a lot of code (after reviewing, of course) that I implemented. On the contrary, it was a statement that I am willing to sustainably maintain.
However, as you say, I am not a familiar with all of the x/net/html package.

And I have been doing continuous contributions (probably go 20+ commits + other packages => 40+ commits) from last year on other packages and gardening some issues, but it is hard to say that I am perfectly familiar with cmd/compile or net/http.
Even if I get the bit, I understand that reviewing my own patch is obviously essential.
If there is one merit, it will be able to smoothly perform bug fixes from others on the code that I created.

I don't know the clear criteria to get the bit (or unexistence?).
But anyway, I will continue to commit to go and its subpackages.

Thanks.