https://fedoraproject.org/wiki/GSoC_2010_plan#Workflow_plan mentions a coding test that students have to pass - where do we find out more about the test, how to administer it, how it's designed, etc? (I can understand the test itself being non-public so students will take it on even footing.)
I've been searching but unable to find stuff, so if it's simply that I'm missing something, just let me know. ;)
--Mel
On Tue, Mar 16, 2010 at 12:21:33PM -0400, Mel Chua wrote:
https://fedoraproject.org/wiki/GSoC_2010_plan#Workflow_plan mentions a coding test that students have to pass - where do we find out more about the test, how to administer it, how it's designed, etc? (I can understand the test itself being non-public so students will take it on even footing.)
I've been searching but unable to find stuff, so if it's simply that I'm missing something, just let me know. ;)
The answer is simply that it doesn't yet exist.
It is not a Google requirement and many organizations don't use one. It has been recommended, however, by many others.
We have a few choices:
1. Cook one up ourselves. 2. Borrow a FLOSS or public domain test but not announce what it is.
That's all I can think of. I can assist on the second item but not the first.
- Karsten
- Cook one up ourselves.
- Borrow a FLOSS or public domain test but not announce what it is.
<braindump> There are several kinds of informal tests that one can do.
There's "can you function in the sort of development environment you'll need?" This is what we did for Sugar Labs last summer, and it worked well: http://wiki.sugarlabs.org/go/Summer_of_Code/Student_application_template#Mis...
There's "can you work with and within a community?" test, which could be a "you must talk about your app with a mentor, here are times they'll be on IRC, provide a log" sort of thing.
Then there's the "can you code" test, which can be "send links to source code (stuff from class ok)."
Generally, I try to go for low overhead, which means stuff that the student probably has done already, and stuff that's easy to evaluate at a glance (for instance, the Sugar Labs exercise was "look at their screenshot, does it have their name in it? ok!")
</braindump>
--Mel
On Tue, Mar 16, 2010 at 10:57 PM, Karsten Wade kwade@redhat.com wrote:
On Tue, Mar 16, 2010 at 12:21:33PM -0400, Mel Chua wrote:
https://fedoraproject.org/wiki/GSoC_2010_plan#Workflow_plan mentions a coding test that students have to pass - where do we find out more about the test, how to administer it, how it's designed, etc? (I can understand the test itself being non-public so students will take it on even footing.)
I've been searching but unable to find stuff, so if it's simply that I'm missing something, just let me know. ;)
The answer is simply that it doesn't yet exist.
It is not a Google requirement and many organizations don't use one. It has been recommended, however, by many others.
We have a few choices:
- Cook one up ourselves.
- Borrow a FLOSS or public domain test but not announce what it is.
That's all I can think of. I can assist on the second item but not the first.
When it was talked about, the plan was to use easyfix.fedoraproject.org as an entry point for bugs to fix that would allow the mentor to assess the candidate
On Fri, Mar 19, 2010 at 3:16 AM, sankarshan sankarshan.mukhopadhyay@gmail.com wrote:
When it was talked about, the plan was to use easyfix.fedoraproject.org as an entry point for bugs to fix that would allow the mentor to assess the candidate
https://fedoraproject.org/wiki/User:Sankarshan/GSoC_Thoughts
On Tue, Mar 16, 2010 at 10:27:45AM -0700, Karsten Wade wrote:
On Tue, Mar 16, 2010 at 12:21:33PM -0400, Mel Chua wrote:
https://fedoraproject.org/wiki/GSoC_2010_plan#Workflow_plan mentions a coding test that students have to pass - where do we find out more about the test, how to administer it, how it's designed, etc? (I can understand the test itself being non-public so students will take it on even footing.)
I've been searching but unable to find stuff, so if it's simply that I'm missing something, just let me know. ;)
The answer is simply that it doesn't yet exist.
It is not a Google requirement and many organizations don't use one. It has been recommended, however, by many others.
We have a few choices:
- Cook one up ourselves.
- Borrow a FLOSS or public domain test but not announce what it is.
That's all I can think of. I can assist on the second item but not the first.
In the cook one up ourself vein, I think that projects that can do it are better off cooking up different tests for different applicants.
For instance, I might have one person apply to my project with the idea of "create a web front end for the application". Another one might submit a proposal to "Rewrite the core in C to reduce memory consumption". I'd probably want the first person to demonstrate that they can start a TurboGear2 project and make it do something (store a message in a db and give it back on another page). The second person I'd want them to show they could use the python-C-API and perhaps some indication that they understood how to optimize code.
-Toshio
On Sun, Apr 25, 2010 at 10:50:02AM -0400, Toshio Kuratomi wrote:
In the cook one up ourself vein, I think that projects that can do it are better off cooking up different tests for different applicants.
Makes sense. Also, good use of the private mentor list would be to discuss these -- if you wanted help from other mentors, that is.
We need to work out the coding test rules ASAP. I'll put it in the FAQ and link to the stub location ...
- Karsten
summer-coding@lists.fedoraproject.org
-
Karsten Wade -
Mel Chua -
Sankarshan Mukhopadhyay -
Toshio Kuratomi