Contributing to cgm-remote-monitor

Design

Participate in the design process by creating an issue to discuss your design.

Develop on `dev`

We develop on the dev branch. You can get the dev branch checked out using git checkout dev.

Style Guide

Some simple rules, that will make it easier to maintain our codebase:

All indenting should use 2 space where possible (js, css, html, etc)
A space before function parameters, such as: function boom (name, callback) { }, this makes searching for calls easier
Name your callback functions, such as boom('the name', function afterBoom ( result ) { }
Don't include author names in the header of your files, if you need to give credit to someone else do it in the commit comment.
Use single quotes.

Use the comma first style, for example:

var data = {
  value: 'the value'
  , detail: 'the details...'
  , time: Date.now()
};

Create a prototype

Fork cgm-remote-monitor and create a branch. You can create a branch using git checkout -b wip/add-my-widget. This creates a new branch called wip/add-my-widget. The wip stands for work in progress and is a common prefix so that when know what to expect when reviewing many branches.

Submit a pull request

When you are done working with your prototype, it can be tempting to post on popular channels such as Facebook. We encourage contributors to submit their code for review, debate, and release before announcing features on social media.

This can be done by checking your code git commit -avm 'my improvements are here', the branch you created back to your own fork. This will probably look something like git push -u origin wip/add-my-widget.

Now that the commits are available on github, you can click on the compare buttons on your fork to create a pull request. Make sure to select Nightscout's dev branch.

Comments and issues

We encourage liberal use of the comments, including images where appropriate.

Co-ordination

Most cgm-remote-monitor hackers use github's ticketing system, along with Facebook cgm-in-the-cloud, and gitter.

We use git-flow, with master as our production, stable branch, and dev is used to queue up for upcoming releases. Everything else is done on branches, hopefully with names that indicate what to expect.

Once dev has been reviewed and people feel it's time to release, we follow the git-flow release process, which creates a new tag and bumps the version correctly. See sem-ver for versioning strategy.

Every commit is tested by travis. We encourage adding tests to validate your design. We encourage discussing your use cases to help everyone get a better understanding of your design.

Other Dev Tips

Join the Gitter chat
Get a local dev environment setup if you haven't already
Try breaking up big features/improvements into small parts. It's much easier to accept small PR's
Create tests for your new code, and for the old code too. We are aiming for a full test coverage.
If your going to be working in old code that needs lots of reformatting consider doing the clean as a separate PR.
If you can find others to help test your PR is will help get them merged in sooner.

5.0 KiB Raw Blame History