Show HN: Zube.io – Simple project management for your GitHub issues
zube.io
zube.io
https://help.github.com/articles/about-third-party-applicati...
I'd love to explore this further with you.
As of now I don't think it's possible.
They're aware of the demand and I assume it would exist if it was practical without moving mountains. More background: http://help.tacoapp.com/connectors/github-issues.html#access..., https://github.com/tacoapp/privacy-policy#conservative-defau...
Some suggestions on other integrations... Stash, GitLab, BitBucket, Github Enterprise... Stash and GH Enterprise might be more difficult.
Honestly, I'd suggest working towards a solution to work with GH Enterprise, as that would probably align with your current structure better, it may be the most work, but it would be a point to more potential large business customers, and a better revenue model.
Some of us have been waiting a while for a competing service to provide this support.
[1] https://gitlab.com/ [2] https://github.com/waffleio/waffle.io/issues/926
We'd been using Github Issues previously but found it hard to prioritize our tickets in a way that was natural for us. The ability to drag and drop reorder our backlog has really helped with that.
Also, the UI works well for quick updates during our morning standup.
The process for creating the images is as follows:
Use quicktime to take a video, called demo.mov (or equivalent movie capture program with whatever file format)
Create a color palette from the movie $ ffmpeg -i demo.mov -vf fps=10,scale=1378:-1:flags=lanczos,palettegen palette.png
Create a gif from the movie using the color palette $ ffmpeg -i demo.mov -i palette.png -filter_complex "fps=10,scale=1378:-1:flags=lanczos[x];[x][1:v]paletteuse" output.gif
Create a sequence of pngs from the gif $ convert -dispose Background -coalesce output.gif -colors 256 PNG8:target-%d.png
party!
Feel free to email us if you need any help!
Only problem is I can't figure out how to edit the content of an issue once I opened the card?
Edit: Also trying to figure out how the Review state work compared to Waffle.
I'm not sure what you mean by your second question. On Zube, the In Review doesn't have a concrete meaning, that is, it doesn't affect the card's state beyond who the issue is assigned to. At Zube, we use the Review column for cards that we have completed but still need to test, have code reviewed or just want to keep an eye for unknown bugs.
At first glance, I believe this will give me and my team better insights into what everyone on the engineering team is up to.
The devs have been really receptive to our feedback, which seems self-evident in this thread.
Comments - syntax highlighting; @mentions, emojis, issue reference autocomplete; live updating from GitHub comments for things like comment updates and deletes (so your data is consistent)
Cards - Commit references, events, and card references. Consistency of data, especially when multiple users are moving cards at the same time.
Boards - add and remove users from the board
Labels - create, update, and delete labels from a repo (not just a card)
Milestones - create, update, and delete labels from a repo (not just a card)
Zube also has many UX features that differ from Waffle like each user having their own row. Creating cards in any row/column. Dedicated views for each milestone.
Waffle has some features that Zube doesn't support right now like burndown charts and search. I'm not an expert on Waffle or anything so please correct me if I'm in error. It's kinda hard to know everything that a competitor does.
We've had the request for multiple repos on one Zube board when talking with PMs and consulting firms and we're aware that it's important for them. However, we're laser focused on making developers happy and they've told us that they care more about managing issues for a single repository, so we implemented that first.
Also Zube is fast :)
You can see our focus on developers by the layout of our board, which is more scrum style than kanban. Each developer has their own row. It makes it easy to see exactly what your tasks are. You can also assign issues by dragging the card over to the user's row, something that isn't possible with a kanban board like ZenHub. We care less about getting an overview of the whole project (what PMs care about) and more about what needs to be done (what devs care about)
We'll continue adding features that make developers happy whether they would fit into the GitHub Issues paradigm or not.
I have a question: how can I view all issues? It seems I can only view issues without a milestone and issues in a milestone separately.
For reference: http://www.plusfortrello.com/p/about.html
EDIT: To clarify, since it's being used as a timesheet, we need a timer.
Hi sep332!
I made a new product, Zube https://zube.io . It's a
simple project management tool for GitHub issues.
I've been working on it with my cofounder for 6 months.
I'm super excited to announce that we're launching
Zube today on Hacker News. You can read more about why
we made it here - https://zube.io/blog .
Hope you check it out and let me know what you think!
Cheers,
Jen
You know this kind of spam is literally illegal, right?I don't mean to spam anyone and I'll remove you from my list.
Edit: To be clear, I only sent emails to people who have given me their emails previously. I didn't scrape them from the internet.
Sorry again!
Edit: Well if I signed up for your emails before, it's not so bad. But without a one-click unsubscribe link, I think it's still in violation of the CAN-SPAM act.