Summer of Code 2006

2012-05-20T04:45:56Z

Shellyalicia:

[[Category:Developer Challenges]]
[[Category:Developer]]
[[Category:Summerofcode]]

Creative Commons is participates in [http://code.google.com/soc/ Google's Summer of Code] as a mentoring organization. Submissions for SoC 2007 will open in March; see the [http://code.google.com/support/bin/answer.py?answer=60325&topic=10729 timeline] for more details. A list of projects accepted for SoC 2006 is available [[Summer of Code 2006 Projects|here]].

This page highlights ideas and suggestions for student proposals.

== 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 '''March 14, 2006''' and close '''March 24, 2006'''. Final decisions by Creative Commons will be made by '''April 9, 2006''' for submission to Google.

== 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.

=== 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://www.ksaday.com/2012/01/gemscool.html ge][http://getid3.sourceforge.net/ tid3()].
* Implement the [[Sample Pool API]] in other web backends or software applications

=== 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 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) ===

* '''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] [http://www.ksaday.com/2012/05/laptop-murah-terbaru.html Laptop] [http://laptop.media.mit.edu/ 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/ Spotli][http://www.ksaday.com/2012/05/games-gratis.html g][http://www.apple.com/macosx/features/spotlight/ ht] 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 ===

* 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 ===

* 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]

Public domain

2012-04-04T01:23:56Z

Shellyalicia: /* See also */

When a work is in the public domain, it is free for use by anyone for any purpose without restriction under copyright law. Public domain is the purest form of open/free, since no one owns or controls the material in any way.

Works that are in the public domain in one legal jurisdiction are not necessarily in the public domain worldwide. Copyright laws differ from jurisdiction to jurisdiction, both in duration of protection and what constitutes copyrightable subject matter. For example, [http://www.usa.gov/copyright.shtml a US Government work] -- clearly in the public domain in the United States -- may or may not be free of copyright restrictions and in the public domain in other jurisdictions. At present, one of the only ways to be certain that a particular work is in the public domain worldwide is to see if the copyright holder has dedicated all rights to the work to the public domain by using [http://creativecommons.org/about/cc0 CC0].

Creative Commons licenses do not affect the status of a work that is in the public domain under applicable law, because our licenses only apply to works that are protected by copyright. For more information, see [[Before Licensing| our Licensing Guide]] to what you should know before you license a work using CC licenses.

Find out more about [http://creativecommons.org/publicdomain CC's public domain tools], and learn more about [http://en.wikipedia.org/wiki/Public_domain the public domain].

== When does a work enter the public domain? ==

This varies by country. To see when a work in the [[United States]] enters the public domain, see [http://www.copyright.gov/pr/pdomain.html copyright.gov's public domain page].

Cornell University has also provided a [http://www.copyright.cornell.edu/public_domain/ handy table about copyright term and the public domain] in the United States.

== Creative Commons public domain tools ==

* [[CC0]] (occasionally written as CC Zero) is a public domain dedication that allows copyright holders to place works in the public domain to the extent legally possible, worldwide.
* CC's [http://creativecommons.org/publicdomain/mark/1.0/ Public Domain Mark] allows anyone to mark a work that is already free of copyright restrictions around the world.

See http://creativecommons.org/publicdomain for more information on CC's public domain tools.

Public domain content in practice is any content without copyright. It may be deliberately freed from restrictions by the copyright owner, or the copyright may lapse after a certain time.

The legal details in practice vary between countries. More information about public domain can be found at [http://en.wikipedia.org/wiki/Public_domain Wikipedia's article on the public domain].

== Appropedia's Public Domain Search ==

[http://www.appropedia.org/Appropedia%27s_Public_Domain_Search Appropedia's Public Domain Search] was started in late 2007 when it was discovered there was no effective public domain search available. This operates on a completely different method to searches using the Creative Commons marks. It uses a manually maintained index of sites known to be public domain - thus it is does not yield 100% public domain results, and content must be checked to confirm public domain status. Reliability is expected to improve, and feedback by users is encouraged.

As CC public domain tools become widely used, searches based on the CC marks would be expected to take over from Appropedia's Public Domain Search.

== See also ==

* [[Cultivating the Public Domain]]
* [http://www.ksaday.com/ Berita Terbaru] and [http://www.compozt.com/ Free All World]
{{Translations
| articles = Hr:Javno dobro, Pt:Domínio público, Ru:Общественное достояние
}}

[[Category:Public domain]]

Creative Commons - User contributions [en]

Summer of Code 2006

Public domain