Google
Summer of Code 2011
AbiWord
Kathiravelu Pradeeban
Contents
✔ Why GSoC?
✔ Before you begin..
✔ Why AbiWord?
✔ Right Project?
✔ Shout!
✔ Apply.
✔ Code.
✔ Conclude/Continue. 2
Google Summer of
Code (GSoC)
✔ Code for a chosen open source
project for 3 months.
✔ Google pays you!
3
Some statistics of
GSoC - 2010
✔ 150 Organizations
✔ Submitted
- 3,464 students.
- 5,539 proposals.
- 36 proposals per organization.
✔ Accepted
- 1026 students/projects.
✔ 943 mentors. 4
Success Rate is
pretty high!
✔ Passed Midterm-Evaluations
- 964 Students.
- Success rate upto Mid- 90+%
✔ Passed the Final-Evaluations
- 917 Students
✔ Success rate - 89%
5
Why Google Summer
of Code?
6
What do you need?
7
Time Line (2011)
✔
January 24th : Program Announced.
th th
✔
February 28 – March11 :
Organizations apply.
th
✔
March 18 : List of Accepted
Organizations.
✔
March 18th - 27th : Students discussing
project ideas.
✔
March 28th – April 8th : Students
application period. 8
Time Line [After
getting accepted..]
✔
April 25th : Accepted Students
announced.
: Community Bonding Period Begins.
✔
May 23rd : Coding Begins.
✔
July 11th – July 15th : Mid Evaluations.
✔
Aug 15th – Suggested Pencils Down.
✔ Tests, Documentation improvements,
etc.
9
Time Line
[Concluding]
✔
Aug 22nd – Firm Pencils Down.
✔ Stop Work!
✔
Aug 26th – Final Evaluation Deadline.
✔
Aug 29th – Final Results.
✔
Aug 30th – Begin Code Submission to
Google.
10
Why AbiWord ?
✔ Have a look at the list of organizations
of GSoC2010.
✔ 152 organizations last year!
✔ Some new organizations each year.
✔ AbiWord has participated in all the
Google Summer of Code's since
2006.
11
Before you begin..
✔ Google Summer of Code is all about
being Open Source.
✔ Get your basics right.
✔ Netiquettes.
✔ Sign up to the lists.
✔ Join the irc channel – #abiword at
irc.gnome.org
12
Technologies ..
✔ Language -
✔ C++
✔ Version Control Systems -
✔ SVN
✔ IDE -
✔ Microsoft Visual Studio, Anjuta, ..
✔ Whatever you are comfortable with.
✔ Issue Tracker - Bugzilla
13
Network Etiquettes
✔ NO CAPS! (UNLESS YOU ARE SHOUTING!)
✔ Don't take messages personally.
✔ Be ethical; respect.
✔ Be Specific and clear.
✔ Research (google.. ;)) before asking.
✔ Be helpful to others.
✔ Dn't snd ur sms msgs to thrds or lsts.
✔ Language/English 14
Mailing lists
✔ Avoid HTML mails.
✔ No [URGENT]/[IMPORTANT] tags.
✔ No unnecessary attachments.
✔ No Cross Posting.
✔ Don't hijack threads.
✔ Post only to the relevant list (user/dev)
✔ Check the mail archives first.
15
IRC Etiquettes
✔ Be an observer first.
✔ Refer to others using their irc nick.
✔ Don't expect immediate replies; wait.
✔ Don't post bulk of text into irc.
✔ Post error logs to http://pastebin.com/
or http://paste.ubuntu.com/ and
share the url instead.
16
Find THE right
project..
✔ Go through the projects/ideas list.
✔ Will be updated more.
✔ Have a look at the last year's.
✔ Mailing lists
✔ Dev - abiword-dev@abisource.com
✔ User - abiword-user@abisource.com
✔ Commit - abisource-cvs-
commit@abisource.com
✔ Talk to the mentors - IRC, mail, .. 17
What makes you
special?
✔ Your interests and motivation
- Pick something you really enjoy
doing.
✔ Experience
- Being a great user doesn't
necessarily mean that you can be a
good developer.
✔ Opportunities
18
- What makes you the right person?
Experience
✔ Prove It!
- Patches.
- Assist other students!!!
- Bug reports and fixes.
19
Opportunities..
✔ Project that matches your previous
work.
✔ Choose the right one.
20
Shout!
✔ Communicate early.
✔ Communicate often.
✔ Ask questions.
✔ Most importantly, Answer others'
questions!
✔ Mentor is your friend!
21
Be Known..
✔ NO Sir, Madam..
✔ First Name or Preferred calling name.
✔ No Mr. Dr. either.
✔ Be heard!
✔ Be visible!
✔ Be responsive!
✔ Be quick! 22
Apply
✔ Register as a student for GSoC.
✔ Feel free to use AbiWord's wiki for
draft proposal.
✔ Get mentor's opinion and improve.
✔ Apply on Google.
✔ Can edit later (till the last minute!)
✔ Check often for the mentor/developer
comments and attend to them.
23
Propose.. ♡
✔ How to impress the
mentor/developers?
✔ Stick to the organization's template.
✔ Abstract.
✔ Introduce yourself properly.
✔ Focus on the relevant facts.
✔ Why do you fit? Your skill sets.
✔ List of the patches you have
submitted. 24
Propose ..
✔ Synopsis/Short-description
✔ Proves you got it correct.
✔ Benefits
✔ Benefits to AbiWord and other
projects.
✔ Deliverables
✔ Code, Documentation, test cases, ..
✔ Project Details
25
✔ A detailed description of the project.
Propose ..
✔ Project-Schedule / Time line
✔ Finer details.
✔ Testing takes time.
✔ Don't be overoptimistic.
✔ Starting/ending time. Any absence in
middle or conflicts.
✔ Bio – How do you fit AbiWord and the
particular project?
✔ References and additional details. 26
After the submission..
✔ Don't go invisible!
- Evaluation is still going on.. ;)
✔ You may be asked to provide
additional information.
✔ Start coding on your project. (only if
you didn't apply for multiple projects)
✔ Be motivated.
27
Got Selected?
YAYYY!!!
✔ Don't Panic.
✔ You have one more month just to
mingle with the developers and the
code base.
✔ Mentor(s) are there to help you!
✔ Keep touch with the developers.
✔ Users.
28
Community Bonding
Period
✔ Go through the code base and
documentation.
✔ Coding styles and coding guide lines.
✔ Start with simple hacks.
✔ Understand the project idea more.
✔ Come up with a design.
✔ Communicate often
✔ irc/dev list/wiki 29
Coding (Easiest task
of all.. ;))..
✔ Commit often.
✔ Meaningful Commit messages.
✔ Keep others updated (Daily ?).
✔ IRC, dev list, personal mails (if you
prefer, but not encouraged), wiki,
blog posts
✔ Get feedback from the mentor(s).
✔ Plan for the mid and final evaluations
early, with the mentor. 30
Conclude/Continue..
✔ Pencils Down Date
✔ Firm Pencils Down Date
✔ GSoC Coding ends here.
✔ Get a tarball of all the diff files to
submit to Google.
✔ Keep contributing to AbiWord.
31
Project Ideas for
2011..
✔ http://www.abisource.com/wiki/Google_Summer_of_Code_2011
32
Some links.. ;)
✔ GSoC-2011 FAQ
✔ GSoC-2011 Home Page
✔ GSoC Student Guide
✔ GSoC-2011 AbiWord
✔ Compiling AbiWord
✔ Developing on Windows using MSVC
33
For more
Information ..
✔ Join GSoC Discuss Group -
http://groups.google.com/group/google-
summer-of-code-discuss
34
Wish you all the best..
35