Alter guidance for new contributor code reviews to require clones.
At this morning's team meeting we decided that we're just seeing
too many different kinds of patch requests and review requests
and want to raise the bar a little.
diff --git a/ContributingCode.wiki b/ContributingCode.wiki
index 08903a3..e112b2f 100644
--- a/ContributingCode.wiki
+++ b/ContributingCode.wiki
@@ -83,26 +83,18 @@
=== Requesting A Code Review ===
-Please use `git bundle` to create a bundle file that contains your
-commits.
+Please push your commit to a [https://code.google.com/p/soc/source/clones server-side clone] of Melange and start a new thread on
+[MailingListsGuidelines the developer mailing list] in which you link
+to your commit and ask for review.
-If your change addresses a known issue in Melange, please attach the
-bundle containing your commits to the issue addressed as an attachment
-in a comment on the issue. If your change is not relevant to any
-particular issue, attach your bundle to a new message to the
-[MailingListsGuidelines#Developer_list developer mailing list].
-
-Upon reciept of your bundle, a Melange committer will conduct a review
-of your code, typically within two or three days.
+A Melange committer will conduct a review of your code, typically
+within two or three days.
=== Responding To A Code Review ===
-Review of a commit generates a message to the
-[MailingListsGuidelines#Commits_list commits list]. Typically the
-reviewer will ask several questions during the course of the review;
-respond to these questions in a reply message. If appropriate, attach
-a revised bundle containing revised a version of your commit for
-further review.
+Typically the reviewer will ask several questions during the course
+of the review; respond to these questions in a reply message. If
+appropriate, push a revised version of your commit for further review.
*Contributions by first-time contributors typically go through several
rounds of review.* We hope you both learn from and enjoy the process.
