| # Gardening |
| |
| ## What is gardening? |
| |
| "Gardening" in open source projects refers to the background maintenance tasks done to keep the project healthy & growing & nice looking. |
| |
| This page lists common Go gardening tasks. |
| |
| ## Access |
| |
| If you've been regularly active in the Go community for some time, feel free to ask for Gerrit and/or Github access to modify things. |
| |
| See http://golang.org/wiki/GerritAccess and http://golang.org/wiki/GithubAccess |
| |
| ## Gardening Tasks |
| |
| Before doing any gardening work, especially on the issue tracker, remember to familiarize yourself with the issues life-cycle, described here: [Handling Issues - Issue States](https://github.com/golang/go/wiki/HandlingIssues#issue-states). |
| |
| ### Triage new bugs |
| |
| Look at the untriaged bugs. For Go, we use the presence of a Milestone field to mean that the bug has been triaged. To search for un-milestoned issues, use https://github.com/golang/go/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+no%3Amilestone |
| |
| While triaging the bug: |
| |
| * is it a duplicate? Close it, referencing the dup. |
| * is it a Question rather than a bug? Close it and reply with something like "For questions about Go, see https://golang.org/wiki/Questions." |
| * is the subject the correct format? It should start with the package path and a colon: "net/http: fix crash in Server during foo operation" |
| * is it in a subrepo? Set the milestone to "Unreleased". Unless it's a subrepo that goes into a release, like godoc or http2. |
| * if it is a regression and you can reproduce it, use git bisect to find the bad commit (optional but very helpful). |
| |
| See https://golang.org/wiki/HandlingIssues for how we use Github's issue metadata. |
| |
| ### WaitingForInfo |
| |
| Find bugs that are in state WaitingForInfo (https://github.com/golang/go/labels/WaitingForInfo) and ping them, remove the label when replies arrive, or close the bugs if a reply never arrived. |
| |
| ### "Unplanned" bugs" |
| |
| "Unplanned" issues have a habit of being neglected. Check out old ones and see if they're easily fixable (and can be moved to a Go1.n or Go 1.nMaybe milestone), or should be closed. |
| |
| These are the Unplanned bugs sorted by age, most stale ones first: https://github.com/golang/go/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20milestone%3AUnplanned%20sort%3Aupdated-asc%20-label%3AGo2%20-label%3ALanguageChange |
| ### Pending CLs |
| |
| Review the format of commit messages and presence of tests and formatting of code and typos/grammar in incoming pending CLs. All of that can be done without determining the correctness of the change itself. See https://dev.golang.org/release for the list of pending CLs. |
| |
| Once it has a +1, the owner of that area can give it a +2. |
| |
| Read a +1 as meaning "triaged", or "not obviously wrong". If it has tests, is formatted properly (references a bug number, probably), and is ready for more review, give it a +1. |
| |
| ### Pending CLs: ask about tests |
| |
| If a new CL arrives without a test, but could/should have a test, ask if they could add a test. Or suggest how. |
| |
| ### Pending CLs: run TryBots |
| |
| If you have access (see https://golang.org/wiki/GerritAccess) to run the TryBots and you see a CL with plausible (and non-malicious) code, kick off the TryBots. (We've never seen malicious code trying to escape our TryBot sandboxes, but that's why it's not automatic yet. Please alert us if you see something.) |
