From Fedora Project Wiki
http://teachingopensource.org/index.php/POSSE_California_CS_Planning#School_contact_informationThe idea of the coding test is for mentors and sub-projects to have an objective way of showing that a student has essential skills and knowledge to start the project.
The test needs to be created by the mentor/sub-project, since each idea and proposal are about different frameworks using different languages, with different goals.
Students
- Talk with your mentor to find out what they are intending for a coding test.
- Take the test when provided.
- If you don't pass the test, consider if you should continue applying.
- Must you pass the test to get your proposal accepted? The mentor knows.
- If you have the option of continuing to apply, talk with the mentor to make sure you should continue. The project might require more than you are able to do at this point in time; try again next year.
Mentors
- You understand the code, frameworks, and dependencies of your project. What does a student need to know to start the project and have a fair chance at success? Examples are:
- Familiarity with the base language(s).
- Ability to figure out frameworks.
- Knows what to do with an API.
- Devise a straightforward (no tricks!) test that utilizes components in the proposed project.
- Give this test to each student who applies for the project.
- Do this early, if possible, to help students know if they should continue.
- Decide if passing the test is a MUST or a SHOULD condition. You may want to work with a student who didn't pass the test if you still feel they are otherwise qualified.
- Apply the rules fairly - it must be a MUST or a SHOULD condition for all students.