Difference between revisions of "Summer of Code 2007"
Jon Phillips (talk | contribs) (→General Ideas) |
Jon Phillips (talk | contribs) (added overlay) |
||
Line 107: | Line 107: | ||
* [[User:Nathan Yergler|Nathan Yergler]] (nyergler) | * [[User:Nathan Yergler|Nathan Yergler]] (nyergler) | ||
[[Image:Example.jpg]] | [[Image:Example.jpg]] | ||
+ | |||
+ | == External Links == | ||
+ | |||
+ | * [http://code.google.com/soc/ Google Summer of Code (SoC)] | ||
+ | * [http://code.google.com/soc/studentfaq.html Google SoC FAQ] |
Revision as of 17:53, 23 April 2006
Creative Commons is participating in Google's Summer of Code 2006 as a mentoring organization.
This page highlights ideas for Google Summer of Code student proposals and feature updates as the program progresses.
Contents
Students
If you find an idea listed below that you like, we encourage you to read up about the Creative Commons Developer Community, 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:
- HOWTO Write Project Proposals
- Inkscape's Accepted Proposals
- Internet2 Experience
- Portland State University Experience
- http://venge.net/monotone/summerofcode.html
- http://www.internet2.edu/~shalunov/tmp/rwatson-soc.txt
Selection Criteria
Please read the Selection Criteria. Participants who read this will be much further along than others.
Questions
- Read up about the Creative Commons Developer Community
- Join the cc-devel mailing list and ask questions
- Join the 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
Find (Search)
Any new tools which support finding of content licensed with a Creative Commons license
ccTools
The general tools created to work with Creative Commons licenses and content licensed with these licenses.
ccHost
- Extend ccHost to work with new media filetypes and push changes up-stream to getid3()
- Setup and build a video version of ccmixter.org using cchost.
- Implement sample pool API in other web backends or software applications
ccPublisher
LiveCD
Create an Open Source LiveCD which add some CC-licensed content and features the Creative Commons Tools/Software. 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.
Applications
- Integrate finding and publishing of CC licensed content directly within applications like OpenOffice.org, The Gimp, and [1]
Desktop
- Integrate finding and publishing of CC licensed content directly within the Open Source Desktop (think Gnome or KDE integration).
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.
Plugins
- Develop plugins that utilize Creative Commons licenses and metadata in your favorite applications
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
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
Libraries
- libcclicense
- libarchiveorg - make a lower level c-library of PyArchive
Mentors
- Mike Linksvayer (mlinksva)
- Jon Phillips (rejon)
- Nathan Yergler (nyergler)