| Both sides previous revision Previous revision Next revision | Previous revision |
| summerofcodementorchecklist [2009/04/14 22:46] – TimKientzle | summerofcodementorchecklist [2022/06/28 23:04] (current) – Remove "Do I have to use Subversion?" FAQ, it's not an issue anymore. LiWenHsu |
|---|
| ====== Summer of Code Mentor Checklist for FreeBSD Mentors ====== | ====== Summer of Code Mentor Checklist for FreeBSD Mentors ====== |
| |
| This page collects ideas and suggestions for %%FreeBSD%% developers mentoring student projects during [[SummerOfCode2009|Summer of Code 2009]]. | This page collects ideas and suggestions for %%FreeBSD%% developers mentoring student projects during [[SummerOfCode|Summer of Code]]. |
| Any questions can be discussed on the soc-mentors@ mailing list or brought to the attention of soc-admins@. | Any questions can be discussed on the soc-mentors@ mailing list or brought to the attention of soc-admins@. |
| |
| ===== Ideas/Planning Phase, Before Student Applications Accepted ===== | ===== Ideas/Planning Phase, Before Student Applications Accepted ===== |
| |
| In 2008, student applications started being accepted in April. | A few things need to be under way before the application period opens. |
| A few things need to be under way before then. | |
| |
| * Review the ideas list and add submissions. More than half of our student applications use ideas taken from the %%FreeBSD%% ideas list. Our students have a wide variety of backgrounds, so we can use ideas for all experience levels. | * Review the ideas list and add submissions. More than half of our student applications use ideas taken from the %%FreeBSD%% ideas list. Our students have a wide variety of backgrounds, so we can use ideas for all experience levels. |
| * Help mail students and communicate. In particular, we encourage students to propose their ideas on current@ and other public forums. Few things are more discouraging than getting no response at all. We also encourage students to try to locate %%FreeBSD%% developers to act as potential mentors; if you get an inquiry that you can't help with, forward the request to someone who can. | * Help mail students and communicate. In particular, we encourage students to propose their ideas on current@ and other public forums. Few things are more discouraging than getting no response at all. We also encourage students to try to locate %%FreeBSD%% developers to act as potential mentors; if you get an inquiry that you can't help with, forward the request to someone who can. |
| |
| ===== Community Bonding Period, Before the Summer (April 20--May 23) ===== | ===== Scoring proposals ===== |
| | |
| | * Although Melange provides built-in functionality for scoring proposals, it doesn't allow us enough flexibility to really assess proposals and identify weaknesses or causes for concern in each. Instead we use a Google Docs spreadsheet, which enables us to score in multiple dimensions, and see each others scoring. See [[SummerOfCodeScoring|Summer of Code Scoring]] for more details. |
| | |
| | ===== Community Bonding Period, Before the Summer ===== |
| |
| Before coding officially begins is a good time to discuss the project with your student and work out how you'll work together. | Before coding officially begins is a good time to discuss the project with your student and work out how you'll work together. |
| Among the issues you should discuss: | Among the issues you should discuss: |
| |
| * When are you available? Vacations (both mentor's and student's), class schedules, and other factors should be well-understood before the beginning of coding. Keep in mind that the %%GSoC%% schedule is designed around US class schedules, which generally end in mid-May. You may need to find ways to adjust if your student is on a different class schedule. | * Which version control system the student would like to use. More information is available at [[SummerOfCodeVCS|Summer of Code VCS]]. |
| | |
| | * When are you available? Vacations (both mentors and students), class schedules, and other factors should be well-understood before the beginning of coding. Keep in mind that the %%GSoC%% schedule is designed around US class schedules, which generally end in mid-May. You may need to find ways to adjust if your student is on a different class schedule. |
| |
| * How will you communicate? Email, IRC, in-person meetings (if you happen to be in the same geographic area) are all reasonable. You should work out something that works well for you and your student and figure out a suitable schedule. For most students, you should plan to communicate every day or two. Negotiate this explicitly with your student and plan to hold them to what you negotiate. Encourage them to pick a public forum such as mailing lists for most communications. | * How will you communicate? Email, IRC, in-person meetings (if you happen to be in the same geographic area) are all reasonable. You should work out something that works well for you and your student and figure out a suitable schedule. For most students, you should plan to communicate every day or two. Negotiate this explicitly with your student and plan to hold them to what you negotiate. Encourage them to pick a public forum such as mailing lists for most communications. |
| |
| * Does the student need to do any preparatory work before start-of-coding? It's a good idea to make sure your student is at least comfortable building and upgrading %%FreeBSD%% from source. If your student needs to be working with -CURRENT (most do), you should make that clear and help them get started working in that environment. Otherwise, students are likely to spend the first weeks of the summer dealing with routine issues like learning how to use single-user mode. | * Does the student need to do any preparatory work before start-of-coding? It's a good idea to make sure your student is at least comfortable building and upgrading %%FreeBSD%% from source. If your student needs to be working with -CURRENT (most do), you should make that clear and help them get started working in that environment. Otherwise, students are likely to spend the first weeks of the summer dealing with routine issues like learning the difference between "make kernel" and "make buildkernel" and learning to read UPDATING. |
| |
| ===== First Half of the Summer, Before the Mid-term Evaluations ===== | ===== First Half of the Summer, Before the Mid-term Evaluations ===== |
| |
| In 2009, coding officially begins May 23, with mid-term evaluations beginning in early July. | |
| Generally, this is a ramp-up period where students gain familiarity with their specific project and make their first concrete progress. | Generally, this is a ramp-up period where students gain familiarity with their specific project and make their first concrete progress. |
| |
| ===== Second Half of the Summer, After the Mid-term Evaluations ===== | ===== Second Half of the Summer, After the Mid-term Evaluations ===== |
| |
| In 2008, coding completed in early September. | |
| After the mid-terms, your student should have clear goals and be able to make steady progress. | After the mid-terms, your student should have clear goals and be able to make steady progress. |
| |
| |
| ====== Frequently Asked Questions ====== | ====== Frequently Asked Questions ====== |
| |
| ===== Do I have to use Perforce? Can my student work in another SCM? ===== | |
| |
| For administrative reasons we'd like to keep the number of revision control systems to a minimum. For kernel projects it almost certainly makes sense to use Perforce because of the ease of branching and tracking changes in -CURRENT. | |
| |
| For userland or ports projects however, there is more flexibility. Please talk with soc-admins, but it should be fine to use code.google.com. | |
| |
| ====== Other Links ====== | ====== Other Links ====== |
| ===== Mentoring Guidelines / Advice for FreeBSD Mentors ===== | ===== Mentoring Guidelines / Advice for FreeBSD Mentors ===== |
| |
| See SummerOfCodeMentoring for some guidelines posted by Robert Watson, Murray Stokely, and others. | See [[SummerOfCode/MentorAdvice|Summer of Code Mentor Advice]] for some guidelines posted by Robert Watson, Murray Stokely, and others. |
| | |
| | ---- |
| | |
| | {{tag>Gsoc}} |
| |