Cassio Melo cassio'ufpe at gmail'com

1
Cassio Melo cassio.ufpe at gmail.com
May/2008
2
Summary - GSoC

• What?
• Why?
• When?
• How?
• The GSoC process
• An Application Example
• Successful SoC projects
• References

3
What?
4
Google Summer of Code http//code.google.com/soc
/

• The Google Summer of Code is a program designed
  to encourage college student participation in
  open source development
• includes most major opensource projects
• GNU, Blender, Debian, Fedora, Gentoo, FreeBSD,
  GCC, GNOME, KDE, OLPC, Mozilla, Mono, Python,
  Ubuntu, Apache, Wikipedia, Samba, X11, ... plus
  about 120 others

5
Program Statistics
6
Why?
7
Why?

• The program has been exceptionally successful
  both for Google and for the participating
  organizations/projects
• Can attract advanced degree research efforts,
  talented students
• Students are eager and work exceptionally hard on
  their projects (in fact, they usually propose
  their own project topics)
• Successful collaboration model for remotely
  interacting as part of an open source project
  with community resources in place

8
When?
9
GSoC 2008 Timeline

• March 3-12 Google will accept applications from
  open source projects.
• March 13-17 Google program administrators review
  organization applications.
• March 17 List of accepted mentoring
  organizations published on code.google.com/soc/
• March 24-31 Student applications acceptance
  period.
• Interim Period Would-be student participants
  discuss application ideas with mentoring
  organizations.

10
GSoC 2008 Timeline

• March 24 Student application period opens.
• April 14 accepted student proposals announced at
  code.google.com/soc/
• May 26 Students begin coding for their GSoC
  projects.
• July 14 Mid-term evaluations deadline.
• September 1 Final evaluation deadline.
• September 3 Students can begin submitting
  required code samples to Google.

11
Student stipends

• Google will provide a stipend of 5000 USD per
  accepted student developer, of which 4500 USD
  goes to the student and 500 USD goes to the
  mentoring organization.
• Accepted students in good standing with their
  mentoring organization will receive a 500 USD
  stipend shortly after coding begins on May 26,
  2008.
• Students who receive passing mid-term evaluations
  will receive a 2000 USD stipend shortly after the
  mid-term evaluation deadline, July 14, 2008.
• Students who receive passing final evaluations
  and who have submitted their final program
  evaluations will receive a 2000 USD stipend and
  mentoring organizations will receive 500 USD
  shortly after the final evaluation deadline,
  September 1, 2008

12
How?
13
How?

• Open source organizations (e.g., BZFlag, Blender,
  Gentoo) are invited or apply to participate
• Students submit project proposals to the
  organizations, organizations rank the submissions
• Google allocates a given number of slots to each
  organization, the students work all summer on
  their project in close mentored collaboration
  with that organization

14
Google
Mentor Organization
The GSoC Process by Morrison
Student
15
Applying

• Participate actively in discussion lists, sending
  patches to the community.
• Your project idea must be aligned with
  organizations expectations show to the
  community your idea, ask for suggestions
• Make a plan together with the mentoring
  organization
• Be honest enough to assume if you never
  participated, but you are willing to do so
• Think about what you would like to do, before
  anything else

16

• An application for Google Summer of Code 2007,
  Creative Commons project
• OpenOffice.org Writer add-in for publishing CC
  licensed documents
• 
  
• Cassio de Albuquerque Melo ltcassio.ufpe at
  gmail.comgt
• Summary
• IP issues are becoming critical in all areas.
  Adobe has recognized that by developing XMP
  platform. Creative Commons is an important way of
  adding IP licensing information to a document's
  metadata. Despite being a requested feature for
  OpenOffice.org for more than two years, nothing
  has materialized. http//www.openoffice.org/issue
  s/show_bug.cgi?id66656 filed in June 2006
  http//www.openoffice.org/issues/show_bug.cgi?id2
  9404 filed in May 2004. We can't wait anymore.
  The goal of this project is to provide a tool for
  supporting the process of licensing documents.
  Microsoft Office has a Creative Commons plug-in
  to put IP metadata in its documents. I propose a
  similar Creative Commons add-in for
  OpenOffice.org that would allow license
  information to be embedded in OpenOffice.org
  documents. http//www.openoffice.org/issues/show_
  bug.cgi?id29404 is an example of one way this
  tool could be used. Having a simple way to add
  Creative Commons licenses will help to spread
  those licenses much more broadly.
• Benefits
• My vision is to encourage the use of CC licenses
  in documents. Authors can express their
  intentions regarding how their works may be used
  by others. Implemented suitable interface will
  make easy the licensing process. This feature is
  very important for OOo end-users. Moreover,
  implementation of such add-in will increase CC
  marked documents. Of course, this metadata
  inserted only provides a first approximation of
  the license. Users are encouraged to read the
  full license to make sure it meets their
  expectations.
• Plan
• This project will build upon existing work.
  Development will consist of 3 main parts

17

• Deliverables
• Brief list of deliverables
• - Requirements document the features to be
  implemented in a high-level abstraction level,
  classified by priority
• - Project plan the plan of development,
  including a detailed schedule and release plan
• - Release report a document describing the
  currently status of the release
• - Progress report a weekly project status
• - Update the OpenOffice wiki page
  http//wiki.creativecommons.org/OpenOfficeOrg_Add
  in
• - Fully functional OOo plugin
• - A Patch to OpenOffice if necessary.
• These assets will be available in project and
  will be evaluated frequently by the assigned
  mentor. All the releases schedule, including its
  features will be defined in the Project Plan
  which will be delived at the beginning of SoC
  program.
• Qualifications
• I believe that I'm a suitable person to carry
  out this project. As a long-time OOo user I'm
  well too aware of the fact that OOo needs support
  to CC licences.
• I did work for a summer in my undergraduate
  course with the R.i.S.E Reuse in Software
  Engineering - http//www.rise.com.br team at
  Federal University of Pernambuco, which is an
  Open Source project though felt more like a
  University project! -) https//simple.dev.java.n
  et/ They do have very good practices for source
  control, reviews, mailing list, etc. I also
  understand the importance of good coding and
  documentation for projects.
• This (academic) year, I developed an OOo plugin
  to replace the existing OOo notes. Public
  distribution will begin in the near future.
  Additionally I have a year of industrial
  experience, having worked as a software engineer
  on C.E.S.A.R Recife Center for Studies and
  Advanced System - http//www.cesar.org.br in a
  ant/CVS indexer project.

18
Successful GSoC projects

• add yours in this section

19
Creative Commons Add-in for OpenOffice.org (a SoC
2007 project)

• Creative Commons is a not-for-profit organization
  that promotes the creative re-use of intellectual
  and artistic works, whether owned or in the
  public domain
• Creative Commons Add-in for OpenOffice.org allows
  users to select and embed a Creative Commons
  license in documents
• Writer (word processing documents)
• Calc (spreadsheets)
• Impress (presentations).
• The project was presented at OSCON 2007

20
Creative Commons Add-in for OpenOffice.org
21
Adding UML 2.0 Profiles support to ArgoUML

• ArgoUML
• UML CASE tool
• Currently supports UML 1.3 (with NetBeans MDR)?
• Offers tools for code generation to many
  programming languages (e.g. Java, C,SQL...)?
• Profiles are the default UML 2.0 language
  extension tool
• stereotypes
• tagged values

22
Adding UML 2.0 Profiles support to ArgoUML
23
Gsocers and mentors around the world (2007)
24
References

• GSoC offical page http//code.google.com/soc
• GSoC Blog http//googlesummerofcode.blogspot.com
• GSoC disscussion list http//groups.google.com/gr
  oup/google-summer-of-code-discuss
• Creative Commons Add-in http//wiki.creativecommo
  ns.org/OpenOfficeOrg_Addin
• Morrison presentation
• Google SoC presentation

25
Cassio Melo cassio.ufpe at gmail.com
May/2008