github.com/wallyworld/juju@v0.0.0-20161013125918-6cf1bc9d917a/FAQ.txt (about) 1 2 3 4 Q: I want to get involved. Where should I start? 5 A: Read the docs. They're not complete (feel free to contribute), but 6 they help. Suggested reading order: 7 8 1. README 9 2. CONTRIBUTING 10 3. doc/architectural-overview.txt 11 4. doc/how-to-write-tests.txt 12 5. the other docs in doc/ 13 14 Many of the docs in the doc/ directory become progressively more clear 15 as you begin actually working in the code. Keep re-reading them 16 periodically to gain more benefit. 17 18 19 20 Q: How do I find out what's going on currently? How does the juju-core 21 team communicate regularly? 22 A: IRC. Mailing Lists. Code Reviews. 23 24 1. IRC: most day-to-day discussion happens in #juju-dev on freenode. 25 2. Mailing Lists: [juju-dev](https://lists.ubuntu.com/mailman/listinfo/juju-dev) 26 3. Code Reviews. These are likely to change very soon, but 27 historically these have happened in codereview.appspot.com, and 28 they're initiated using the lbox tool referred to in the CONTRIBUTING 29 doc. 30 31 32 33 Q: How do I run only specific test suites using gocheck? 34 A: The quick answer is that the -gocheck parameters must be *last* on the 35 command line, for example: 36 37 go test -v ./state -gocheck.v -gocheck.f="StateSuite|CleanupSuite" 38 39 Also, if you want to use -gocheck.v or -gocheck.vv, you must also provide 40 the -v option to go test, otherwise the -gocheck.v* options are silently 41 ignored. 42 43 Additionally, you can only specify -gocheck.f filters on one package at 44 a time. If you use the go test ellipsis (./...) it will ignore your 45 filter strings. 46 47 48