Halp is a conversational ticketing solution for Internal Ops teams. We halp customers like Slack, Pinterest, and Strava track, automate, and humanize how they handle internal requests all inside Slack. We’re a seed stage company with a team of 12.
Technologies we use:
* React
* Typescript
* GraphQL + Apollo
* MongoDB
We’re hiring a senior full stack software engineer to join our team in Boulder or Denver, Colorado. To learn more, reach out to the email in my profile!
At Waffle.io, we're all about making project management better for engineers. We believe it's awesome that GitHub is investing in this too, and we'll continue to make GitHub delicious :). More here: http://blog.waffle.io/say-hello-to-wafflebot/
We're all about making it easier for dev teams to track their work, but keeping them close to their code. Waffle's core features - board view of your issues & PRs, multi repo support, metrics - are now free for all users on GitHub.
In the future we'll have paid add-ons to solve pain points for larger teams. But, for today, we believe making Waffle's core feature set free is the right path to helping more people on GitHub.com.
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.
