View source for Summer of Code 2007

[[Category:TechChallenges]]
[[Category:Developer]]
[[Category:Summerofcode]]
[[Category:2006]]

Creative Commons is participating in [http://code.google.com/soc/ Google's Summer of Code 2006] as a mentoring organization.

This page highlights ideas for [http://creativecommons.org/weblog/entry/5857 Google Summer of Code] student proposals and feature updates as the program progresses. 

== Students == 

If you find an [[#General Ideas|idea listed below]] that you like or have your own idea for a Creative Commons-related open source project, we encourage you to read up about the [[Developer|Creative Commons Developer Community]], [[#Questions|ask questions]], and then include the following in your proposal: 

# Detailed description / design document
# an approximate schedule (timeline)
# brief description of past projects (including open source) that you've participated in
# brief resume/bio/contact information

== Writing Proposals ==

The following links detail successfull general ways to write a Summer of Code Proposal:

* [http://inkscape.org/wiki/index.php/SOC_Writing_Project_Proposals HOWTO Write Project Proposals]
* [http://inkscape.org/wiki/index.php/SOC_Accepted_Proposals Inkscape's Accepted Proposals]
* [http://www.internet2.edu/~shalunov/writing/soc2005.html Internet2 Experience]
* [http://summer.cs.pdx.edu/?q=node/12 Portland State University Experience]
* http://venge.net/monotone/summerofcode.html
* http://www.internet2.edu/~shalunov/tmp/rwatson-soc.txt

== Selection Criteria ==

Please read the [[Summer of Code Selection Criteria|Selection Criteria]]. Participants who read this will be much further along than others.

== Questions ==

# Read up about the [[Developer|Creative Commons Developer Community]]
# Join the [[Mailing Lists|cc-devel mailing list]] and ask questions
# Join the [[IRC|Creative Commons chat channel]], #cc, on irc.freenode.net.

== Deadlines == 

Student applications open on '''May 1, 2006''' and close '''May 8, 2006'''. Final decisions by Creative Comons will be made by '''May 22, 2006''' for submission to Google. 

== General Ideas ==

More ideas are avaible in the [[Tech Challenges]] section of the website. What follows is a generalized listing of quick ideas which any student may use to identify interests. Please do not be constrained by the ideas below, but please use them to jumpstart and understand the general areas we are interested in supporting.

=== Publish ===

* Any new tools which support publishing of content licensed with a Creative Commons license
* A DHTML version of http://creativecommons.org/license/ -- such a proposal should include design improvements that take advantage of a dynamic layout and incorporate licensing options currently on the left side of http://creativecommons.org/license/
* Develop plugins that utilize Creative Commons licenses and metadata in your favorite applications.  If these are web-based ideally licensing both at site-level and "object" (e.g., page, image) level should be supported, and [[RDFa]] metadata.

=== Find (Search) ===

* Any new tools which support finding of content licensed with a Creative Commons license
* Extend the [[CcNutch]] codebase to support [[RDFa]] and image, audio, or video search (using scoped metadata, not image/audio/video analysis!)

=== ccHost ===

* Extend [[ccHost]] to work with new media filetypes and push changes up-stream to [http://getid3.sourceforge.net/ getid3()].
* Implement the [[Sample Pool API]] in other web backends or software applications

=== ccPublisher ===

* Implement [[ccPublisher]] support for uploading works to [[ccHost]] installations.  Note that this may require working with the ccHost codebase as well.
* Implement support for embedding license metadata in additional file types; this support would be in the form of additions to the <code>cctagutils</code> library.  Contact [[User:NathanYergler|Nathan Yergler]] for details or specifics.
* Implement back end support for other publishing platforms, such as Flickr, My Space, etc.  Basic [[Writing_a_Storage_Provider|documentation]] on storage providers has been started.

=== mozCC ===
* Update and revise [http://yergler.net/projects/mozcc mozCC].  New features needed include support for [[RDFa]] embedded metadata and visualization of license information for specific elements (i.e. outlining an image if the metadata declares that the image is specifically licensed).

=== LiveCD (and other CD/Disc Distributions) ===

* '''LiveCD''': Create an Open Source [http://en.wikipedia.org/wiki/Live_CD LiveCD] which adds CC-licensed content and features the Creative Commons Tools.  Also, one should make a way to keep in sync with mainline LiveCDs so that this project does not have to maintain its own LiveCD.
* Another type of CD project would be a script which collects different high-quality CC-licensed content onto a standard disc sizes (CD, DVD) along with the different CC software projects (and the OS' they support). Important for this is to develop a strong way to automate the creation of these discs which could be used by [Freedom Toaster Kiosks http://www.freedomtoaster.org/], the [http://laptop.media.mit.edu/ $100 Laptop Project], and other projects. The ideas is that anyone could take an on-line ISO and burn it for use off-line.

=== Desktop Applications ===

* Add support for selecting a license within open source applications such as the above.  A successful implementation will use the [[Creative_Commons_Web_Services|web services]] to provide up to date license information.

* Integrate finding and reusing of CC licensed content directly within applications like [http://www.openoffice.org OpenOffice.org], [http://gimp.org The Gimp], [http://www.inkscape.org Inkscape], [http://audacity.sourceforge.net Audacity], etc.

=== Desktop Integration ===

* Integrate finding and publishing of CC licensed content directly within the Open Source Desktop (think Gnome or KDE integration).  A starting point for Gnome may be the prototype Nautilus extension for displaying license information embedded in MP3 files.
* Extend the [http://yergler.net/projects/cc-spotlight/ CC licensing extractor] for [http://www.apple.com/macosx/features/spotlight/ Spotlight] to support multiple file formats and polish it to release quality.  Issues which must be addressed include extractor chaining and packaging.

=== Media Mixing ===

* Build basic media mixing tools either for the Open Source Desktop or for the web (think AJAX) that allows for mixing of legal media files (photos, videos, music, etc) in order to create interesting remixes and art.
* Build an application (probably DHTML would be most useful) that allows one to drag licenses and see [[Frequently_Asked_Questions#I_used_part_of_a_Creative_Commons-licensed_work.2C_which_Creative_Commons_license_can_I_relicense_my_work_under.3F|how they may be combined]].

=== Web Mashups ===

* Its all the craze! Develop some [http://en.wikipedia.org/wiki/Mashup_%28web_application_hybrid%29 web mashups] by combining multiple different web-based APIs (creative commons, amazon, google, flickr, archive.org) to create a project that uses these APIs to help spread CC-licensing

=== Attributors ===

* Create scripts which add attribution and basic license information into media
** Photos: this would create some basic graphical overlay to the image, or basic html wrappers around the content that says author name, license (url).
** Other Media: Please propose other ways one could attribute authorship on the media itself

=== Open access publishing and Science ===

* Create or add CC licensing and [[RDFa]] support to an [http://en.wikipedia.org/wiki/Open_access open access publishing]] tool.  Example --
:It would appear a practical RDFa proposal would be around tagging a scientific HTML doc with the triples extracted and built with an NLP tool. The elements of the text, genes, diseases, pathways, therapeutics, etc, would be directly embedded in the text around such words (perhaps rendered as typed links) , while the triples of how they interplay would be represented as well. This would bring together the human readable world with the concept-codified space.

* An application that does something interesting with [http://creativecommons.org/weblog/entry/5778 Uniprot] or other CC-licensed dataset enabled by CC licensing.

== Bonus Points ==
* An ''ideal'' proposal would include support for [[RDFa]], remixing, [http://en.wikipedia.org/wiki/Open_format open formats] and affordances for educational and worldwide (not just wealthy regions) use. Ability to release under an open source license and incorporation of some Creative Commons affordance are necessary. However, a solid proposal is far more important than buzzword compliance.  Please read Google's [http://code.google.com/soc/studentfaq.html Summer of Code Student FAQ] and [[#Writing_Proposals|advice from past participants]] as you create your proposal. Good luck!

== Mentors ==

* [[User:Mike Linksvayer|Mike Linksvayer]] (mlinksva)
* [[User:Jon Phillips|Jon Phillips]] (rejon)
* [[User:NathanYergler|Nathan Yergler]] (nyergler)
* [[User:Alex|Alex Roberts]]

== External Links ==

* [http://code.google.com/soc/ Google Summer of Code (SoC)]
* [http://code.google.com/soc/studentfaq.html Google SoC FAQ]