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