Reitveld does something like this, although it does make sense for bitbucket as well as long as we don't go overboard and implement an entire code review suit. I still believe that proper tools can be used for many purposes.
It would be great to be able to comment on a particular revision of a patch queue, before it was pulled into the main repo.
Presumably, comments need to be addressed. When a new version of a patch queue is committed, you could detect if the lines changed are those with comments, and show comments still outstanding from the previous revision. All without any extra explicit interface / user-interaction.
For the immediate future, BitBucket could use basic conversation
thread for each changeset. I'd like to ask the other developers
collaborating things like... "WTF?!", "Could you explain what you did
here because it doesn't work as described in your commit.", "hey,
great work you saved me 10 hours", etc etc. You get the idea.
In the future, you could get much more complex with it. There could
be inline code comments/questions. You could get even more "Code
For now, I'd just like a simple conversation thread available for each
change set. This conversation is something that any developer
collaborating with me can read and respond to. Maybe even it'd be
part of the email notifications if they are turned on.