1 |
On 2/26/08, joshua jackson <tsunam@g.o> wrote: |
2 |
> Rémi Cardona wrote: |
3 |
> > joshua jackson a écrit : |
4 |
> >> 2) We need mentors, so far confirmed I have: Diego and Saleem |
5 |
> > |
6 |
> > What kind of work is involved there? I wouldn't mind being a mentor |
7 |
> > but I'd like to know a bit more about what's expected from a "good" |
8 |
> > mentor. |
9 |
|
10 |
I hope to have documentation up by the end of the week. |
11 |
|
12 |
> > |
13 |
> > Thanks, |
14 |
> > |
15 |
> > Rémi |
16 |
> |
17 |
> There's a few requirements. Being decent in a language or multiple |
18 |
> languages would certainly be a plus, as the students are writing code. |
19 |
> having someone writing something in C or C++ when you've never touched |
20 |
> it wouldn't exactly work out that well obviously. |
21 |
|
22 |
You will reviewing the student's ideas and work. You will need |
23 |
whatever skills are required to to that; it will depend highy on what |
24 |
project you choose to mentor. |
25 |
|
26 |
> |
27 |
> Having time to interact with the student as well. They are getting paid |
28 |
> as are we as an organization, so helping them and giving them idea's is |
29 |
> needed. Touching base and making sure they are still progressing on |
30 |
> their projects. Its summer...but they are being paid to work so it is a |
31 |
> job as I hope as a mentor you would take a similar approach as well. |
32 |
|
33 |
You should expect to spend a minimum of five (5) hours a week doing |
34 |
reviews of your student's code. Ideally you would make remarks for |
35 |
readability and documentation as well as design and implementation. |
36 |
You should meet with your student regularly to discuss progress; if |
37 |
the student is having problems they should be brought up and dealt |
38 |
with. You should run your students code to make sure it functions as |
39 |
he or she said it would. If it has tests, run those too. If it |
40 |
doesn't have tests; ask the student to write some ;) |
41 |
|
42 |
> |
43 |
> Basically you act as a technical boss/mentor/leader to someone. |
44 |
|
45 |
I would argue that you are a peer, not a boss. In the end, someone |
46 |
the student should probably take advice from in order to have a |
47 |
decently working product by summer's end. |
48 |
|
49 |
> |
50 |
> One area I'm working on for this year is goals within the overall goal |
51 |
> that can be implemented hopefully even if the project isn't fully |
52 |
> finished before the end of the project. |
53 |
> |
54 |
> For the mentor it won't be a full time commitment but having time to |
55 |
> talk with/help someone with their project and explain how to implement |
56 |
> this feature or get this information from Gentoo's system would take |
57 |
> some time. |
58 |
> |
59 |
> As a warning some people come on board with excellent programming |
60 |
> ability that you don't need to do much with/for. Some well its their |
61 |
> first real jump into programming and need more attention. I plan on |
62 |
> having a few additional questions for the Gentoo related applications to |
63 |
> help define that kind of thing and hope to get people together in such a |
64 |
> way. |
65 |
|
66 |
While true I don't think it is fair for the 'superstar' guy to just |
67 |
let him do whatever. |
68 |
*review their code*. Read it, run it, see what it does. If the |
69 |
student says they wrote it in 3 hours and it is awesome and well |
70 |
commented try running it through a profiler; find places where it |
71 |
could be improved. Look for poorly implemented algorithms, memory |
72 |
leaks, over-use of memory etc... |
73 |
|
74 |
> |
75 |
> As well a few of the people who are helping run it have agreed to help |
76 |
> poke/get updates from the mentors and step in and help in whatever way |
77 |
> possible to the students as well. Basically, we want as many projects to |
78 |
> succeed as possible and become a daily tool or vastly improved tools as |
79 |
> possible. Its certainly something that is possible. |
80 |
|
81 |
My ideas are all insane (I probably only did half when I was a mentor) |
82 |
but I want the students to have a good experience and I want the code |
83 |
to not suck and that requires a mentor who actually gives a damn and |
84 |
is willing to put time into it. |
85 |
|
86 |
-Alec |
87 |
|
88 |
> |
89 |
> |
90 |
> -- |
91 |
> gentoo-dev@l.g.o mailing list |
92 |
> |
93 |
> |
94 |
-- |
95 |
gentoo-dev@l.g.o mailing list |