status-im
/
burnchart
mirror of https://github.com/status-im/burnchart.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

waffle

This commit is contained in:
Radek Stepan 2014-10-17 21:29:42 -07:00
parent dc3a871ad6
commit 07aae10c2e
2 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -21,6 +21,7 @@ GitHub Burndown Chart as a service. Answers the questions "are my projects on tr
- payments need to be automatic, why penalize users that are loyal to us with a burden of an admin task? - payments need to be automatic, why penalize users that are loyal to us with a burden of an admin task?
- ability to use the program needs to be frictionless; jump straight into the action, fill in data behind the scenes etc. - ability to use the program needs to be frictionless; jump straight into the action, fill in data behind the scenes etc.
- send reminders to people whose account is expiring - send reminders to people whose account is expiring
- [Waffle](https://waffle.io/) from Rally software has a kanban board that will support [burnup chart](https://waffle.io/waffleio/waffle.io/cards/53e5347682b317f7d9ad6eac); it will charge $7/month
##Plans ##Plans

3
TODO.md
View File

@ -44,6 +44,8 @@
- [ ] show a countdown clock towards the end of the milestone or show overdue - [ ] show a countdown clock towards the end of the milestone or show overdue
- [ ] trigger success topbar when we have completed a milestone on chart page; show plain when we are behind - [ ] trigger success topbar when we have completed a milestone on chart page; show plain when we are behind
- [ ] on chart page show a little progress bar in the title - [ ] on chart page show a little progress bar in the title
- [ ] add a chart straight from the hero banner
- [ ]
##Backlog ##Backlog
@ -125,3 +127,4 @@
- [ ] if we save user's tokens we could check data on their behalf, then messaging would work; API could be provided so that others could plug into the data - [ ] if we save user's tokens we could check data on their behalf, then messaging would work; API could be provided so that others could plug into the data
- [ ] derive insights; one part is to see if we are on track, the other is to get better at estimating. If we know when an issue is worked on and when closed, with its accompanying size, we can say which issues went well, and which fared poorly. Then we can visualize a weekly/monthly/per-milestone list of loosers and winners. Perhaps the user can glean a pattern from that. - [ ] derive insights; one part is to see if we are on track, the other is to get better at estimating. If we know when an issue is worked on and when closed, with its accompanying size, we can say which issues went well, and which fared poorly. Then we can visualize a weekly/monthly/per-milestone list of loosers and winners. Perhaps the user can glean a pattern from that.
- [ ] create fake Firebase endpoint for GitHub auth, or change the endpoint in settings (easier) - [ ] create fake Firebase endpoint for GitHub auth, or change the endpoint in settings (easier)
- [ ] have an icon that shows a progress for a milestone that can be shown on GitHub README page