Evaluation Suggestions

From Google Summer of Code Mentor Wiki

Jump to: navigation, search
  • Question 6 should at least have a comment box like most other questions; it should also have the radiobutton "The code is currently experimental but with more work on it (from the student after SOC or from others) it could be merged in".
    • Right now the only options are basically "code is in" or "code will be thrown away", which is a bit limiting ;-)
    • Or maybe this is what the option "With some work the code is ready [...]" means, but the phrasing of that option is quite confusing. Sounds like saying two opposite things in the same sentence ;)
  • Question 9 ("How much time have you spent mentoring your student since the midterm evaluation, on average?") The available options are 0-5, 6-10, 10-15, and more than 15hrs per week. This is in contrast to the empirical average of about 5hrs/week.
    • The 0-5 option covers a range from fully at expectation (5hrs) to almost certainly insufficient or negligent (0-1hrs). Likewise, the next option covers a range from slightly more than expected (6hrs) to something that's probably nearly unsustainable for many people who aren't paid for their FLOSS work (10hrs).
    • The options should be more along the lines of 0-2 (reason for concern), 3-7 (around the empirically expected average), 8-12 (reason for concern), and more than 12.
  • Question 9 ("How much time have you spent mentoring your student since the midterm evaluation, on average?") IMHO it would be better not to give a list of ranges to choose, but to ask users to enter the average number of hours they spent in a text box. That way there's no 'leading' nature to the question. Once you present the participant with a list of ranges you introduce bias, not just in the reporting, but in the mind of the participant who will be wondering what the meaning behind the groupings are, and what each answer will mean. -- Jason Cleeland (LimeSurvey)
  • Question 12 requires exactly three checkboxes to be checked? Or maximum three? The wording isn't clear about that.
    • I'd like a rating for every single point, like "1 = Not a problem at all" to "5 = The project almost failed because of this issue". -- Stefan Majewsky
Personal tools