Code review for Bitbucket / hg?

If you follow a workflow similar to what Scott Chacon described as github-flow where each team member has a fork of the main repo on bitbucket, pushes to his own fork and when he is done, issue a pull request to the main repo, you'll get code review support for free. Pull requests on bitbucket shows the diffs and supports comments to be added. It is not as good as github ones as, AFAIK, you can't comment on individual files/lines but it's good enough IMO.

If you follow a workflow similar to what Scott Chacon described as github-flow, where each team member has a fork of the main repo on bitbucket, pushes to his own fork and when he is done, issue a pull request to the main repo, you'll get code review support for free. Pull requests on bitbucket shows the diffs and supports comments to be added. It is not as good as github ones as, AFAIK, you can't comment on individual files/lines but it's good enough IMO.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.