Difference between revisions of "Summer of Code/Application/2009"

Summer of Code/Application/2009 (view source)

Revision as of 20:32, 9 March 2009

81 bytes added , 20:32, 9 March 2009

→‎What steps will you take to encourage students to interact with your project's community before, during and after the program?: -- New wording

Sev

Bureaucrats, Interface administrators, Administrators

1,510

edits

@@ Line 133: / Line 133: @@
 ===  What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
-Our community uses forums, IRC, a Wiki and our mailing list for a vivid exchange of thoughts all the time. We will urge the students to participate in all of them; especially on IRC can they directly talk to many nice and helpful team and community members. The mentors will introduce the students to the rest of the team (making sure everybody knows who the students are). There are people active in the IRC channel virtually 24/7, thanks to the international nature of the project.
+In order to help the students to get familiar with the project, we created several importand documents for them. Particularly we have an exhaustive developer central where we describe important internals of our project.
-We also expect the students to talk to non-mentor team members on a regular basis about parts of ScummVM for which these team members are experts (if these parts happen to be relevant for the student's project). To achieve that, the mentors will specifically introduce them to each other, and will try to encourage them to work together.
+Also we use forums, IRC, Wiki and development mailing list during whole project development. Every developer, and students will be treated as such from the very start, is encouraged to take part in discussions in every channel that we use. Basically, on IRC any student will be able to get support literally 24/7, as our developers scattered all over the globe.
+Also not only the mentors communicate with the students, but every team member does that. The students are marked with special flag on our IRC, so everyone know who they are. Also we require the students to write introductory letters to our development list, so everyone will have impression about them and their skills.
 ===  What will you do to ensure that your accepted students stick with the project after GSoC concludes? ===
 Our experiences last year show that guys who are genuinely interested in the project will stick around. And that's really the drive for open source: to be interested in the project one is participating. We will try to select students who best match this criterion. Other than that, we run a cool team with loose coding deadlines and a cheerful IRC channel and mailing list, so prospective team members should feel at home soon. We always welcome new contributions with pleasure. Spending some time before someone gets promoted to normal team membership is how we've always done it; GSoC gives us the chance to implement this again, with added benefits too :-)