summerofcode:mentoradvice

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
summerofcode:mentoradvice [2018/03/03 07:29] – move it to a useful place in the hierarchy MarkLinimonsummerofcode:mentoradvice [2020/02/10 09:24] (current) – Added Gsoc category TrevorRoydhouse
Line 9: Line 9:
 ===== Requirements for Mid-term evaluation success ===== ===== Requirements for Mid-term evaluation success =====
  
-  * Code submitted to Perforce is a necessary but not sufficient condition for a passing evaluation at the mid-term period.  All mentors should be keeping track of the repository to ensure there student has ironed out any access issues, and has submitted code well before the mid-term period.+  * Code submitted to Subversion is a necessary but not sufficient condition for a passing evaluation at the mid-term period.  All mentors should be keeping track of the repository to ensure there student has ironed out any access issues, and has submitted code well before the mid-term period.
  
 ==== Information on being a mentor ==== ==== Information on being a mentor ====
Line 42: Line 42:
 Make sure you ask them about their level of effort and availability over the summer--in particular, if they have travel plans. Make sure you ask them about their level of effort and availability over the summer--in particular, if they have travel plans.
  
-=== Perforce, e-mail, etc. ===+=== Subversion, e-mail, etc. ===
  
-We will provide all students with %%FreeBSD%%.org e-mail aliases and perforce accounts with a soc2010 work area.  We will also add them to the soc-students alias.  We expect that all project work will be done in Perforce unless a prior arrangement is made with soc-admins.  Google *requires* that work be done in an open source repository, and that the work be monitored, etc.  By using Perforce, we ensure the work is open source, widely available, can be collaborated on, and provide a common commit mailing list for all student projects. There's some excellent new user documentation available on Perforce, but you will probably find your student requires quite a bit of support in the first few weeks as they get up-to-speed.+We will provide all students with %%FreeBSD%%.org e-mail aliases and subversion accounts with a //soc20xx// work area.  We will also add them to the soc-students alias.  We expect that all project work will be done in Subversion unless a prior arrangement is made with soc-admins.  Google *requires* that work be done in an open source repository, and that the work be monitored, etc.  By using Perforce, we ensure the work is open source, widely available, can be collaborated on, and provide a common commit mailing list for all student projects. There's some excellent new user documentation available on Perforce, but you will probably find your student requires quite a bit of support in the first few weeks as they get up-to-speed.
  
 - Student community and IRC - Student community and IRC
Line 91: Line 91:
 into perforce along the way.  Status updates can take many different into perforce along the way.  Status updates can take many different
 forms, but they need to be linked from one canonical location for all forms, but they need to be linked from one canonical location for all
-students.  That location is wiki.freebsd.org, and we'll setup an+students.  That location is %%FreeBSD%% Wiki, and we'll setup an
 account for each student.  The [[/SummerOfCode2010|SummerOfCode2010]] page will have a list account for each student.  The [[/SummerOfCode2010|SummerOfCode2010]] page will have a list
 of each successful student project with a link to a separate wiki that of each successful student project with a link to a separate wiki that
Line 113: Line 113:
 handle all of our own issues with students without having to escalate handle all of our own issues with students without having to escalate
 to Google when possible. to Google when possible.
 +
 +----
 +
 +{{tag>Gsoc}}
  
  • summerofcode/mentoradvice.1520062179.txt.gz
  • Last modified: 2018/03/03 07:29
  • by MarkLinimon