I'm in for more new users. Experience is important, but since it's a really new service, and you had your success, it can't be that bad.
You can focus on making the experience better after getting some more users and more feedback.
If someone is going to leave because of the experience right now, well, there's always more people not using the software than people using it... Make it attractive to new people first, and then make it better for those using it.
I know that most of the times (ok, all of the times) you'll have more than one commit for any feature you develop.
We'll have a small gem or something to do that. You'll start your work and we'll track your time and at the end make a commit with the time stamp (or use git notes to keep the commits clean). All the commits you do in that time will be "ignored".
We don't have this now because we didn't have the time to do this (48 hours is not that much you know).
Thanks for the feedback anyway. Well have your comments in mind when developing v2 and the gem.
> We don't have this now because we didn't have the time to do this (48 hours is not that much you know).
I didn't intend to bash on your project. I'm sorry if my comment read that way.
I was just saying that I, personally, would not want my commits to be tied to an invoice that is most likely going to be read by a non-coder because that would severely hamper the quality of my commits.
I do believe though that for other people this might not be as much of an issue - heck it probably wouldn't for me if I were working on different stuff than I'm working on right now.
I just wanted to inform the people here not to jump to conclusions but think what this integration might (or might not - depending on their situation) do to their commits.
I LOVE it when people like you have a cool idea and follow through; whether the result is usable for me or isn't.
Oh no, no "offense" taken. We really appreciate feedback (all of it).
Having people disagree with the app forces us to make it better.
About the messy commit messages, that's why git notes may help (keeps your commits clean, but you still don't have to write the invoice entries again and again).
It has some advanced features like estimating the time spent on each line item based on number of commits or number of source changes.
For more accurate invoicing, you would utilize an app like TimeSink to record your computer's activities and then BBNW can cross reference that time spent with your git commits and figure out the billed activity that way.
Nonetheless, absolutely great job on the implementation! I had no idea anyone else was working on the same problem. If you're in the Bay area, I'd love to collaborate.
You can focus on making the experience better after getting some more users and more feedback.
If someone is going to leave because of the experience right now, well, there's always more people not using the software than people using it... Make it attractive to new people first, and then make it better for those using it.