Awesome, I am a trello fan. Too bad this didn't exist a year ago. Already migrated to JIRA because Github issues was so underpowered. I'd use it otherwise. :(
onclick on the "Go!" button is broken - it's incorrectly referencing the goToURL function as gotoURL. To get past it, use Enter on keyboard instead of the button. (Using jQuery, yet inline event definitions?)
I'm going to test this right away for Docker. We are completely overwhelmed with github issues, and the bottleneck is not contributors: it's our ability to communicate where we need the most help.
Tags do help. Our problem is the sheer volume of issues - 260 currently open and counting [1]. So prioritizing becomes an issue, as well as the unbarably slow web ui.
Based on the email at the bottom of the page, looks like this is from the http://rallydev.com folks? I hope they have plans for an internal/private version, because while I'm not sure I'd use this for my open source projects, I'd love to try it for our internal repos.
It's built by a team of interns at Rally. We'd love to know why you'd use it for private repos but not open source projects, hoping to help people know where they can start contributing to an open source project.
I think this could be used by staff that aren't familiar with github/scared of it (this is more common than you think) to manage issues in a simple and familiar way. I think it would certainly be helpful in my organization, but like GP our repos are private.
Having people know how to start contributing is not an issue I've had with my OSS projects; that could just be me though.
Keeping straight what stage the Issues in our private repos are in, though - that's a very real problem I deal with every day. I'd love to be able to surface our internal company flow in a simple way like this; it's very kanban-like, and doesn't require us to add another tool or try to keep things in sync since it sits right on top of Github Issues which we already use.
27 comments
[ 4.8 ms ] story [ 72.0 ms ] threadAnd if you do that, consider taking a page from the Sprint.ly playbook..only charge for months the user actually uses your service.
http://waffle.io/jashkenas/backbone
[1] https://github.com/dotcloud/docker/issues?direction=desc&sor...
An error occurred in the application and your page could not be served. Please try again in a few moments.
If you are the application owner, check your logs for details.
Keeping straight what stage the Issues in our private repos are in, though - that's a very real problem I deal with every day. I'd love to be able to surface our internal company flow in a simple way like this; it's very kanban-like, and doesn't require us to add another tool or try to keep things in sync since it sits right on top of Github Issues which we already use.
Application Error
An error occurred in the application and your page could not be served. Please try again in a few moments.
If you are the application owner, check your logs for details.