71–80 of 292 posts
Sniffing around the source, looks like a Backbone.js app -- cheers. I'd love to add it to the homepage as an example, if you want to email me a brief paragraph of description. Edit For those poking around, check out the top-level "Models" namespace.
Originally posted this on the announcement blogpost, but my comment is still awaiting moderation, and joel is posting here. :-) Several major +1s: 1) Use of Google login, with ability to set a password to log in without that. I LOVE this, and it fits with what Joel (and Jeff Atwood) have been proselytizing for a while about the use of OpenID. 2) Awesome, responsive UI. Also a few -1s: 1) No indication about pricing p…
What do the colored squares over my avatar mean?
Green: Online and active, Yellow: Online, but inactive, Grey: Not online
When someone is online it means that they're connected to Trello, but they're not necessarily looking at the same board as you.
Great app and highly intuitive. The home page clearly explain what the software does, the signup process is really simple and straightforward, and it's free. Once you get inside, you have a fake board which is there to help you get started.. It took me 2 minutes to try and understand how everything worked. No magic, no complicated features.. really simple and intuitive. I love the "reverse of a card" concept, the sma…
Does it have an API, so I can integrate with other systems? If not, is that planned for?
Originally posted this on the announcement blogpost, but my comment is still awaiting moderation, and joel is posting here. :-) Several major +1s: 1) Use of Google login, with ability to set a password to log in without that. I LOVE this, and it fits with what Joel (and Jeff Atwood) have been proselytizing for a while about the use of OpenID. 2) Awesome, responsive UI. Also a few -1s: 1) No indication about pricing p…
What do the colored squares over my avatar mean?
Joel, serious question, if you're listening. In the blog post, you mention that these teams are adopting the Lean Startup philosophy of ship early and ship often. Does that mean that you've softened on the "never ever write any code without a spec" dogma from "the Joel Test"? I've personally found that when you're doing tight iterations and continuous deployment, writing old-school spec documents feels, well, old-sch…
It's more complicated than that, and it's hard to answer here. Basically -- if you're building something big and complicated and you should know exactly how it's going to work, a big written spec really helps. If you're building something brand new, a startup, or a crazy idea that you need to test quickly and iterate, you should use lots of little specs. It's ok if the specs aren't so fancy... a detailed map of what…
It's easy to see someone jumping in and writing and re-writing code when they haven't thought it through as wasteful. People have a harder time seeing that writing and re-writing specs can be similarly wasteful.
Damn this is pretty similar to the direction my app Wallboardr is taking, except status columns aren't customisable yet. Any thoughts on comparison folks? http://wallboardr.com
I imagine a board for "existing modules / features" That has the current "responsible" person for that item.. and a "new feature" board that has an easy way for people to see who is currently implementing said new feature. Though that would overlap somewhat with fogbugz (search for the task and see who it is assigned to) the board would have the advantage of being more high level and still being easily visible after a task is complete.
Joel (or FogCreek persons), I'm using fogbugz / kiln at home and for my side projects is there some plan to provide integration with those existing projects? Magically linking based on case numbers? Updatet he responsible person on a card based on who is currently assigned some case number?
Damn this is pretty similar to the direction my app Wallboardr is taking, except status columns aren't customisable yet. Any thoughts on comparison folks? http://wallboardr.com
If you can't customize columns, you've already lost :) But I really like the way you explicitly mention Kanban and Scrum, which Trello doesn't mention at all.
To be fair they also have comments and todo lists per card, like Pivotal, so Wallboardr is a bit behind at the moment. I've been wondering how essential sub-card todo lists are for a while, I've found myself wanting them, but MVP ideals have avoided so far.
But we have a stacked burnup chart! :-P