Difference between revisions of "Summer of Code 2007"

From Creative Commons
Jump to: navigation, search
(added first go over)
(→‎General Ideas)
Line 49: Line 49:
 
* Any new tools which support publishing of content licensed with a Creative Commons license
 
* Any new tools which support publishing of content licensed with a Creative Commons 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.
 
* 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.
 +
** joomla, drupal, civicspace, plone,
  
 
=== Find (Search) ===
 
=== Find (Search) ===
  
 
* Any new tools which support finding of content licensed with a Creative Commons license
 
* Any new tools which support finding of content licensed with a Creative Commons license
 +
** beagle, tracker, spotlight (continue/finish)
 
* Extend the [[CcNutch]] codebase to support [[RDFa]] and image, audio, or video search (using scoped metadata, not image/audio/video analysis!)
 
* Extend the [[CcNutch]] codebase to support [[RDFa]] and image, audio, or video search (using scoped metadata, not image/audio/video analysis!)
 +
* Feed aggregators
 +
** Add cc licenses and metadata support
 +
** A feed mashup library
  
−
=== ccHost ===
+
=== Expand Other Software with ccHost's Features or 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
 
* Implement the [[Sample Pool API]] in other web backends or software applications
 +
** wordpress, mediawiki, plone, drupal
 +
* Remix tracking within software or site
  
−
=== ccPublisher ===
+
=== Expand Software with ccPublisher's Features or ccPublisher ===
  
 
* 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 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.
+
** Embedding of XMP in various formats
−
 
+
* 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.
−
=== LiveCD (and other CD/Disc Distributions) ===
+
* Add ccPublisher's publish mechanism to an other application
−
 
 
−
* '''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 ===
 
=== Desktop Applications ===
Line 74: Line 77:
 
* 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.
 
* 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.
 
* 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.
 +
** HIGH-PRIORITY: OpenOffice.org, Other Open Source apps, Jokosher
  
 
=== Desktop Integration ===
 
=== 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.
 
* 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.
 +
** Beagle, Tracker, etc
 
* 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.
 
* 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]].
 
−
*Build an audio or video editing/mixing application with CC support or add support for importing and using CC licensed material and licensing remixes to an existing project such as http://www.diva-project.org
 
  
 
=== Web Mashups ===
 
=== 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
+
* 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, a website, or cross-platform software project which add attribution and basic license information into and/or onto media. The "into" part deals with embedding metadata inside of the media files. The "onto" part deals with some type of media overlay onto the content to identify who a work is attributing to, the license being used, and a URL to the license. Have fun with this one to create interesting creative content that conveys the license. [[Frequently_Asked_Questions#Can_I_apply_a_Creative_Commons_license_to_an_offline_work.3F|See this link on how to properly add a CC license to a work]]
 
−
** Photos: this would create some basic graphical overlay on the image, or basic html wrappers around the content that says author name, license (url). (Think simple banner)
 
−
** Audio: Add a small snippet of audio stating the license, url to license, and the author name somewhere in the file (beginning or end) (Think quick PSA)
 
−
** Video: Create a video bumper that is at the beginning (preferably) or end of a video that states the type of license being used, url to the license, and the author name/url. (Think opening credits)
 
−
** Other Media: Please propose other ways one could attribute authorship on the media itself
 
  
 
=== Open access publishing and Science ===
 
=== Open access publishing and Science ===

Revision as of 23:31, 21 February 2007


Creative Commons is participates in Google's Summer of Code as a mentoring organization. Submissions for SoC 2007 will open in March; see the timeline for more details. A list of projects accepted for last year's SoC 2006 is available here.

This page highlights ideas and suggestions for student proposals for 2007.

Students

If you find an 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 Creative Commons Developer Community, ask questions, and then include the following in your proposal:

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

Writing Proposals

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

Selection Criteria

Please read the Selection Criteria. Participants who read this will be much further along than others.

Questions

  1. Read up about the Creative Commons Developer Community
  2. Join the cc-devel mailing list and ask questions
  3. Join the Creative Commons chat channel, #cc, on irc.freenode.net.

Deadlines

TBD

General Ideas

More ideas are avaible in the Developer 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
  • 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.
    • joomla, drupal, civicspace, plone,

Find (Search)

  • Any new tools which support finding of content licensed with a Creative Commons license
    • beagle, tracker, spotlight (continue/finish)
  • Extend the CcNutch codebase to support RDFa and image, audio, or video search (using scoped metadata, not image/audio/video analysis!)
  • Feed aggregators
    • Add cc licenses and metadata support
    • A feed mashup library

Expand Other Software with ccHost's Features or ccHost

  • Implement the Sample Pool API in other web backends or software applications
    • wordpress, mediawiki, plone, drupal
  • Remix tracking within software or site

Expand Software with ccPublisher's Features or ccPublisher

  • Implement support for embedding license metadata in additional file types; this support would be in the form of additions to the cctagutils library. Contact Nathan Yergler for details or specifics.
    • Embedding of XMP in various formats
  • Implement back-end support for other publishing platforms, such as Flickr, My Space, etc. Basic documentation on storage providers has been started.
  • Add ccPublisher's publish mechanism to an other application

Desktop Applications

  • Add support for selecting a license within open source applications such as the above. A successful implementation will use the web services to provide up to date license information.
  • Integrate finding and reusing of CC licensed content directly within applications like OpenOffice.org, The Gimp, Inkscape, Audacity, etc.
    • HIGH-PRIORITY: OpenOffice.org, Other Open Source apps, Jokosher

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.
    • Beagle, Tracker, etc
  • Extend the CC licensing extractor for Spotlight to support multiple file formats and polish it to release quality. Issues which must be addressed include extractor chaining and packaging.

Web Mashups

  • Its all the craze! Develop some 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.

Open access publishing and Science

  • Create or add CC licensing and RDFa support to an 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 Uniprot or other CC-licensed dataset enabled by CC licensing.

Bonus Points

An ideal proposal would include support for RDFa, remixing, 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 Summer of Code Student FAQ and advice from past participants as you create your proposal. Good luck!

Mentors

External Links

Retrieved from "https://wiki.creativecommons.org/index.php?title=Summer_of_Code_2007&oldid=5308"