2014 Summer Student Orientation notes.

These vary only slightly from last year's notes,
which they also supersede.
diff --git a/2013SummerStudentOrientation.wiki b/2014SummerStudentOrientation.wiki
similarity index 88%
rename from 2013SummerStudentOrientation.wiki
rename to 2014SummerStudentOrientation.wiki
index eaae189..4a2a295 100644
--- a/2013SummerStudentOrientation.wiki
+++ b/2014SummerStudentOrientation.wiki
@@ -1,4 +1,4 @@
-#summary Melange 2013 Summer Student Orientation Topics
+#summary Melange 2014 Summer Student Orientation Topics
 #labels Importance-Useful,Phase-Guidelines,Contents-Complete
 
   * *Code Drafting*
@@ -9,6 +9,8 @@
     * Plan on including running tests as active demonstrations that your code works.
   * *Code Review*
     * Receiving end
+      * Be clear about whether or not you think your code is ready for integration.
+        * It's okay to push commits that say "FOR REVIEW ONLY" when you're asking for an opinion.
       * Who’s been reading the code review discussions on melange-soc-commits@?
         * You all should be.
       * Make sure you’ve read the [PythonStyleGuide Style Guide] and that your code conforms to it
@@ -30,8 +32,8 @@
   * *Mailing lists*
     * Everyone should be subscribed to, and reading every message on, every list: melange-soc, melange-soc-dev, melange-soc-issues, melange-soc-commits, and melange-soc-build. The traffic is reasonably light.
   * *Meetings*
-    * Our current meeting time is weekly on [http://www.timeanddate.com/worldclock/converted.html?iso=20130611T10&p1=224&p2=0 Tuesdays at 10 a.m. America/San Francisco]. If that time doesn’t work for you, let us know and we’ll move it.
+    * Our current meeting time is weekly on [http://www.timeanddate.com/worldclock/converted.html?iso=20140502T1630&p1=0&p2=505&p3=2255 Tuesdays at 4:30 p.m. UTC]. If that time doesn’t work for you, let us know and we’ll move it.
     * Our current meeting technology is Google Hangouts. Try to have a working camera, microphone, and speakers/earphones.
     * Make arrangements to maintain some persistent textual interaction with your mentor - chat, IRC, a daily email thread, or something like that.
   * *Evaluation*
-    * The only chisled-in-stone rule here is that your work at both midterm and final will be judged in terms of what has been included in the Melange master branch, not what might be half-completed and buggy and still-in-progress elsewhere.
\ No newline at end of file
+    * The only chisled-in-stone rule here is that your work at both midterm and final will be judged in terms of what has been included in the Melange master branch, not what might be half-completed and buggy and still-in-progress elsewhere.