How to be a maintainer with merge permission about eos-go HOT 3 CLOSED

Hmmm, we don't have a plan for PRs. If you see some dangling, take them one. If you see things evolving in the community where we aren't tracking as closely (I'm thinking new RPC endpoints that might have been added), you could update the lib to support them.

from eos-go.

@maoueh what do you think? ;-)

Psy, can you finalize a few of the PRs, participate in there, we'll merge one or two, we'll see how you work, and then we grant permissions?

Also, perhaps post this GH issue in a few channels where people know you, and they can vouch for you? We know quite a few folks from that community, we should be able to make a quick decision.

Quite a few projects rely on this repo, and it's a core repo, you'll understand we need to trust but verify ;-)

from eos-go.

I should've asked as like "For being a maintainer, which condition should I meet & which step would be needed" 😅
If the question make you embarrassed, sorry for my impliteness and it should be more careful.

After a dApp builder (named LangChain) & EOSIO hackathon mentor/participant in 2018, I was away from EOSIO. So issue raisers could not know nor vouch me.
I met Yves and Damian from ENF (Damian is not employed but in the grant committee) a few weeks ago and talked about a contribution. And I thought that dedicately maintained Go SDK seems not yet exist and it could be a contribution point. But they found this repo and it had been maintained awesome by team-level work, though a little bit outdated recently.

Even I've never thought I can be granted immediately but want to know your procedure. And finalizing PR would be the best point to enter & practice the code.
In the middle of that, I have one question about "finalizing PR" - would it be a guide to the contributor, or a few direct commits from me?

from eos-go.