Creative Commons - User contributions [en]

Estonia/3.0

2012-02-10T06:50:23Z

Halobigred:

{{License
|Porting status=Completed
|porting began=2009/06/19
|date published=2011/01/06
|mailing list url=http://lists.ibiblio.org/mailman/listinfo/cc-estonia
|institutions=Estonian Information Technology Foundation
|translations exist=Yes
|preport=Yes
|copyright length=Author plus 70 years
|law mirrors=No
|first language=et
|intended translations=et
|adaptation definition=Derivative Work (adaption) means a work that derives from another Work or is based on another Work or other pre-existing Works, such as a translation, an adaption of an original Work, an arrangement of music or other alterations of literary and artistic works as well as phonograms, performances and audiovisual works or any other form into which a Work may be transformed, changed or adapted, including any other form recognizably derived from the original Work. A Collection is not considered a Derivative Work for the purpose of this Licence. Where the Work is a musical work, performance or phonogram, the synchronization of the Work in time-relation with a moving image (“synching”) will be considered a Derivative Work for the purpose of this Licence.
|work definition=Work means a literary, artistic and a scientific work offered under the terms of this Licence. For the purposes of this Licence a performance of a Work, a phonogram, broadcast, first fixation (record) of a film and a database is considered to be a Work, to the extent it is protected by the Estonian Copyright Act.
|distribute definition=Distribute means to make available to the public the original Work as well as the copies and Derivative Works of the original Work via sale or other transfer of ownership (including [http://www.rentittoday.com lease and rental]).
|collection definition=Collection means a collection of Works, which, by reason of the selection and arrangement of its content, constitutes intellectual creation into which a Work is included in its entirety and in unmodified form along with one or more other Works, each constituting separate and independent Works that have been assembled into a collective whole, such as periodical publications, anthologies or encyclopaedias. A Work that constitutes a Collection will not be considered a Derivative Work (as defined above) for the purposes of this Licence.
|neighboring rights rec=Yes
|what neigh rights=Performance, Phonogram, Broadcasts, Other
|other neigh rights=The related rights are as follows: 1. Rights of Performers, 2. Producers of Phonograms and 3. Broadcasting Organisations. The chapter VIII in Estonian Copyright Act regulates this part. Unfortunately no official translation from Copyright Act being effective at the current period is compiled.
|protects databases under c=No
|sui generis db=Yes
|sui generis length=15 years
|stat comp regime=No
|rights waivable=Yes
|collecting societies=Eesti Authorite Uhing (Estonian Authors' Society)
|rec moral rights=Yes
|moral rights types=Right of Attribution, Right to Integrity, Right to have a work published anonymously or pseudonymously, Others
|other moral rights=Right of additions to the work, Right of protection of author’s honour and reputation, Right of disclosure of the work, Right of supplementation of the work, Right to withdraw the work, Request that the author's name be removed from the work which is being used
|moral rights term=Life of the author plus _ years
|moral rights term years=70
|moral rights waivable=No
|moral rights licenseable=Yes
|has cels=Yes
|cel type=Other
|other cel=Free Use
|warranties=Yes
|liability limits=Yes
|liability limit type=Disclaim all liability
|form requirements=Yes
|other mandatory provisions=No
|cc is license=No
|cc is contract=Yes
|contract infringement remedies=Damages
|contract damages remedies=General
|public disc=Yes
|pdr=Estonia Public Discussion Report.ods
}}

Grants/Patamu.com

2012-02-10T06:35:41Z

Halobigred:

{{Grant Application
|Project Title=Patamu.com
|applicants=Adriano Bonforti
|contact person=Adriano Bonforti, info@patamu.com
|coordinator=Adriano Bonforti
|start date=2010/06/30
|end date=2010/12/31
|Affiliation=Free Hardware Foundation, FPML.it
|Mainurl=http://www.patamu.com
|Affiliated=No
|description=Patamu.com is an new born site, with the aim to provide free and instantaneous time stamping and [http://www.rentittoday.com/storage-units-rentals self storage] of art works (such as music) and of any creative work in general, and it is intended for musicians, photographers, writers, poets, artists, journalists, bloggers, researchers, etc, to help them diffuse their works in CC protecting themselves from plagiarism. The contextual release of these works in a Creative Commons license is highly encouraged in our site. Patamu.com follows a Business Ethics model, offering a useful and complete free service for the basic user, and a premium service (almost at production cost) for professional users. Patamu.com is probably one of the first sites in Italy and in Europe to provide this kind of service. We also plan to develop a knowledge database and a blog containing information about CC, free culture world, and an overview on the world of royalties collecting companies, to provide users with a strong know how, and offer them orientation to pursue the diffusion of free art and culture.
|output=The first tangible output would be a new area of the site, implemented in the form of a blog and open source knowledge database, with all the useful information for users about creative commons licenses, and on how to integrate CC licenses with proof of authorship using the free time stamping service provided in Patamu.com or similar techniques. Another important project output would be the definition of the legal status of Patamu.com, and the eventual establishment of Patamu as a real and recognized company or organization, allowing the site to better pursue its aim for the diffusion of creative commons culture. Other outputs would be the translation of the site in other languages (2 European and 2 non European languages, of which 1 non OECD) and the completion of the English translation and, finally, an improvement in the technologies would be made, allowing the provision of better services for users. Newspaper articles will also be written during this 6 month period, to illustrate and promote the Patamu project.
|community=We are targeting the broad community of authors of creative works in general, such as musicians, writers, photographers, artists, but also scientists or journalists, or bloggers. In other words, anyone producing a creative work. Our site would help them to feel free to diffuse their works without the fear of being plagiarized (through the use of the digital time stamping). This, in synergy with CC licenses, would allow a better diffusion of artistic and cultural content, and allow many members of the community to obtain for free a service that is now provided almost only by royalties collecting societies. For instance, in Italy protection from plagiarizing is provided at high costs by the state royalties collecting organization SIAE, which binds the authors with many constraints on the use of their own creative works. Recent studies show that 90% of these authors don't even receive any royalties for their artworks, but nevertheless still use SIAE, even if it is only to prove their authorship. Patamu services would free all these people from the constraints of SIAE, by providing a viable, valid and non-constraining alternative for proof of authorship, thus encouraging them to spread their works in CC licenses. Furthermore, the know how database created in Patamu would help the community to better decide how to license and spread their works, and to have an overview of the best practicing and CC-integrated royalties collecting societies in various countries.
|community relationship=My personal knowledge in the field of plagiarism protection and free diffusion of creative works comes from the fact that I am a musician, a physicist, and I compose music, and so do my fellows. Therefore the project of Patamu was generated from our first hand experience and needs, and those of our network of connections, since a similar service was not available. We are in contact with many members of both the artistic and scientific community, and many of them feel the need of such a service. I have been in contact for a long time with "Free Hardware Foundation" and "FPML.it" networks for free culture, and our discussions, together with the feedback of their communities, helped me develop a pilot concept, which has finally recently come to life as Patamu.
|measurement=The impact of the project would be evaluated by the number of subscribers that will apply in the following months, as well as on the number of timestamped files and visitors to the site (especially in the new blog area). A special professional feedback feature will also be implemented, to interact as much as possible with the users and involve them in the discussion to improve the service and develop new features in the site. The impact on the larger community would be evaluated by the diffusion of the Patamu project awareness (also on newspapers, blogs,etc), and hopefully by the number of invitations that we would receive to participate in conferences or debates dealing with creative commons and free culture subjects to illustrate our project.
|participants=We expect to involve around 400-600 participants in the first 6 months. We will seek their involvement through an open source model for the site: everybody will be encouraged to interact and to propose new ideas to improve the service, through a feedback section, in which users can propose and vote ideas. At the same time, the users will be encouraged to collaborate in the blog area, thus creating a common and shared knowledge database regarding subjects related to the free culture and creative commons world. We will seek and sustain their involvement proposing a Business Ethic model, in which service is provided for free for non-pro users, young users or non profit organizations, and the project is economically sustained by the professional users. In this sense we already had a good feedback: since the unofficial launch on the site, 2 weeks ago, we already received many collaboration proposals from net-labels, non profit or ethic business organizations, and in the coming days a new EP will be released under Creative Commons licence, with protection from plagiarism and storage of the protected content provided by Patamu. At the same time, we already received the first few pro subscriptions. This shows that our model can work.
|impact=As a musician, I noticed that one of the fears of the artists releasing their works in Creative Commons is to be plagiarized. For this reason, sometimes the artists prefer to pay an amount to the royalties collecting societies which incidentally provide also protection from plagiarizing. In this way, unfortunately, their artworks are sometimes no more eligible to be released in CC licenses (this is for instance the case in Italy). By providing a free protection, and leaving the user free to release his artworks in any kind of license (the CC license is the one proposed in our site), together with our storage service, Patamu would improve the "sensation of safety" of the users, encouraging them to release their creative works in CC and increasing therefore the amount of cultural and scientific content freed in CC in Italy, and hopefully in other countries as well. The blog area, furthermore, would help the user to deepen his knowledge on the subject, and therefore to better choose the option that is more suitable for his needs.
|tech needs=The technologies used in the site are JOOMLA and the SSL technology. I bring to the project both my programming skills as a physicist and my experience in the creative commons and free culture area as a CC musician and composer. Our technical needs would be mainly high speed, high capacity and highly configurable Linux servers. We already have them, but they have an high monthly cost. Help from CC in this sense would help us to lower our monthly costs.
|challenges=The main challenge we have to face is the diffusion of our project. We plan to overcome it by making a big effort on spreading awareness of our project through the links that we have already established with organizations working in the free culture and CC area (such as the Free Hardware Foundation, Buskerlabel, Fpml.it, to give some examples in Italy) but also using other advertisement channels in popular social networks, or other similar places where our project can be immediately perceived as useful.
|sustainability=As already stated, we want to sustain our project through the pro subscriptions, which would help us keeping our basic service free. Great care is also involved in keeping the overall maintenance costs very low. Finally, several collaborations are underway for agreement, both to provide low cost services to Patamu, and to help other sites provide a similar service powered by Patamu.
On the other hand, with the CC funding we aim at publicizing our site in such a way that a broader community can be involved in its use, and more pro users can be activated. Our plan for the end of December 2010 is to have around 400-500 users, and of those around 80 with a pro subscription. This would be enough to spark a virtuous circle and to sustain the service costs for the following year.
|scalability=The Patamu project has already planned new areas of extension to provide further services to an expanding community of users, and will adjust and possibly differentiate its services according to the feedback received from the users.
The project is designed to be very flexible both in internal organization and in resources employed. Nevertheless the servers are already very powerful, to stand a possible sudden expansion, and the services themselves are studied and tested to sustain a bigger flow of traffic. Because of the relatively low start-up costs, the economical resources earned in case of success of the site will be mainly reinvested in upgrades of the site and of the related services.
|resource needs=Apart from the funding, a help on the hosting of the site would be very useful. We already have a high performance and high capacity server, which is highly reliable and configurable but also expensive. If CC could help by providing a similar server at zero costs, this would help us keep a high quality service, while lowering the maintenance costs. Another enormous help that CC could give us would be by spreading the knowledge of Patamu site and services in all the realities where this can be useful, and also helping us with legal and informative consultancies regarding the CC world, where this could be useful.
Finally, the CC funding could help us in defining the legal nature of Patamu by partially sustaining the high costs that are necessary in Italy to found an organization or a company. The funding could help us also to finance substantial upgrades of the site such as its translation, the development of the knowledge base area, and new service upgrades. Finally, the funding would be of great help to sustain a basic advertisement campaign to give visibility to the site.
|communication=Patamu actually communicates with its community through multiple channels: directly through the site for the already subscribed members, but also through some extended mailing lists having free culture as the main subject. Furthermore we are present in the main social networks, and the writing of newspaper articles on both mainstream and sectoral newspapers is underway. Finally, Patamu already participated in some meetings and debates about CC and free culture, and is already participating in some CC projects (such as the release of an EP) that can promote the service and the site.
|budget=Patamubudget.xls
|legal=Yes
}}

Partner Interface

2012-02-10T06:16:45Z

Halobigred: /* Part 2: Processing and Storage of license information */

[[Category:Developer]][[Category:technology]][[Category:guide]][[Category:Integration]]
{{Infobox|See [[Web Integration]] for information on all Creative Commons' integration tools.}}

== Web Integration Developer's Guide ==

''Integrating Creative Commons licenses into your web application''

While Creative Commons offers a range of license choices and public domain options direct from its license page, if you have created an application or built a website that allow people to contribute works you may prefer to integrate the license engine directly into your site or application. This guide serves to explain all the steps necessary and options available for integrating Creative Commons into your software. If you are integrating Creative Commons licenses with a non-web application, or would like more control over the user interface, the [[Creative Commons Web Services]] may be more appropriate.

This guide is generally split into three parts:

* [[#Part 1: Letting users select a license|Part 1: Letting users select a license]]
* [[#Part 2: Processing and Storage of license information|Part 2: Processing and Storage of license information]]
* [[#Part 3: Display of license information|Part 3: Display of license information]]

== Part 1: Letting users select a license ==

Whether your software is a website or a downloadable application, the first step to integrating Creative Commons licenses is letting users select a license directly from your software. The process involves loading a simplified Creative Commons license interface from within a popup window, embedded into your website, or launched from an HTML window control in your application. URL variables are read into the page and are appended when complete, allowing data to be extracted from the process and passed through it.

==== The remote license engine application ====

The heart of the process is running the remote license interface which is available at this URL:

http://creativecommons.org/license/?partner={partner}&exit_url={exit_url}&stylesheet={stylesheet}&partner_icon_url={partner_icon_url}

Note that the curly braces, i.e. {partner}, should be omitted. The full set of URL variables available are as follows:

<div class="code">

'''partner (required):''' The name of your application or site, used for tracking usage at Creative Commons. Any descriptive name can be added here.

'''exit_url (required):''' The return URL on your application that will load after a user selects a license and will contain appended variables in the URL that your software will need to read.

'''additional requirement:'''

Your exit_url must include "license_url=[license_url]" and may optionally include the license_name=[license_name], license_button=[license_button], and deed_url=[deed_url] variables. Explanation of each:

'''license_url:''' URL for the selected license. Link to this URL in the licensed page. Example: http://creativecommons.org/licenses/by/2.0/

'''license_name:''' Pretty name for the selected license. Example: Attribution

'''license_button:''' URL for the image corresponding to the selected license, useful for displaying on a licensed page. Example: http://creativecommons.org/images/public/somerights20.gif

'''deed_url:''' URL for the deed corresponding to the selected license. Usually this will be identical to the value of license_url, unless a "branded" license is selected. Note that even if deed_url is different than license_url, is is still valid to use the URL specified by license_url, as both will point to the same legal code. If you want to support this feature, link to the deed_url in the licensed page. Example: http://creativecommons.org/licenses/by-nc-nd/2.0/deed-music

A sample exit URL would be:

http://example.com/return_from_cc?license_url=[license_url]%26license_name=[license_name]

The license engine will replace the license_url, license_name, license_button, and deed_url variables with proper variables once a user has chosen a license (more on this in Part 2). The square brackets must be included for the license engine to properly replace the values.

Note that your exit URL can carry your application's URL variables into and out of the license application by URL escaping within your exit URL, for example:

http://example.com/return_from_cc?license_url=[license_url]%26license_name=[license_name]%26userID=42%26user-work=foo.jpg

The above example will let your application know that a userID of 42 that submitted a user-work titled foo.jpg selected a specific license on exit of the license engine.

If you want to maintain state but do not wish to pass data through the URL (e.g., for reasons of privacy or data size), consider saving the data in a user cookie (which will only be sent to your site, not creativecommons.org), save the data in a file or database and save a lookup key in a cookie or pass the lookup key via the URL, or use the popup or iframe methods (see below), which do not require the user to "leave" your form.

'''stylesheet (optional):'''

URL of a Cascading Style Sheet (CSS) file to customize the layout, look, and feel of the license questions. View source on the license engine to see the ID and classes available to be styled.

'''partner_icon_url (optional):''' if you'd like a custom image displayed at the top of the license application, add the image's URL in this variable.

''The following enable choosing licenses ported to the copyright law of specific legal jurisdictions. See the [[http://creativecommons.org/international Creative Commons international page]] for more information.''

'''jurisdiction (optional):''' Choose licenses of specified jurisdiction. With jurisdiction_choose on, sets pre-selected jurisdiction. You may use any jurisdiction code supported by the license engine.

'''jurisdiction_choose (optional):''' If set to '1', user will be given a list of jurisdictions to choose from.

'''lang (optional):''' Allows an override of the language used to present the user interface. A list of available languages codes is available from the [http://api.creativecommons.org/docs/readme_dev.html#locales API].
</div>

=== Invoking the remote license engine from your application ===

Once you have figured out the appropriate variables that will be fed into and out of the remote license engine, you need to invoke it from your website or application.

There are a few basic ways to accomplish this task:

* Popup window launched from your website
* Redirect from your website to license engine
* IFRAME embedded within your website
* Launched via HTML control within your desktop application

=== Popup window launched from your website ===

The most popular method of invoking the remote license engine is via a popup window. A user clicks something on a page that launches a small window containing the questions. After answering them, users proceed, the window closes, and the original page is updated to reflect their choice. Sites using this method will usually change a hidden form variable dynamically (using javascript) when the user finishes the license selection process.

Screenshot of popup below. Implementation example: [[Movable Type]].

[[Image:Choose_license_popup.png]]

=== Redirect from your website to license page ===

This option does not use popup windows of any kind and instead you leave the site you originated from, pick your license, then return to the site with your selection info for the site to decifer. Sites using this method would need to parse the URL variables within the return URL.

=== IFRAME embedded within your website ===

For those that do not want to use popup windows, have an audience using version 5.0 web browsers and up, and would like to keep the license selection within their application, an IFRAME can be used much like the popup. Sites using this method would embed the question form into their page, and upon completion, pass variables between the IFRAME and surrounding page.

=== Launched via HTML control within your desktop application ===

For desktop applications this method would essentially mimic the popup window code, but instead use a native HTML control within your application. On Windows, visual basic and visual C++ applications have access to an Internet Explorer HTML control that can be launched from within your application. For Mac programmers, OS X offers webcore controls that use Safari as a native browser environment from within your application.

== Part 2: Processing and Storage of license information ==

Once users of your website and application have the ability to select a license, the next step is processing the results of their selection. As mentioned in the previous section, the exit_url is the place on your server that users will return to. Once loaded, the data in the URL will need to be parsed. A exit URL result is shown below:

http://example.com/return.cgi?license_url=http://creativecommons.org/licenses/by-nc/2.0/&license_name=Attribution-NonCommercial&license_button=http://creativecommons.org/images/public/somerights20.gif&deed_url=http://creativecommons.org/licenses/by-nc/2.0/

Depending on your web application's server technology, you'll have to parse data from the URL as needed. From the above url, the following data points can be found:

<div class="code">
'''license_url:''' http://creativecommons.org/licenses/by-nc/2.0/

'''license_name:''' Attribution-NonCommercial

'''license_button:''' http://creativecommons.org/images/public/somerights20.gif

'''deed_url:''' http://creativecommons.org/licenses/by-nc/2.0/
</div>

If you had any additional embedded URL variables specific to your application, you will want to parse those out as well. The exact method and code used to read URL variables will depend on your website/application's language of choice and the syntax of that language.

This data can be used in several places within an application. A well-written application will display a user's choice by using the license_name variable as confirmation, such as "You selected the Attribution-Noncommercial license for your uploaded work." You will likely want to store the license_url and license_code variables within your application, most likely in database filed associated with contributions. Again, the exact method and code used to store license information will depend on your configuration, setup, and [http://www.rentittoday.com/storage-units-rentals storage options].

CcPublisher 2 Architecture

2012-02-10T06:10:56Z

Halobigred: /* p6.storage */

[[Category:CcPublisher]]
[[Category:Developer]]
{{needs updated}}
This document outlines the architecture developed for ccPublisher 2.x. At this point it is still considered a draft and subject to change. No applications based on the ccP 2.x codebase have been released. ccPublisher 2.0 will be the first application released using this code base, probably in February 2006.

== Design Goals ==

The following are goals we've attempted to meet while developing ccPublisher 2.x:
* Cleanly separate the User Interface from Internet Archive/uploading components
* Functional code separation
* Easy customization for partners
* Extensible for adding features
** without doing a complete customization
** to existing applications in a reasonable amount of time
* The ability to update a set of core functionality
* Allow for straight forward customization of the application. "Straight forward" means that elements of the user interface have a minimal number of interconnection points, and program logic is contained in a central location.

The following are considered non-goals:

* A general purpose application framework. Certain architectural details exist because ccPublisher and it's derivatives have common functionality: collecting information and uploading files. While individual pieces of code may be useful for other applications, the platform is designed to support this particular model.
* Addition of embedding support for more file types; this will be addressed in a release following 2.0.

== Object Model ==

=== Terminology ===

* A P6 application is designed to take a "Work" and send it somewhere
* A Work may contain one or more "items", such as files, CD tracks, etc
* A "[http://www.extraspace.com/Storage/Facilities/US/Ohio/Cincinnati/900352/Facility.aspx Storage] Provider" is responsible for taking the work and performing the action on it
* Metadata fields may be applied to any object:
** the work
** each item
** the storage provider (i.e., for username and password)

=== High Level Overview ===

The core of ccPublisher 2 is the P6 library, a set of common code intended to be used as a whole to perform core actions. P6 Applications consist of two phases: declaration and configuration. Declaration is the development of objects, event listeners and other code. Configuration consists of instantiating and connecting that code.

Configuration is handled through the use of ZCML, the Zope Configuration Markup Language. The ZCML directives configure adapters, event listeners and objects to instantiate. It also defines metadata fields to include in the uploaded package. Finally, the configuration can be arbitrarily extended using 3rd-party ZCML snippets to register new functionality. One example of this might be a blog pinging extension which posts a blog entry when new content is uploaded using a P6 Application. Note that depending on the registration mechanism used, it is possible to add content to all P6 Applications installed on a user's system.

In addition to ZCML, P6 uses the Interface and Component model from the Zope3 project. We maintain a snapshot in the CC Tools CVS Repository.

=== Additional Resources ===

* [http://yergler.net/talks/p82_architecture ccPublisher 2: Architecture & Design] <br/>Slides from a talk Nathan gave at CC San Francisco, June, 2005.
* [http://svn.zope.org/Zope3/trunk/src/zope/configuration/ ZCML in the Zope3 Repository]

== The P6 Package ==

The P6 package forms the core functionality of ccPublisher 2 and related applications. This section provides an overview of the sub-packages and modules developers should be aware of. For more detailed documentation of specific items, see the Epydoc documentation at http://mirrors.creativecommons.org/developer/doc/p6/current/. Note that some subpackages, such as p6.configure and p6.zcmlsupport, only provide internal support for bootstrapping applications.

===p6.api===

The p6.api module provides a sub-set of functionality from other p6 sub-packages. The api module is intended to provide a simple way to import commonly needed functionality.

===p6.app===

The p6.app package collects application-level functionality, including top-level window classes. This may be merged into p6.ui in a future release.

===p6.metadata===

A core piece of functionality for P6 applications is the collection of metadata. The p6.metadata package provides interfaces for encapsulates metadata fields and metadata groups. A metadata field is a single piece of information, such as artist or title. A metadata group provides a logical grouping for one or more fields. A metadata group may also be associated with a particular type of item or interface. The p6.ui package introspect this information for generating a user interface.

===p6.storage===

The p6.[http://www.rentittoday.com/rental-blog/2012/02/self-storage-cincinnati-oh/ storage] package encapsulates the interfaces used for Works, Items, and backend "storage" providers. The current implementation includes generic interfaces, interfaces for file-based items, and a generic No-Op storage provider. For an example of a custom storage provider, see the ArchiveStorage class in the ccPublisher distribution.

===p6.ui===

The p6.ui package provides three primary pieces of functionality: user interface generation for metadata groups and fields, stock wizard pages, and interfaces for custom wizard pages. It also includes a sample, custom page in the form of the license selector wizard page (license.py).

CcPublisher 2 Architecture

2012-02-10T06:08:50Z

Halobigred: /* Terminology */

[[Category:CcPublisher]]
[[Category:Developer]]
{{needs updated}}
This document outlines the architecture developed for ccPublisher 2.x. At this point it is still considered a draft and subject to change. No applications based on the ccP 2.x codebase have been released. ccPublisher 2.0 will be the first application released using this code base, probably in February 2006.

== Design Goals ==

The following are goals we've attempted to meet while developing ccPublisher 2.x:
* Cleanly separate the User Interface from Internet Archive/uploading components
* Functional code separation
* Easy customization for partners
* Extensible for adding features
** without doing a complete customization
** to existing applications in a reasonable amount of time
* The ability to update a set of core functionality
* Allow for straight forward customization of the application. "Straight forward" means that elements of the user interface have a minimal number of interconnection points, and program logic is contained in a central location.

The following are considered non-goals:

* A general purpose application framework. Certain architectural details exist because ccPublisher and it's derivatives have common functionality: collecting information and uploading files. While individual pieces of code may be useful for other applications, the platform is designed to support this particular model.
* Addition of embedding support for more file types; this will be addressed in a release following 2.0.

== Object Model ==

=== Terminology ===

* A P6 application is designed to take a "Work" and send it somewhere
* A Work may contain one or more "items", such as files, CD tracks, etc
* A "[http://www.extraspace.com/Storage/Facilities/US/Ohio/Cincinnati/900352/Facility.aspx Storage] Provider" is responsible for taking the work and performing the action on it
* Metadata fields may be applied to any object:
** the work
** each item
** the storage provider (i.e., for username and password)

=== High Level Overview ===

The core of ccPublisher 2 is the P6 library, a set of common code intended to be used as a whole to perform core actions. P6 Applications consist of two phases: declaration and configuration. Declaration is the development of objects, event listeners and other code. Configuration consists of instantiating and connecting that code.

Configuration is handled through the use of ZCML, the Zope Configuration Markup Language. The ZCML directives configure adapters, event listeners and objects to instantiate. It also defines metadata fields to include in the uploaded package. Finally, the configuration can be arbitrarily extended using 3rd-party ZCML snippets to register new functionality. One example of this might be a blog pinging extension which posts a blog entry when new content is uploaded using a P6 Application. Note that depending on the registration mechanism used, it is possible to add content to all P6 Applications installed on a user's system.

In addition to ZCML, P6 uses the Interface and Component model from the Zope3 project. We maintain a snapshot in the CC Tools CVS Repository.

=== Additional Resources ===

* [http://yergler.net/talks/p82_architecture ccPublisher 2: Architecture & Design] <br/>Slides from a talk Nathan gave at CC San Francisco, June, 2005.
* [http://svn.zope.org/Zope3/trunk/src/zope/configuration/ ZCML in the Zope3 Repository]

== The P6 Package ==

The P6 package forms the core functionality of ccPublisher 2 and related applications. This section provides an overview of the sub-packages and modules developers should be aware of. For more detailed documentation of specific items, see the Epydoc documentation at http://mirrors.creativecommons.org/developer/doc/p6/current/. Note that some subpackages, such as p6.configure and p6.zcmlsupport, only provide internal support for bootstrapping applications.

===p6.api===

The p6.api module provides a sub-set of functionality from other p6 sub-packages. The api module is intended to provide a simple way to import commonly needed functionality.

===p6.app===

The p6.app package collects application-level functionality, including top-level window classes. This may be merged into p6.ui in a future release.

===p6.metadata===

A core piece of functionality for P6 applications is the collection of metadata. The p6.metadata package provides interfaces for encapsulates metadata fields and metadata groups. A metadata field is a single piece of information, such as artist or title. A metadata group provides a logical grouping for one or more fields. A metadata group may also be associated with a particular type of item or interface. The p6.ui package introspect this information for generating a user interface.

===p6.storage===

The p6.storage package encapsulates the interfaces used for Works, Items, and backend "storage" providers. The current implementation includes generic interfaces, interfaces for file-based items, and a generic No-Op storage provider. For an example of a custom storage provider, see the ArchiveStorage class in the ccPublisher distribution.

===p6.ui===

The p6.ui package provides three primary pieces of functionality: user interface generation for metadata groups and fields, stock wizard pages, and interfaces for custom wizard pages. It also includes a sample, custom page in the form of the license selector wizard page (license.py).

Case Studies/FREE - THE JOURNEY

2012-02-10T05:56:51Z

Halobigred: /* Overview */

{{Case Study
|Description=FREE- THE JOURNEY is an experimental 15 song audio video compilation. The music was recorded impromptu during a vacation jam in 2009. In 2010, Bonfire Collective, now working on its debut studio album decided to release the music as a prelude to the first single launch. But we wanted to do something different.
|Mainurl=http://www.facebook.com/event.php?eid=101072603292010
|Author=Bonfire Collective / Creative Collective TV
|User_Status=Creator
|Tag=Live music, experimental, psychedelic, experimental video production
|License short name=CC BY-NC-SA
|CC adoption date=2010
|Format=Sound, MovingImage, Other
|Country=India, Global
}}
== Overview ==

The project was basically run by a core group of 3 people with a like minded vision of creating something out of the box. Keeping in mind the old adage "If you want something done right, do it yourself" a group us of decided to see this thing through by efficiently multitasking. Owing to our varied backgrounds as both musicians and creative professionals, we were able to strike a balance between delivery and deadlines. Many may wonder why deadlines for a creative non profit collaboration? Apart from the obvious effective usage of time and resources, we felt that unless you put a date to something, it very rarely comes out. This may involve some time sacrifice, but we found that the production was more cohesive since people were focused on an end product rather than on ideals. The deadline gave little room to go off on tangents. This however in no way impeded our creative abilities. If anything, we think that it juiced us up and made us think about solutions rather than problems.

The music itself was a breeze. The Plan - "Lets [http://www.rentittoday.com rent] a studio and jam!" The recording room itself was only about 12 feet by 12 feet. Arjun, Aum, Rakesh and Boskey squeezed into the tiny space. I was in the mixing booth and Praveen in the vocal booth. The studio had a terrace with an amazing view of the backwaters and the city.

To be honest I don't think, any of us really had an idea of what we wanted to do or how we were going to accomplish a half way decent recording when we didn't even have material. Day One ended with us doing about 5 hours of recording. Day two started early and was much more productive than Day One. I think that the band was much more focused. We recorded for 4 straight hours with small breaks.

Back in Chennai, India, we started the review of the material. No one had really heard anything till then.It was just suppose to be a fun thing with no serious expectations. So what did we have? 3 hours of coherent to vaguely coherent music. We didn't have a sound engineer at the time and didn't want to spend money on an experiment that was done more for fun than work or profit. We decided to edit the music ourselves. Now its important to remember that there wasn't really much we could do. The drums were already mixed and the guitar/bass/key tones were already in place. The most we could do was some leveling and a bit of mastering. To make things interesting we added a couple of voice samples.We proceeded to cut them up into songs in our free time and completed the audio in 2 months. We had 1 hour of music - about 17 songs. The music however, sat on our hard drives for over a year and was previously never released.

A friend of ours had referred me to Creative Commons, an online community that shares creative work - media that can be reused (depending on the licenses). So we got online and based on the themes of the songs, we downloaded video content from blip.tv that could be adapted. To our surprise,many of the videos looked like they had been shot / designed just for the music. In some cases we followed through on the concepts with multiple videos edited together around a central theme. Videos were edited to fit the music on Sony Vegas Pro. Now we've been Final Cut Pro users for the last 4 years, but when I used Vegas 9 I was astounded by its ease of use, flexibility and render speeds. I think that its by far the best editing software for quick turn around projects. We did our post production with After effects to give the product an original unifying look and re-optimized the videos to strike a good stream / quality balance.

I would like to mention here that optimization was quite a task. First of all movies from blip.tv are normally in flv format. We suggest converting them to MPEG2 for editing and upload. We scaled up the footage first to 720x480 using OJOsoft total video converter, but you can use any good converter. The results were encouraging. Very little pixelation or drop frames.

The result of this effort is FREE - THE JOURNEY, a 15 song - 53 minute audio video compilation. We have released it on Facebook, Blip.tv and YouTube. This is the first time a Creative Commons project of this scale has been done from India and probably (we think) one of the bigger ones worldwide. In the process we have also launched our own YouTube channel - Creative Collective TV

'''Music by LBG-Bonfire Collective Collaboration'''
Arjun Janakiram: Bass, Aum Janakiram: Guitars, Avneet Janakiram: Guitars, Boskey: Keyboards, Praveen Heinrich: Flute, Harmonica, Percussion, Rakesh Khanna: Drums

Recorded at Studio, Ernakulam, Kerala, India

'''Mixed at The Lab – Audio Production Unit, Chennai, India'''

Mastered by Udaya Kiran, The Lab

'''Video Post Production: Apptitude'''

'''Produced by CC TV (Creative Collective TV) – A MMU Communications Initiative'''

Executive Producers: Avneet Janakiram, Arjun Janakiram, Aum Janakiram

'''Video Credits'''

Pondicherry -A Stop Motion Project by Shaun Dsa
Source: Individual, The Ancestors Tale by Ian Elsner,
Ritournelle by Lachamplure,
3.2.2.4 by MoleCabal,
Clockfish by ExploderFace,
Pagen envy by Qutub, Abstract by Mengtime, The Red Dancer by Patsylai,
Faces5, Faces9, Faces6 by Hmotro,
peteherroncomArchivedVideos by Peteherron,
MorningStorm by Apperceptions,
TimeLapse by JumperTV,
TimeLapseTest by Squampton,
WhatKindOfShape by Gosmedia,
ParticlesSampleVideo by Lostmarbledvtemp,
Y by Speculativism,
ScaryPumpkin by VideoJester,
Grendel by Pacfolly,
FaceIt by Marquisdejolie,
SpiderWeb by ErinNealey,
ScaryHole by AngryBeth,
LaSpirale by Dziit,
GrooveUrbano by Fabioramosnascimento,
EPPElectroPlasmaPulse by MindsiMedia,
Water by DotAtelier,
Animation by HassenMalek,
LINES by Mxpccw,
Source Blip.tv

== License Usage ==

Most of the footage used have a CC by NC-SA license. Others had a commercial license So we decided to also release FREE under CC by NC-SA. The music is available on Jamendo under the same license.

== Motivations ==

The reasons for doing this are manifold. First this is a creative body of work founded on the core principle of doing "art for art" and not for money. As a creative outfit we wanted to flex our muscles and push the envelope without any restrictions.That means no whiny clients complaining about what they thought they were getting.We were our own clients - we knew what we wanted and how we were going to get it.

Secondly, the collaboration with talented artists and film makers from round the world made the project all that more interesting. As creative professionals, there is always this ever growing desire to work on material with new people. However, time and money constraints prevent most of us from entering into collaborations that can turn out work in a reasonable span of time. Creative Commons gave us that opportunity.

Fun Factoids about FREE

1. The recording was done in 12 hours over 2 days. We left Kerala with 3 hours of audio which was further vetted down to 1 hour 10 minutes.

2. The Music took us 2 months to sort through and edit due to time constraints. The videos took us 2 weeks.

3. All the songs have retained their original names

4. No overlays, no retakes, just some voice samples

5. Its the first ( to the best of our knowledge) Creative Commons project of this scale done from India

== Media ==
'''Facebook event :''' http://www.facebook.com/event.php?eid=101072603292010 (Oct 7th -Dec 31st 2010)

'''Youtube Channel :''' http://www.youtube.com/user/creativecollectivetv

'''Music Downloads''': http://www.jamendo.com/en/album/76667

Case Studies/FREE - THE JOURNEY

2012-02-10T05:51:29Z

Halobigred: /* Overview */

{{Case Study
|Description=FREE- THE JOURNEY is an experimental 15 song audio video compilation. The music was recorded impromptu during a vacation jam in 2009. In 2010, Bonfire Collective, now working on its debut studio album decided to release the music as a prelude to the first single launch. But we wanted to do something different.
|Mainurl=http://www.facebook.com/event.php?eid=101072603292010
|Author=Bonfire Collective / Creative Collective TV
|User_Status=Creator
|Tag=Live music, experimental, psychedelic, experimental video production
|License short name=CC BY-NC-SA
|CC adoption date=2010
|Format=Sound, MovingImage, Other
|Country=India, Global
}}
== Overview ==

The project was basically run by a core group of 3 people with a like minded vision of creating something out of the box. Keeping in mind the old adage "If you want something done right, do it yourself" a group us of decided to see this thing through by efficiently multi-tasking. Owing to our varied backgrounds as both musicians and creative professionals, we were able to strike a balance between delivery and deadlines. Many may wonder why deadlines for a creative non profit collaboration? Apart from the obvious effective usage of time and resources, we felt that unless you put a date to something, it very rarely comes out. This may involve some time sacrifice, but we found that the production was more cohesive since people were focused on an end product rather than on ideals. The deadline gave little room to go off on tangents. This however in no way impeded our creative abilities. If anything, we think that it juiced us up and made us think about solutions rather than problems.

The music itself was a breeze. The Plan - "Lets [http://www.rentittoday.com rent] a studio and jam!" The recording room itself was only about 12 feet by 12 feet. Arjun, Aum, Rakesh and Boskey squeezed into the tiny space. I was in the mixing booth and Praveen in the vocal booth. The studio had a terrace with an amazing view of the backwaters and the city.

To be honest I don't think, any of us really had an idea of what we wanted to do or how we were going to accomplish a half way decent recording when we didn't even have material. Day One ended with us doing about 5 hours of recording. Day two started early and was much more productive than Day One. I think that the band was much more focused. We recorded for 4 straight hours with small breaks.

Back in Chennai,India, we started the review of the material. No one had really heard anything till then.It was just suppose to be a fun thing with no serious expectations. So what did we have? 3 hours of coherent to vaguely coherent music. We didn't have a sound engineer at the time and didn't want to spend money on an experiment that was done more for fun than work or profit. We decided to edit the music ourselves. Now its important to remember that there wasn't really much we could do. The drums were already mixed and the guitar/bass/key tones were already in place. The most we could do was some leveling and a bit of mastering. To make things interesting we added a couple of voice samples.We proceeded to cut them up into songs in our free time and completed the audio in 2 months. We had 1 hour of music - about 17 songs. The music however, sat on our hard drives for over a year and was previously never released.

A friend of ours had referred me to Creative Commons, an online community that shares creative work - media that can be reused (depending on the licenses). So we got online and based on the themes of the songs, we downloaded video content from blip.tv that could be adapted. To our surprise,many of the videos looked like they had been shot / designed just for the music. In some cases we followed through on the concepts with multiple videos edited together around a central theme. Videos were edited to fit the music on Sony Vegas Pro. Now we've been Final Cut Pro users for the last 4 years, but when I used Vegas 9 I was astounded by its ease of use, flexibility and render speeds. I think that its by far the best editing software for quick turn around projects. We did our post production with After effects to give the product an original unifying look and reoptimized the videos to strike a good stream / quality balance.

I would like to mention here that optimization was quite a task. First of all movies from blip.tv are normally in flv format. We suggest converting them to MPEG2 for editing and upload. We scaled up the footage first to 720x480 using OJOsoft total video converter, but you can use any good converter. The results were encouraging. Very little pixelation or drop frames.

The result of this effort is FREE - THE JOURNEY, a 15 song - 53 minute audio video compilation. We have released it on Facebook, Blip.tv and Youtube. This is the first time a Creative Commons project of this scale has been done from India and probably (we think) one of the bigger ones worldwide. In the process we have also launched our own youtube channel - Creative Collective TV

'''Music by LBG-Bonfire Collective Collaboration'''
Arjun Janakiram: Bass, Aum Janakiram: Guitars, Avneet Janakiram: Guitars, Boskey: Keyboards, Praveen Heinrich: Flute, Harmonica, Percussion, Rakesh Khanna: Drums

Recorded at Studio, Ernakulam, Kerala, India

'''Mixed at The Lab – Audio Production Unit, Chennai, India'''

Mastered by Udaya Kiran, The Lab

'''Video Post Production: Apptitude'''

'''Produced by CC TV (Creative Collective TV) – A MMU Communications Initiative'''

Executive Producers: Avneet Janakiram, Arjun Janakiram, Aum Janakiram

'''Video Credits'''

Pondicherry -A Stop Motion Project by Shaun Dsa
Source: Individual, The Ancestors Tale by Ian Elsner,
Ritournelle by Lachamplure,
3.2.2.4 by MoleCabal,
Clockfish by ExploderFace,
Pagen envy by Qutub, Abstract by Mengtime, The Red Dancer by Patsylai,
Faces5, Faces9, Faces6 by Hmotro,
peteherroncomArchivedVideos by Peteherron,
MorningStorm by Apperceptions,
TimeLapse by JumperTV,
TimeLapseTest by Squampton,
WhatKindOfShape by Gosmedia,
ParticlesSampleVideo by Lostmarbledvtemp,
Y by Speculativism,
ScaryPumpkin by VideoJester,
Grendel by Pacfolly,
FaceIt by Marquisdejolie,
SpiderWeb by ErinNealey,
ScaryHole by AngryBeth,
LaSpirale by Dziit,
GrooveUrbano by Fabioramosnascimento,
EPPElectroPlasmaPulse by MindsiMedia,
Water by DotAtelier,
Animation by HassenMalek,
LINES by Mxpccw,
Source Blip.tv

== License Usage ==

Most of the footage used have a CC by NC-SA license. Others had a commercial license So we decided to also release FREE under CC by NC-SA. The music is available on Jamendo under the same license.

== Motivations ==

The reasons for doing this are manifold. First this is a creative body of work founded on the core principle of doing "art for art" and not for money. As a creative outfit we wanted to flex our muscles and push the envelope without any restrictions.That means no whiny clients complaining about what they thought they were getting.We were our own clients - we knew what we wanted and how we were going to get it.

Secondly, the collaboration with talented artists and film makers from round the world made the project all that more interesting. As creative professionals, there is always this ever growing desire to work on material with new people. However, time and money constraints prevent most of us from entering into collaborations that can turn out work in a reasonable span of time. Creative Commons gave us that opportunity.

Fun Factoids about FREE

1. The recording was done in 12 hours over 2 days. We left Kerala with 3 hours of audio which was further vetted down to 1 hour 10 minutes.

2. The Music took us 2 months to sort through and edit due to time constraints. The videos took us 2 weeks.

3. All the songs have retained their original names

4. No overlays, no retakes, just some voice samples

5. Its the first ( to the best of our knowledge) Creative Commons project of this scale done from India

== Media ==
'''Facebook event :''' http://www.facebook.com/event.php?eid=101072603292010 (Oct 7th -Dec 31st 2010)

'''Youtube Channel :''' http://www.youtube.com/user/creativecollectivetv

'''Music Downloads''': http://www.jamendo.com/en/album/76667