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.
Show HN: Trello for GitHub Issues
21–28 of 28 posts
Re: Show HN: Trello for GitHub Issues
#22Also see http://huboard.com/ .
Re: Show HN: Trello for GitHub Issues
#23Very nice. It's fun to look at Backbone.js' issues list from within a Backbone app ;) http://waffle.io/jashkenas/backbone
Re: Show HN: Trello for GitHub Issues
#24Application 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.
Re: Show HN: Trello for GitHub Issues
#25Also see http://huboard.com/ .
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.
Re: Show HN: Trello for GitHub Issues
#26http://waffle.io/rallysoftware/waffle.io : 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.
Re: Show HN: Trello for GitHub Issues
#27Does this work with private repos? If so then SHUT UP AND TAKE MY MONEY!
And if you do that, consider taking a page from the Sprint.ly playbook..only charge for months the user actually uses your service.
Re: Show HN: Trello for GitHub Issues
#28Based 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.
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.