You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is mainly for @nipunreddevil and @oliparson ...
I've just stumbled across a service called HuBoard which is free for open source projects and allows us to easily prioritise and re-order github issues. I haven't looked deeply into this but it feels like a great idea for NILMTK becuase we have loads of open issues and it's hard to keep track of which issues need working on most urgently (and I might try it out soon on a private research project).
I'd be very interested if anyone has any experience with HuBoard or any other systems for easily prioritising github issues (and, no, github's 'Milestone' and 'Labels' features don't provide sufficient granularity or easy of re-ordering).
update
also, waffle.io looks good. And is free at the moment.
The text was updated successfully, but these errors were encountered:
JackKelly
changed the title
Sorting NILMTK github issues
Sorting NILMTK github issues using HuBoard?
Feb 27, 2015
JackKelly
changed the title
Sorting NILMTK github issues using HuBoard?
Sorting NILMTK github issues using external tool?
Mar 10, 2015
This is mainly for @nipunreddevil and @oliparson ...
I've just stumbled across a service called HuBoard which is free for open source projects and allows us to easily prioritise and re-order github issues. I haven't looked deeply into this but it feels like a great idea for NILMTK becuase we have loads of open issues and it's hard to keep track of which issues need working on most urgently (and I might try it out soon on a private research project).
I'd be very interested if anyone has any experience with HuBoard or any other systems for easily prioritising github issues (and, no, github's 'Milestone' and 'Labels' features don't provide sufficient granularity or easy of re-ordering).
update
also, waffle.io looks good. And is free at the moment.
The text was updated successfully, but these errors were encountered: