tsoding / snitch

Language agnostic tool that collects TODOs in the source code and reports them as Issues
MIT License
506 stars 41 forks source link

Be able to see when TODO's were introduced #4

Open fabulousduck opened 6 years ago

fabulousduck commented 6 years ago

It would be nice to see when a TODO was introduced and by who to keep track on what different contributors are working on and when.

Also usefull to see if a TODO has been introduced long ago and probably not going to be implemented by the person who put it there

rexim commented 6 years ago

@fabulousduck When we talk about licensing of the code it is indeed important to keep track of who made the changes, where, and when. And for that we have git.

But if we talk about maintainability of the code, IMO, such information is completely irrelevant. I believe that the code should be organized so anybody can make contributions anywhere. And when I put my TODOs I always keep a mental note that "maybe this will be implemented not by me".

The main point of this "game" is to decompose the issue and be done with it. And go do something else, play a video game for instance. Once your ready to make another contribution you pick another TODO (maybe yours maybe not) and continue the "game".

Some people may put unclear TODOs which implicitly makes them the owners of that TODO. I will combat that when I review PRs. Plus since the TODOs are associated with an issue we can always discuss them and clarify them for everybody else.

fabulousduck commented 6 years ago

I see, that clears it up. I think this issue can be closed then

rexim commented 6 years ago

@fabulousduck I think we need to document that somewhere. I'll keep this issue open as a reminder to document that.