8/8/2019 Google Summer Code
1/45
i want 2 do
project. tell
me wat 2
do.Shakthi KannanGNU Free Documentation License
September 2008
Version 1.2
8/8/2019 Google Summer Code
2/45
WARNINGThe views expressed here are
those of the author (otherwise,why would it be here?). You are
welcome to agree to disagree,well, whatever. Any copying or
public performance of this
presentation is permissible (yay!)thanks to the GNU FreeDocumentation License.
8/8/2019 Google Summer Code
3/45
Beforeyou
begin...
8/8/2019 Google Summer Code
4/45
Sir Madam
Address people by their
First Name!
8/8/2019 Google Summer Code
5/45
No room for any
sentiments/emotionalfeelings.
Use /dev/null.
Be thick-skinned.
8/8/2019 Google Summer Code
6/45
Earnyour Living
8/8/2019 Google Summer Code
7/45
Hunger for
Knowledge
8/8/2019 Google Summer Code
8/45
so-called student
+degree
!=engineer
You cannot buyknowledge.
8/8/2019 Google Summer Code
9/45
Learn to
READ
READ
READ
8/8/2019 Google Summer Code
10/45
Read
Mailing
List
Guidelines!
8/8/2019 Google Summer Code
11/45
Collaborative DevelopmentProject Websites
http://sarovar.org
http://savannah.gnu.org
http://sf.net
http://freshmeat.net
http://sarovar.org/http://sarovar.org/8/8/2019 Google Summer Code
12/45
When you write to your mentor(s), mention:
Skillsprogramming languages, tools used.
Domain of interestapplication/system/databases/web/embeddedet.al.
Project time-frame
Also write something about yourself, anyprevious Free Software experiences, interestsetc.
8/8/2019 Google Summer Code
13/45
Don't make ORDERSlike these ...
i like to be a project member in your
team. please send me the details.
i want 2 do project. tell me wat 2do.
8/8/2019 Google Summer Code
14/45
no interest
+
final year project!=Free Software
project
8/8/2019 Google Summer Code
15/45
Have detailed
discussion with
the mentor(s)before starting the
project work!
8/8/2019 Google Summer Code
16/45
Communicationduring
the project ...
8/8/2019 Google Summer Code
17/45
Read
Free Software
CommunicationTools
8/8/2019 Google Summer Code
18/45
Englishis the accepted languagein the business world, and in the
Industry.
If your English is terrible, get help.
All your Peter jokes in school/college areuseless.
Welcome to the real world!
Get serious. Get help with your English.
8/8/2019 Google Summer Code
19/45
Language
ReadingComprehensionWriting
Bad grammar is acceptable. Atleast do a spell-check.
Spoken
8/8/2019 Google Summer Code
20/45
Every weekend
have a
one-to-onechatdiscussionwith
your mentor(s)
8/8/2019 Google Summer Code
21/45
Mentor(s), who work, are busyduring weekdays.
Don't disturb them duringweekdays, unless it is urgent.
Just sende-mail
during weekdays.
8/8/2019 Google Summer Code
22/45
If your English is terrible, don'texplain the error!
By trying to explain it in your
own words, you only make itworse!
Just copy and paste theoutput/error or log
messages.
8/8/2019 Google Summer Code
23/45
Not being
on timeis
unprofessional,rude,
awful!
Punctuality is important.
Time is precious!
As on date, you cannot undo time!
8/8/2019 Google Summer Code
24/45
If you are not able to make itto the online discussion with
your mentor(s),
inform!Mentor(s) can get to do theirwork rather than wait for you!
8/8/2019 Google Summer Code
25/45
When asking a question
in writing, put aquestion mark
at the end.
How does anyone know if you
are making a statement or
asking a question ?
8/8/2019 Google Summer Code
26/45
Doing the
project...
8/8/2019 Google Summer Code
27/45
Understand what mentor(s) can do ...
Mentor(s) CANNOT write project abstracts,
write code, do project documentation, prepare presentations,
... for you.Mentor(s) can only tell you what to do.
8/8/2019 Google Summer Code
28/45
Start with small tasks to
assess your progress,before you handle bigproject tasks.
Patience is the key tosuccess.
8/8/2019 Google Summer Code
29/45
Never ever do
last minute work!
Send status
updates on dailybasis!
8/8/2019 Google Summer Code
30/45
curve !
learning
a steepthrough
goingYou are
8/8/2019 Google Summer Code
31/45
Communicate like an engineer!
Always give detailed info when posting aproblem or asking a question.
Don't give blunt information like:
Internet is not working.
I have compilation problem.
8/8/2019 Google Summer Code
32/45
Communicate like an engineer!
Internet is not working.
What is the network setup? What did you try? How do you say it is not working? Which GNU/Linux distribution?
i lik i
8/8/2019 Google Summer Code
33/45
Communicate like an engineer!
I have compilation problem.
What source code? How did you compile? Which compiler? Where is the error output? Which GNU/Linux distribution?
8/8/2019 Google Summer Code
34/45
HOWTO report bugs
effectivelyhttp://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Bug Writing
Guidelineshttp://marianne.in2p3.fr/datagrid/bugzilla/bugwritinghelp.htm
http://www.chiark.greenend.org.uk/~sgtatham/bugs.htmlhttp://marianne.in2p3.fr/datagrid/bugzilla/bugwritinghelp.htmlhttp://marianne.in2p3.fr/datagrid/bugzilla/bugwritinghelp.htmlhttp://www.chiark.greenend.org.uk/~sgtatham/bugs.html8/8/2019 Google Summer Code
35/45
Keep journal/log of:
daily activities, e-mail correspondences, problems solved, HOWTOs/reference links.
Helps in project documentation.
8/8/2019 Google Summer Code
36/45
When you reply to e-mail or
questions, reply to all thequestions asked.
Don'tskipanything!
Same when following HOWTOs,documentation, tutorials et. al.
Over-enthusiasm can cause you to
8/8/2019 Google Summer Code
37/45
ymake your own decisions.
Never make your own
decisions!
Else, why do you need mentor(s)?
Always inform your team members,or consult your mentor(s) before
doing anything new
8/8/2019 Google Summer Code
38/45
When sending e-mails,
don't forget to CCall your team members.
If youintentionally/unintentionally
forget to CC, your team willlose trust in you!
If you keep
8/8/2019 Google Summer Code
39/45
y p
repeating
the same mistakesagain, and again, and again,
expect the mentor(s) to findother developers.
It is normal for people tomove in, and out of project
teams
C
8/8/2019 Google Summer Code
40/45
Can my
friend(s) alsojoin
the project?
Only if they get selected by the mentor(s).
8/8/2019 Google Summer Code
41/45
Never ask personal
questionsto your mentor(s).
It is none of your business.
Respect other peoples' privacy.
Write small code first and
8/8/2019 Google Summer Code
42/45
Write small code first, andsend it to your mentor(s) for
feedback.
Easy to correct smallmistakes on daily basis,
than to submit a chunk at theend of the week, and re-doeverything. PITA.
8/8/2019 Google Summer Code
43/45
Never makeassumptions.
Always give proof when
you make statements.
8/8/2019 Google Summer Code
44/45
Never hesitate to ask questions.
If in doubt, ask.
No harm in making sure you have understood.
Being silent gives the impression that you haveunderstood.
Feel free to have open discussions with your
mentor(s).
The more you hesitate, lesser the communication,more the communication gap, and project at stake!
8/8/2019 Google Summer Code
45/45
Impossibleis a word only to
be found inthe dictionary of fools.
~Napoleon
Top Related