Dropped the section on Rietveld, which we no longer use.
diff --git a/ContributionReviews.wiki b/ContributionReviews.wiki index dac2aa5..2c2d5c6 100644 --- a/ContributionReviews.wiki +++ b/ContributionReviews.wiki
@@ -97,37 +97,7 @@ both "small" and "non small" ones, include the diff itself as an email attachment, to make it easier for reviewers to patch the change into a working copy with `patch`. Such a diff attachment can be produced with -the methods described above: - -Alternately, committers can use `upload.py` to submit -[ContributionReviews#Using_Rietveld_for_code_reviews Rietveld code reviews]. - -==== Using Rietveld for code reviews ==== - -An instance of -[http://code.google.com/p/rietveld/ Guido van Rossum's Rietveld] -code review tool has been set up at -http://codereviews.googleopensourceprograms.com for use by -[ContributionReviews#Committers Melange committers]. An account on -[http://mail.google.com/a/googleopensourceprograms.com googleopensourceprograms.com] -is required in order to post code review requests and to provide code -review comments. - -Patches supplied via the Rietveld web form should be created following -[ContributionReviews#Patches these instructions]. The melange repository -includes a custom version of the Rietveld `upload.py`. To start a code review, -do something like this and respond to the prompts: - -{{{ -cd ~/code/melange -./thirdparty/rietveld/upload.py \ - -- soc/models/new_model.py soc/models_deleted_model.py -}}} - -To upload an updated diff for an existing code review in progress, simply -supply the extra `--issue=<the existing issue number>` option. Rietveld -will then display the deltas between the previously supplied diff and the -new one. +the methods described above. ==== Suggested patches from casual contributors ====