Live data from Hacker News

Waffle.io

waffle.io

41–50 of 66 posts

Re: Waffle.io

#41
post #40

Earlier quoted context omitted.

I think that's being rather harsh - to me it's trying to link a Trello style community/team tool on top of Github. And as someone who has tried to get a largish team, including non developers, to collaborate using existing Github features this might well be a good idea. Also the name - very few domain names seem to have much connection with the domain anymore, picking on this crowd for having a weird domain name hard…

Thanks. :) I posted this below, but in case you missed it, we agree. We have a new landing page getting ready to launch. Here's a preview of what we're working towards: http://screencast.com/t/IZnoWChXyQ

We love Github Issues at our company, but it's missing one thing we really need: metrics. We need to track when a milestone was started, who completed how many issues in a milestone, what was the issue estimated at and what was to actual time to complete. We need data on what there is to be done and what will be done.

That being said, I don't think this is a feature set for Github issues. This is not an open source concern; it's a business concern and I don't think business should drive Github.

So a third party integration is perfect for this. Is this something on the roadmap of waffle.io?

Re: Waffle.io

#42
post #35
post #32

Earlier quoted context omitted.

[deleted]

Congratulation, you don't understand people at all. You wrote all this non-constructive frothy reply without answering the fundamental question holyjaw put forth: > I have literally no clue what your product does even after reading the infographic at the top of the page a few times.

Tank you.

Re: Waffle.io

#43

This is wonderful. The main page doesn't mention the term, but the easiest way to describe this is that it is adding a Kanban board to Github. http://en.wikipedia.org/wiki/Kanban_board The simplicity to effectiveness ratio of Kanban boards really impress me.

Huboard http://huboard.com is the Kanban board my employer uses for github and its pretty nice. It'll autoupdate if any team member changes the board.

There's also TaskTub: http://www.tasktub.com/

Re: Waffle.io

#44
post #40

Earlier quoted context omitted.

Thanks. :) I posted this below, but in case you missed it, we agree. We have a new landing page getting ready to launch. Here's a preview of what we're working towards: http://screencast.com/t/IZnoWChXyQ

We love Github Issues at our company, but it's missing one thing we really need: metrics. We need to track when a milestone was started, who completed how many issues in a milestone, what was the issue estimated at and what was to actual time to complete. We need data on what there is to be done and what will be done. That being said, I don't think this is a feature set for Github issues. This is not an open source c…

Yep. We're definitely looking at adding more planning functionality and metrics around milestones in the near future.

Re: Waffle.io

#45
post #2

I would urge you to take another look at the flow of your landing page. I have literally no clue what your product does even after reading the infographic at the top of the page a few times. - GitHub users want a way to help out on open source projects - waffle.io places a dynamic badge in your GitHub README file for all to see where they can help - Clicking that badge takes anyone to your public waffle.io board wher…

I strongly dislike everything about waffle.io. I feel bad about it, because these are good people who more than likely love their product and it's getting a lot of hate here despite them coming here to respond to feedback... but. 1. Most people here are confused about what this is for. After understanding what it's for, I find that it's not even a solution looking for a problem... it's a force-fed solution to a non-e…

I think the name is because you end up with a grid of cards. It's a pretty tenuous link though.

Re: Waffle.io

#46
I think this is a fantastic idea. I've often felt that the Github issues page is too uninviting for non-developers (and that may be okay for lots of projects) but it's obvious to me how beneficial it is to provide a kanban interface for end-users that ties directly to the github issues.

Re: Waffle.io

#47
You need to clean up the wording some. When I first read

  Clicking that badge takes anyone to your public
  waffle.io board where users can view and edit tasks.
It sounds like random github users can decide what tasks get worked on. "Users" is vague here.

Also "opensource your workflow" isn't clear. I had no idea that meant "make your kanban board public".

Why not "Waffle.io is a public kanban board that deeply integrates with github issues"? Clear, to the point, no one complains that they can't tell what the product does.

Re: Waffle.io

#48
post #2

I would urge you to take another look at the flow of your landing page. I have literally no clue what your product does even after reading the infographic at the top of the page a few times. - GitHub users want a way to help out on open source projects - waffle.io places a dynamic badge in your GitHub README file for all to see where they can help - Clicking that badge takes anyone to your public waffle.io board wher…

I strongly dislike everything about waffle.io. I feel bad about it, because these are good people who more than likely love their product and it's getting a lot of hate here despite them coming here to respond to feedback... but. 1. Most people here are confused about what this is for. After understanding what it's for, I find that it's not even a solution looking for a problem... it's a force-fed solution to a non-e…

Yes, because Apple or Trello are much better names.

Honestly, I clicked the link solely because I thought "damn, waffle.io is an awesome name".

Also, I think hooking a kanban board up to github issues is great. Not mind blowing, but definitely nice to automate coordination between the two.

Re: Waffle.io

#49
Communicating the progress of a project or feature is something really important I think open-source people need to realize, when they have a fairly non-technical audience.

I think GitHub milestones are central to productivity and communicating progress to a base of interested parties, so I would recommend focusing on milestones specifically—also to encourage their use—rather than showing one huge list of issues by default. It’s fairly disorienting, even to me as a regular GitHub user and contributor.

Those cards take up an awful lot of vertical space, which I don’t think is going to scale well with a large project. Look at project like Bootstrap: https://waffle.io/twbs/bootstrap. Because you load the issue on scroll, I can’t even get an idea of how many issues there are from the size of my scroll bar. Milestones are the main way for repo owners to manage a large number of issues.

From what I could tell, you can sort by milestones using a filter, but for some reason, the list of milestones wouldn’t load?

A while back, I created a small never-to-be-finished project called milestones.js to involve a general audience in the progress of upcoming features—taking advantage of milestones: https://github.com/ndarville/milestones.js. At the bottom of the README are some related projects that might be of interest to you as well.

In other words:

1. Find out who you want your users to be.

2. Find out what they should be shown.

3. Focus on milestones, GitHub’s killer productivity feature.

4. Fit more issues vertically; the card metaphor isn’t that important.

5. Know that the dynamic loading of issues on scroll is working against you from a UX perspective.

Re: Waffle.io

#50
I like the idea, it seems really helpful, but just as a warning if you call your site Waffle and blue is the prominent color, especially on the logo, you're going to cause people to make connections that shouldn't be made...
Post reply on HN