expectations
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
expectations [2016/02/01 12:01] wkerzend |
expectations [2016/03/10 10:13] (current) unoebauer |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| In addition to the [[acceptance_requirements|Acceptance Requirements]] that all students are required to abide by, there are participation and behavior expectations. | In addition to the [[acceptance_requirements|Acceptance Requirements]] that all students are required to abide by, there are participation and behavior expectations. | ||
| - | The program timeframe is ''very'' short. There's not much time to get up to speed, so there is a need to be clear of what is expected. Also, many students haven't done a lot of real-world development work previously. On top of that, most mentors and students are in different locations so coordinated interaction can be difficult at times. Because of this, it's vitally important to the success of each student's project for all expectations to be specified and understood before students begin coding for the summer. This should be the first step in a long series of frequent communication between student and their mentor(s). | + | The program timeframe is **very** short. There's not much time to get up to speed, so there is a need to be clear of what is expected. Also, many students haven't done a lot of real-world development work previously. On top of that, most mentors and students are in different locations so coordinated interaction can be difficult at times. Because of this, it's vitally important to the success of each student's project for all expectations to be specified and understood before students begin coding for the summer. This should be the first step in a long series of frequent communication between student and their mentor(s). |
| This document walks through various expectations for students and mentors, as well as addressing various ways to communicate effectively. | This document walks through various expectations for students and mentors, as well as addressing various ways to communicate effectively. | ||
| Line 20: | Line 20: | ||
| The student should schedule time to work on the project each day and keep to a regular schedule. It's not acceptable to fiddle around for days on end and then pull an all-nighter just before deadlines. It will show in code and in the evaluation. | The student should schedule time to work on the project each day and keep to a regular schedule. It's not acceptable to fiddle around for days on end and then pull an all-nighter just before deadlines. It will show in code and in the evaluation. | ||
| - | |||
| - | ==== Commit access ==== | ||
| - | |||
| - | Students are treated like any other contributor to the project. That means that in order to get commit access, students need to be actively involved and making small succinct patches at first and engender trust with the existing developers. Once the student shows technical competency, demonstrates respect for the [http://brlcad.svn.sourceforge.net/svnroot/brlcad/brlcad/trunk/HACKING developer guidelines], and is known to work well with the other developers, commit access will be granted. ''This should happen before coding begins.'' | ||
| ==== Integrated development ==== | ==== Integrated development ==== | ||
| Line 44: | Line 40: | ||
| - | **VYTAS CAN YOU PUT YOUR GUIDELINES IN THERE ** | ||
| Bad examples | Bad examples | ||
| Line 51: | Line 46: | ||
| * Tweaks. | * Tweaks. | ||
| * Improved version. | * Improved version. | ||
| - | |||
| - | |||
| Line 82: | Line 75: | ||
| - What is the communication schedule? Daily? Every two days? Mondays, Wednesdays, Fridays? | - What is the communication schedule? Daily? Every two days? Mondays, Wednesdays, Fridays? | ||
| - | - What is the best medium to use for regular, scheduled communication? IRC? Mailing list e-mails? Instant messenger? VOIP? Telephone call? Face-to-face? | + | - What is the best medium to use for regular, scheduled communication? IRC/Gitter? Mailing list e-mails? Instant messenger? VOIP? Telephone call? Face-to-face? |
| - | - What is the best medium to use for non-scheduled communication? IRC? Mailing list e-mails? | + | - What is the best medium to use for non-scheduled communication? IRC/Gitter? Mailing list e-mails? |
| === DO === | === DO === | ||
| Line 107: | Line 100: | ||
| **Students should not discuss development in private.** This includes | **Students should not discuss development in private.** This includes | ||
| - | refraining from private IRC discussions as well as private e-mails even | + | refraining from private IRC/Gitter discussions as well as private e-mails even |
| with your mentor unless the discussion involves personal information. | with your mentor unless the discussion involves personal information. | ||
| Other developers need to be aware of the progress, discussions, and | Other developers need to be aware of the progress, discussions, and | ||
| Line 126: | Line 119: | ||
| ==== Resolving problems ==== | ==== Resolving problems ==== | ||
| - | Student can call upon any mentor or other developer, they don't have to limit their interactions to just their mentor. They shouldn't limit their interactions to just one mentor. Students having difficulties communicating with any mentor should contact the [[User:Sean|administrator]]. | + | Student can call upon any mentor or other developer, they don't have to limit their interactions to just their mentor. They shouldn't limit their interactions to just one mentor. Students having difficulties communicating with any mentor should contact the <wkerzendorf@gmail.com>. |
| - | If you're stuck, ask for help on IRC and/or on the mailing list. If you are still stuck, read the source code. If you're still stuck, ask for help again. Better questions frequently yield better answers. | + | We also abide by the [[http://www.astropy.org/about.html|Astropy Community Code of Conduct]] and if there are any violations students should contact <wkerzendorf@gmail.com> to arrange for a confidential meeting. |
| + | |||
| + | If you're stuck, ask for help on Gitter and/or on the mailing list. If you are still stuck, read the source code. If you're still stuck, ask for help again. Better questions frequently yield better answers. | ||
| ==== Design documents ==== | ==== Design documents ==== | ||
| Line 147: | Line 142: | ||
| Many thanks to the Python foundation for their initial write-up document on participant expectations: http://wiki.python.org/moin/SummerOfCode/Expectations | Many thanks to the Python foundation for their initial write-up document on participant expectations: http://wiki.python.org/moin/SummerOfCode/Expectations | ||
| - | [[category:Summer of Code]] | ||
| - | |||
expectations.1454324469.txt.gz · Last modified: 2016/02/01 12:01 by wkerzend
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 3.0 Unported
