code-centered issue tracking?
Is there anything that allows code-centered issue tracking? Recently, Gustavo Niemeyer had an interesting piece up where he suggests private/protected syntax for Python. His point is that code collaboration doesn’t otherwise work in larger uncontrolled environments of dev groups. I agree with most of his observations but not his conclusion. I’d rather like to see reduced communication costs for changing code. Here is an example of what i mean. If see a code fragment like this:
def somefunc(self, x, y, z): self._cache = func(x) + other(y) self.z = self._cache + third(z)
i want to be able to visually mark this code, write a comment like:
hey, i need the third(z) value, and doing self.z-self._cache feels bad – can you help?
and i want my development environment to automatically route this question with exact code refs to the maintainers of the code. This should not take longer than 20 seconds and be automatically managed.
On the receiving side, as the maintainer, i want to get notified and be able to say:
and have it automatically list me all files and issues for it. So i easily see the above question, do a patch, and issue:
and type in a message. Maybe automatically CCed to other library maintainers, a mailing list etc. As the original sender i get back a mail and can use a cmdline tool to apply the patch, give feedback and so forth …
IOW, i want to have tools that automatically manage the issue-addressing, code-referencing, finding-out about package info/release numbers, format the comment related to the cited code, send the mail, register an issue automatically and so on. Is there something like this?
If not: doesn’t we already have most of the pieces? What makes sense to use for it? Mercurial and Patch queues? Maybe the new Bitbucket API? Integrate with existing issue tracker? First goal would be to have it manage itself, i guess 🙂
Written by holger krekel
May 18, 2009 at 11:35 am
Posted in metaprogramming
Subscribe to comments with RSS.