burnchart/README.md

64 lines
2.9 KiB
Markdown
Raw Normal View History

2014-10-30 18:36:40 -06:00
*Existing users: The url mapping has been preserved from the original app, we are just using a different domain. If you'd like to use the previous version(s), grab the tags `v1`, `v2`.*
2014-11-10 19:16:52 -07:00
#[burnchart](http://radekstepan.com/burnchart)
2014-09-01 20:28:28 -07:00
2014-10-30 22:41:41 -06:00
GitHub Burndown Chart as a Service. Answers the question "are my projects on track"?
2014-09-01 21:54:20 -07:00
2014-11-10 20:12:43 -07:00
![Build Status](http://img.shields.io/codeship/5645c5d0-4b7e-0132-641d-623ee7e48d08.svg?style=flat)
2014-11-10 19:16:52 -07:00
[![Coverage](http://img.shields.io/coveralls/radekstepan/burnchart/master.svg?style=flat)](<https://coveralls.io/r/radekstepan/burnchart>)
[![Dependencies](http://img.shields.io/david/radekstepan/burnchart.svg?style=flat)](https://david-dm.org/radekstepan/burnchart)
2014-10-28 22:56:37 -06:00
[![License](http://img.shields.io/badge/license-AGPL--3.0-red.svg?style=flat)](LICENSE)
2014-11-10 19:16:52 -07:00
![image](https://raw.githubusercontent.com/radekstepan/burnchart/master/public/screenshots.jpg)
2014-10-30 18:36:40 -06:00
##Features
2014-10-31 23:12:37 -06:00
1. Running from the **browser**, apart from GitHub account sign in which uses Firebase backend.
1. **Private repos**; sign in with your GitHub account.
1. **Store** projects in browser's `localStorage`.
1. **Off days**; specify which days of the week to leave out from ideal burndown progression line.
1. **Trend line**; to see if you can make it to the deadline at this pace.
1. Different **point counting** strategies; select from 1 issues = 1 point or read size from issue label.
2014-10-30 18:36:40 -06:00
##Configuration
At the moment, there is no ui exposed to change the app settings. You have to edit the `src/models/config.coffee` file.
An array of days when we are not working where Monday = 1. The ideal progression line won't *drop* on these days.
```coffeescript
"off_days": [ ]
```
Choose from `ONE_SIZE` which means each issue is worth 1 point or `LABELS` where issue labels determine its size.
```coffeescript
"points": "ONE_SIZE"
```
2014-10-30 20:01:11 -06:00
If you specify `LABELS` above, this is the place to set a regex used to parse a label and extract points size from it. When multiple matching size labels exist, their sum is taken.
2014-10-30 18:36:40 -06:00
```coffeescript
"size_label": /^size (\d+)$/
```
2014-11-02 21:22:33 -07:00
##Commands
2014-10-30 18:36:40 -06:00
2014-11-01 18:42:39 -06:00
Read the [Architecture](docs/ARCHITECTURE.md) document when contributing code.
2014-10-30 18:36:40 -06:00
```bash
2014-11-02 21:22:33 -07:00
rake build # Build everything & minify
rake build:css # Build the styles with LESS
rake build:js # Build the app with Browserify
rake build:minify # Minify build for production
rake commit[message] # Build app and make a commit with latest changes
rake install # Install dependencies with NPM
rake publish # Publish to GitHub Pages
rake serve # Start a web server on port 8080
rake test # Run tests with mocha
rake test:coverage # Run code coverage, mocha with Blanket.js
rake test:coveralls[token] # Run code coverage and publish to Coveralls
rake watch # Watch everything
rake watch:css # Watch the styles
rake watch:js # Watch the app
2014-10-30 18:36:40 -06:00
```