Hey all so we're in for GSOC 2008 that's great, let's do our best about that
looking at the ICRlog, it seems we're going to have quite a bunch of potential applicants to manage, so I'm posting a couple of guidelines on how we (devs) should manage them in order to help them give us all we need in order to choose what projects we'll mentor. this is probably going to change the way we work and what's going on on #wesnoth-dev for a couple of weeks, so bare with us. Most of the students are eager to join, to get advice and to know what to do to maximize their chances, so here are a few guidelines 1) They should all have a wiki page. (and link it to the summer of code page). We really need to have our ideas on who's who, and "that guy we discussd with on IRC the other day" won't make it. So insist that they write down their ideas, that they describe their own in the same way we described our ideas on the idea page, and that they try to provide more fleshing on the ideas we've outlined. 2) make them compile trunk seems obvious, but make sure they do it 3) Make them read the code. Again, EasyCoding is an easy way to do that but not the only way. Direct them to patches.wesnoth.org and the sticky in CodersCorner about submiting patches. If they are interested in a very specific area, adding doxygen comments to existing code is a "smart way" to get in the code. It forces you to write down your ideas as you understand the code, and it results on a usefull patch. encourage them to mark on the wiki page the patches they submitted so we can follow who did that. These pages are clearly for them to brag on what they do, so encourage them to do that. on a related note, I am a bit overwhelmed right now with the patches, so please try to keep the patchflow steady. do not let patches rot in patches.wesnoth.org This is a call to everybody, please do some patch-monkeying for me, we don't want our students to feel forgoten 4) Make them join the community. there are different aspects to that. Make them play the game if they seem to not know it very well, make them join the forum so they have a feel of the community, We have a special title for potential student, Sirp, Mordante and I (and any forum admin) can give them if you PM us the nick. and of course, these are my ideas of guideline, feel free to discuss it, But I think it's important that we have good bookkeeping wrt students, who made what and when, so nobody feel neglected or misjuged when we have to choose... Thx again averybody for helping them, and once again feel yourself in the "Who to bug on IRC" section fo the Summer of code idea pages Cheers Jeremy
_______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
