1- # Contributing to doit
1+ # Contributing to doctl
22
33** First:** if you're unsure or afraid of _ anything_ , just ask
44or submit the issue or pull request anyways. You won't be yelled at for
55giving your best effort. The worst that can happen is that you'll be
66politely asked to change something. We appreciate any sort of contributions,
77and don't want a wall of rules to get in the way of that.
88
9- However, for those individuals who want a bit more guidance on the
9+ However, for those people who want a bit more guidance on the
1010best way to contribute to the project, read on. This document will cover
1111what we're looking for. By addressing all the points we're looking for,
1212it raises the chances we can quickly merge or address your contributions.
@@ -22,14 +22,14 @@ it raises the chances we can quickly merge or address your contributions.
2222 of the * entire* generated crash log for us to look at. Double check
2323 no sensitive items were in the log.
2424
25- * Respond as promptly as possible to any questions made by the _ doit _
25+ * Respond as promptly as possible to any questions made by the _ doctl _
2626 team to your issue. Stale issues will be closed.
2727
2828### Issue Lifecycle
2929
30301 . The issue is reported.
3131
32- 2 . The issue is verified and categorized by a _ doit _ collaborator.
32+ 2 . The issue is verified and categorized by a _ doctl _ collaborator.
3333 Categorization is done via tags. For example, bugs are marked as "bugs".
3434
35353 . Unless it is critical, the issue is left for a period of time (sometimes
@@ -43,13 +43,13 @@ it raises the chances we can quickly merge or address your contributions.
4343 the issue tracker clean. The issue is still indexed and available for
4444 future viewers, or can be re-opened if necessary.
4545
46- ## Setting up Go to work on doit
46+ ## Setting up Go to work on doctl
4747
4848If you have never worked with Go before, you will have to complete the
49- following steps in order to be able to compile and test doit .
49+ following steps in order to be able to compile and test doctl .
5050
51- 1 . Install Go. Make sure the Go version is at least Go 1.4 .
52- Go 1.4. On a Mac, you can ` brew install go ` to install Go 1.4 .
51+ 1 . Install Go. Make sure the Go version is at least Go 1.6 .
52+ On Mac OS X , you can ` brew install go ` to install Go 1.6 .
5353
54541 . Set and export the ` GOPATH ` environment variable and update your ` PATH ` .
5555 For example, you can add to your ` .bash_profile ` .
@@ -59,7 +59,7 @@ following steps in order to be able to compile and test doit.
5959 export PATH=$PATH:$GOPATH/bin
6060 ```
6161
62- 1. Make your changes to the doit source, being sure to run the basic
62+ 1. Make your changes to the doctl source, being sure to run the basic
6363 tests.
6464
65651. If everything works well and the tests pass, run `go fmt` on your code
0 commit comments