I don't think this would be so risky, it seems like it would be a good thing to parse the @foo and look for a user named foo. If this user is found, link the @foo and cc foo on the comment / bug report / review, if the user foo isn't found, then just leave the text as is.
Another way to do this is to use the existing ideas from the launchpad bzr integration stuff ( lp:~foo ). This would be pretty simple for people who are using LP for code hosting / reviews, and would provide the branding benefit of reminding the user of lp while typing it. It also could seem a bit less like we're just integrating "micro-blogging" features into Launchpad and a bit more natural to Launchpad's existing feature set.
I don't think this would be so risky, it seems like it would be a good thing to parse the @foo and look for a user named foo. If this user is found, link the @foo and cc foo on the comment / bug report / review, if the user foo isn't found, then just leave the text as is.
Another way to do this is to use the existing ideas from the launchpad bzr integration stuff ( lp:~foo ). This would be pretty simple for people who are using LP for code hosting / reviews, and would provide the branding benefit of reminding the user of lp while typing it. It also could seem a bit less like we're just integrating "micro-blogging" features into Launchpad and a bit more natural to Launchpad's existing feature set.