Development Protocols

Social Protocols

We are committed to foster a vibrant thriving community, including growing a culture that breaks cycles of marginalization and dominance behavior. In support of this, some open source communities adopt Codes of Conduct. We are still working on our social protocols, and empower each team to describe its own Protocols for Inclusion. Until our teams have published their guidelines, please use the link above as a general guideline.

Coordination

• For task management we use Waffle or for the non-kan-ban view github's issues
• All tickets should be "bite-sized" i.e. no more than a week's worth of coding work. Larger tasks are represented in Milestones.
• Chat with us on Gitter or Slack
• We have a weekly dev-coord hangout on Tuesday's 9am PST/ 12pm EST

Test Driven Development

We use test driven development. When you add a new function or feature, be sure to add the tests that make sure it works. Pull requests without tests will most-likely not be accepted!

Code Formatting Conventions

All Go code must be formatted with gofmt. To make this easier consider using a git-hook or configuring your editor with one of these: (Emacs, vim, Sublime, Eclipse)

For Atom, you could try this package but it requires some configuration.