A pure hobby project is developed on the basis of ‘Do I feel like a bit of coding this weekend? I wonder what would be fun to do.’ A developer who takes this attitude isn’t making plans at all. They code when they feel like it; they release (if at all) when it seems like a good idea.
I have some projects like this, and the “bug” tracker is 90% feature requests that I wrote up so I wouldn’t forget them. When I want to work on something, I browse through the issues and pick something out.
I agree, but I go farther than that, I have a repo called ‘me’ and I put my life TODO list there. I’m too lazy to learn/use more than 1 todo/reminder/task tool. It has it’s downsides for sure, but I still prefer it over having to babysit yet another tool.
That said, I think I’d love this vaporware bug and plan tracker tool, if it was done “right”, where right is obviously subjective, and like them, I don’t know what that looks like at this point in time.
I have some projects like this, and the “bug” tracker is 90% feature requests that I wrote up so I wouldn’t forget them. When I want to work on something, I browse through the issues and pick something out.
I agree, but I go farther than that, I have a repo called ‘me’ and I put my life TODO list there. I’m too lazy to learn/use more than 1 todo/reminder/task tool. It has it’s downsides for sure, but I still prefer it over having to babysit yet another tool.
That said, I think I’d love this vaporware bug and plan tracker tool, if it was done “right”, where right is obviously subjective, and like them, I don’t know what that looks like at this point in time.