Go Wechaty project initialized!

[huan]

See: wechaty/wechaty#1927

[huan]

In reply to #20

Hi all, I really appreciate all the efforts that you guys made, the progress of our Go Wechaty is fantastic!

Current our Go team members include @dchaofei , @dingdayu , and @SilkageNet , which I believe all of you guys are Go masters who have a great experience of writing the Go code.

In the contract, I have a very limited Go experience. To be honest, I should say ZERO because I only write some kind of the Hello World in Go.

According to the above facts, I believe the best way to drive the Go Wechaty code base growth, is to let the people who really know Go to make all the decisions, and it's also because I trust our contributors.

After thinking about that, I feel it will be great to grant the write privilege to our core contributors so that we will be able to work on the code more smoothly. So I have configured this repository to the following settings, and let's continue working with those settings for a few weeks and to see if it's ok for us, and also try to find out how to improve it to better fit our needs.

Repo Settings for Core Contributors

The Roles

1. All @wechaty/contributors have Role of Triage, which can manage Issues and PRs.
2. All @wechaty/go have Role of Write, which can push commits to the repository.

   except the master, see Branch protection rules above

The Branch Protection

1. master branch has been protected, which means we can only merge PR to it
2. Require pull request reviews before merging, required approving reviews is set to 2
3. Require status checks to pass before merging, which means the CI must turn green

Please feel free to manage the Issues and Pull Requests as you want when you believe it's the best practice, and everything is right. Especially, please help each other by adding your reviews to other's Pull Request, and approve it after you believe everything is OK.

Any suggestions/comments will be welcome by commenting on this issue.

[huan]

Link to wechaty/PMC#28