https://wiki.creativecommons.org/api.php?action=feedcontributions&user=Matt898&feedformat=atomCreative Commons - User contributions [en]2024-03-28T10:18:22ZUser contributionsMediaWiki 1.30.0https://wiki.creativecommons.org/index.php?title=CcPublisher_2_Architecture&diff=57882CcPublisher 2 Architecture2012-06-29T02:25:31Z<p>Matt898: </p>
<hr />
<div>[[Category:CcPublisher]]<br />
[[Category:Developer]]<br />
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.<br />
<br />
== Design Goals ==<br />
<br />
The following are goals we've attempted to meet while developing ccPublisher 2.x:<br />
* Cleanly separate the User Interface from Internet Archive/uploading components<br />
* Functional code separation<br />
* Easy customization for partners<br />
* Extensible for adding features<br />
** without doing a complete customization<br />
** to existing applications in a reasonable amount of time<br />
* The ability to update a set of core functionality<br />
* 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.<br />
<br />
The following are considered non-goals:<br />
<br />
* 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.<br />
* Addition of embedding support for more file types; this will be addressed in a release following 2.0.<br />
<br />
== Object Model ==<br />
<br />
=== Terminology ===<br />
<br />
* A P6 application is designed to take a "Work" and send it somewhere<br />
* A Work may contain one or more "items", such as files, CD tracks, etc<br />
* A "[http://www.rentittoday.com/rental-stores/Extra-Space-Storage-Cincinnati-OH-Self-Storage-1756 Storage] Provider" is responsible for taking the work and performing the action on it<br />
* Metadata fields may be applied to any object:<br />
** the work<br />
** each item<br />
** the storage provider (i.e., for username and password)<br />
<br />
=== High Level Overview ===<br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Additional Resources ===<br />
<br />
* [http://yergler.net/talks/p82_architecture ccPublisher 2: Architecture & Design] <br/>Slides from a talk Nathan gave at CC San Francisco, June, 2005.<br />
* [http://svn.zope.org/Zope3/trunk/src/zope/configuration/ ZCML in the Zope3 Repository]<br />
<br />
== The P6 Package ==<br />
<br />
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.<br />
<br />
===p6.api===<br />
<br />
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. <br />
<br />
===p6.app===<br />
<br />
The p6.app package collects application-level functionality, including top-level window classes. This may be merged into p6.ui in a future release.<br />
<br />
===p6.metadata===<br />
<br />
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.<br />
<br />
===p6.storage===<br />
<br />
The p6.[http://www.rentittoday.com/rental-blog/3703/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.<br />
<br />
===p6.ui===<br />
<br />
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).</div>Matt898https://wiki.creativecommons.org/index.php?title=CcPublisher_2_Beta_3&diff=55249CcPublisher 2 Beta 32012-02-13T06:54:47Z<p>Matt898: </p>
<hr />
<div>=== ccPublisher 2 Beta 3 ===<br />
<br />
Thursday, May 12, 2006<br />
<br />
==== Release Notes ====<br />
<br />
This release of ccPublisher 2 corrects many bugs exposed during the previous Beta 2 period. In particular, error handling and input validation have been significantly improved. Some problems with uploading to the Internet Archive were due to inpropoer error checking; these issues have been corrected.<br />
<br />
In addition to error fixes, this release includes the new Extension Point API which allows extensions and [http://www.rentittoday.com/storage-units-rentals storage providers] to contribute to the primary user interface. It also includes initial support for multiple backends; the final 2.0 release will contain the two providers analogous to ccPublisher 1's functionality: Internet Archive and Self-Hosting.<br />
<br />
This release includes "phone home" code to open an issue in the ccPublisher Tracker when a crash occurs. This new tracker is located at http://roundup.creativecommons.org/ccpublisher; all feature requests and bugs are tracked there. When a crash occurs, you are no longer prompted for your email address -- if you authorize ccPublisher to upload the crash information, you are provided with a link to the web page so you can follow progress. You can add yourself as a "nosy" account (and receive email when updated) or subscribe to the RSS feed of activity.<br />
<br />
If you have suggestions, feature requests, or bug reports, you can file them in the tracker as well (http://roundup.creativecommons.org/ccpublisher).<br />
<br />
If you wish to discuss development of ccPublisher, you can subscribe to the [http://lists.ibiblio.org/mailman/listinfo/cc-devel cc-devel mailing list].<br />
<br />
==== Downloads ====<br />
<br />
* Linux (tar.gz): http://download.berlios.de/cctools/ccPublisher-1.9.3.tar.gz<br />
* Windows XP: http://download.berlios.de/cctools/ccPublisher-1.9.3.exe<br />
* Mac OS X: http://download.berlios.de/cctools/ccPublisher-1.9.3.zip<br />
<br />
==== Installation ====<br />
<br />
* '''Windows:''' The download link above points to <code>ccPublisher-1.9.3.exe</code>; run that file and ccPublisher will be installed and added to your Start menu.<br />
* '''Linux:''' The download link above points to a source tarball, which includes most of what you need. You will also need [http://wxpython.org/download.php wxPython 2.6 (Unicode build)] and [http://effbot.org/downloads/#elementtree elementtree]. Once you have those two dependencies installed, untar the download and run <code>ccpublisher.py</code>.<br />
* '''Mac OS X:''' The download link points to a zip file which contains the application file. Unzip the archive to run ccPublisher.<br />
<br />
[[Category:CcPublisher]]</div>Matt898https://wiki.creativecommons.org/index.php?title=CCBus&diff=55248CCBus2012-02-13T06:47:25Z<p>Matt898: </p>
<hr />
<div>'''This is a draft project proposal and is not (yet) officially endorsed nor organized by Creative Commons. It is an initiative by CC Guatemala and other community members.'''<br />
<br />
[[File:CCBuslogo.png]]<br />
<br />
CC Guatemala, led by Renata Avila, together with community members Teresa Sempere García and Michelle Thorne, would like to organize a CC Bus tour through Central America. [http://www.rentittoday.com The plan is to rent one] of the region’s ubiquitous mini vans, pack it full with CC enthusiasts and open web folks, and traverse the region for two weeks, holding workshops, salons, parties, and whatever event format necessary to connect the lively Free Culture scene in Central America. On the itinerary are Guatemala, Nicaragua, Costa Rica, Honduras, and El Salvador. You can see [http://maps.google.com/maps/ms?ie=UTF8&hl=es&msa=0&ll=11.393879,-92.592773&spn=19.168592,26.762695&z=5&msid=103378094407398207803.00047ca89d10743d4438c our route on Google Maps] and a [http://www.slideshare.net/RenataAvila/cc-bus slideshow with further information].<br />
<br />
== Itinerary == <br />
Add your ideas and suggestions! <br />
===Guatemala=== <br />
* Antigua Guatemala - CENTRO DE FORMACIÓN DE LA COOPERACIÓN ESPAÑOLA Antiguo Convento de la Compañía de Jesús. 6ª Avda. Norte. entre 3ª y 4ª calle LA ANTIGUA - GUATEMALA <br />
* Xela - http://www.casanoj.com/principal.html<br />
===Nicaragua===<br />
* Managua - OFICINA TÉCNICA DE COOPERACIÓN Plaza Bolonia, 2 1/2 Cuadra Abajo, Frente a a la Embajada de Dinamarca MANAGUA - NICARAGUA <br />
===Costa Rica===<br />
* University of Costa Rica - http://www.ucr.ac.cr/<br />
<br />
===Honduras===<br />
* Tegucigalpa - http://www.ccet-aecid.hn/<br />
* A Cayos Cochinos! - http://www.cayoscochinos.org/<br />
<br />
===El Salvador===<br />
* San Salvador - http://www.ccespanasv.com/<br />
<br />
==Supporters==<br />
Add your ideas for local partners, volunteers, venues, and sponsors. We're looking for Free Culture advocates, commoners, artists, Wikipedians, Free Software developers, librarians, teachers, open web enthusiasts, anyone really who would like to get involved.</div>Matt898https://wiki.creativecommons.org/index.php?title=North_Dakota_State_University&diff=55157North Dakota State University2012-02-06T23:41:52Z<p>Matt898: </p>
<hr />
<div>{{UCOP<br />
|University=North Dakota State University<br />
|University Type=Public<br />
|Mainurl=http://www.ndsu.nodak.edu/<br />
|Policy URL=http://www.ndsu.edu/policy/190.htm<br />
|Policy Date=2008/05/06<br />
|Policy Clarity=Somewhat clear<br />
|Creative works ownership status=Author<br />
|Creative works ownership status exceptions=Yes<br />
|Creative works ownership status exceptions types=Sponsored work, Work for hire<br />
|Creative definitions=Significant Use of University System. Significant Use of Institution Resources means an Author's use of other employees' time or Institution facilities or equipment that appreciably increases the Institution's costs beyond those normally incurred in support of an employee in the Institution. Significant Use does not include the normal use of Institution employees, facilities, or equipment commonly available to faculty, staff, or the public, such as libraries, Internet access, office and [http://www.rentittoday.com/storage-units-rentals storage space], office equipment, computers, and/or office supplies. Unless otherwise agreed, Significant Use also does not include the use of Institutional developmental leave time, so long as it does not appreciably increase the Institution's costs beyond those normally incurred in support of an employee of the Institution.<br />
"If there has been Significant Use of Institutional Resources to create a Copyrightable Work, the ownership of which is vested in the individual employee . . . . The Institution shall be reimbursed for the Significant Use of any facilities, personnel or resources, except those considered part of the normal academic environment including library facilities."<br />
<br />
Work [http://www.rentittoday.com For Rent] or Hire. Defined pursuant to Federal Copyright Law which includes a Work prepared by an employee within the scope of employment or a Work created pursuant to a written agreement identifying the Work as a Work for Hire.<br />
|Courseware ownership status=Author<br />
|Courseware ownership status exceptions=Yes<br />
|Courseware ownership status exceptions types=Sponsored work, Work for hire<br />
|Courseware definitions=Mediated Courseware.<br />
* a. Self-initiated Mediated Courseware. When employees develop Mediated Courseware without specific direction by the Institution, unless otherwise agreed, the ownership of the courseware shall remain with the employee. Normally, no royalty, rent or other consideration shall be paid to the employee when that Mediated Courseware is used for instruction at the Institution and such Mediated Courseware shall not be used or modified without the consent of the employee. While the Creator is under Institutional employment, the Mediated Courseware shall not be sold, leased, rented or otherwise used in a manner that competes in a substantial way with the for-credit offering of the employee's own Institution unless that transaction has received the approval of the chief academic officer of the Institution. The Institution shall have a perpetual, non-exclusive royalty-free right to use such courseware for archival research purposes. Should approval be granted to offer the course outside of the Institution, the provisions of section 4b of this policy shall apply.<br />
* b. Institution-directed Mediated Courseware. When the Institution directs in an employment contract the creation of a specific Mediated Courseware, the resulting Mediated Courseware belongs to the Institution and the Institution shall have the right to revise it and decide who will utilize the Mediated Courseware in instruction. The Institution may specifically agree to share revenues, pursuant to the General Patent Policy with the employee(s) receiving a minimum of 30 percent of the net royalties and fees, and control rights with the employee.<br />
|Materials ownership status=Author<br />
|Materials ownership status exceptions=Not Specified<br />
|Materials ownership status exceptions types=Sponsored work, Substantial use of University resources, Work for hire<br />
|Student Ownership Status=Author<br />
|Student Ownership Status Exceptions=Yes<br />
|Student Ownership Status Exception Types=Work for hire, Substantial use of University resources<br />
|Open Access Policy=Unknown<br />
|OA Policy URL=http://<br />
}}<br />
Policy is relatively clear w/r/t/ professor's works. However, it doesn't distinguish between traditional works and other works.<br />
W/r/t courseware, policy gives author ownership over individual mediated courseware, but places limitations on owner's use. Also not clear if substantial use of university resources exception applies to courseware.</div>Matt898https://wiki.creativecommons.org/index.php?title=Construction_Equipment&diff=55116Construction Equipment2012-02-03T04:03:08Z<p>Matt898: </p>
<hr />
<div>{{ContentDirectory<br />
|mainurl=http://www.constructiontoday.org<br />
|ccportal=http://www.constructiontoday.org<br />
|format=Text, InteractiveResource, Other<br />
|size=251<br />
}}<br />
Find building and construction trade shows, exhibitions, fairs and conferences worldwide and search our database of building, construction companies, and [http://www.rentittoday.com/construction-equipment-rentals construction equipment rental], with everything licensed under CC Attribution-Noncommercial-Share Alike 3.0 Unported.</div>Matt898https://wiki.creativecommons.org/index.php?title=Grants/CC_Full-dome&diff=55115Grants/CC Full-dome2012-02-03T03:53:03Z<p>Matt898: </p>
<hr />
<div>{{Grant Application<br />
|Project Title=CC Full-dome<br />
|applicants=Artists' House in Weimar<br />
|contact person=Daniel Caleb Thompson<br />
|coordinator=Daniel Caleb Thompson (Project Manager), Prof. Ben Sassen (University Liason & Media Artist), Hannes Wagner (Full-Dome guru), Thomas Wohlfarth (IT), Jan Zehn (Audio)<br />
|start date=2010/08/01<br />
|end date=2010/10/09<br />
|Affiliation=Facepalm Productions, KulturTragWerk e.V., Bauhaus-University Weimar Media Faculty & Computing Service, Machine Room of the Student Government, MX-Wendler, Cultural Office of the City of Weimar<br />
|Mainurl=http://kuenstlerhaus-weimar.de<br />
|Affiliated=No<br />
|description=We want to build a platform for full-dome film projection and production, making it possible for artists, film-makers and students to freely access a dome and create content for this medium that is currently in its infancy. This project will serve to acquire the technology and materials to build the dome, port VJ software (MX-Wendler) to the Linux platform, create the technical infrastructure and make the handbook so that others can also fashion their own domes for similar projects. We see this work as the beginning of a long-term project that will create an infrastructure that, in the words of Prof. Ben Sassen, will "be made freely available for local Creative Commons licensed projects" and make "media available to a broad cross-section of society ranging from school-age to retirement-age".<br />
|output=# free & public access to a dome projection system for CC projects<br />
# CC-licensed project blueprints using consumer grade technology, minimal proficiency in construction <br />
# take the first step down the road of the creation of a render-farm available to the community for the post-production and test-rendering of full-dome projects<br />
# the porting of professional VJ software from Windows & Mac to Linux platform, made freely available to the Linux community, albeit under a closed-source license.<br />
|community=The community is composed of artists, film-makers and students currently developing films and visualizations for full-dome projection systems, some of whom live and work in the area, others would travel to use the dome. The full-dome is actually a "bastard-child" of planetarium projection-systems. Arising from this cross-over situation, the technology, [http://www.rentittoday.com/storage-units-rentals storage rental space] and relative lack of planetariums make it a very cost-prohibitive venture in film-making. In Weimar, where we will build the first CC Dome, there isn't even a dome to be used - even though the local community of film-makers and university students are very productive making their films, they don't even have a place to run test-renderings or even showcase their works to others.<br />
Our work will concretely reduce travel costs and time loss while increasing productivity and availability of this exciting and immersive medium. On an extended level, we will also provide the plans for making such a dome, thus expanding and empowering our community.<br />
|community relationship=In itself, the Artists' House was an organization active in the Weimar arts industry from 1887 until 1945, and is currently enjoying its revival as a community-based non-commercial meeting point for artists of all genres and those interested in supporting the arts. It is a hub of the community, located in the center of the city. We are currently planning our monthly CC Salon, to begin in July.<br />
Its director, Daniel Caleb Thompson, has been at the forefront of the local avant garde arts and media scene for the past 10 years. For his final thesis project at Bauhaus-University Weimar in 2004 he made 5 home-brew video projectors and a live holographic presentation system. Furthermore he also helped found the Galerie Eigenheim in Weimar, was its Director from 2008 - 2009 and has spent the past several years acquiring and managing funding for a variety of small to large projects, most recently for the City of Weimar as projects curator for the "Bauhaus Lab" that was funded by EU Culture.<br />
One of our key partners is a young full-dome film company, which will be premiering its CC licensed film "SUPER GOLDEN YEARS" in our full-dome on the 9th of October.<br />
Our partnership with Bauhaus-University includes the Professor for Experimental Television as well as the lecturer responsible for the Full-dome department at the Media faculty. Additionally, the university center for computing will be providing networking facilities and an array of licenses.<br />
The Machine Room is a small community of hackers, DIYers and Linux enthusiasts always ready to get involved in new and exciting projects with media.<br />
MX-Wendler is professional VJ server software, however it is currently only available on Macintosh and Windows platforms. We are working closely with its lead developer to resolve porting issues, and hope to release a closed-source but freely available (for non-profit organizations) full-dome alpha version for Linux in early September.<br />
Last but not least, our cooperation with the City of Weimar's Cultural Office guarantees the acceptance and promotion of our cultural work from a legal and sociology-political standpoint in Weimar and the State of Thuringia.<br />
|measurement=The immediate impact of this project will be measured by the number of people retained by the Artists' House as volunteers after this first phase is completed. Naturally, it can also be measured by the quantity (and technical quality) of full-dome media-projects produced in Weimar over the course of the next few years. In the short term we hope to see a increasing interest in full-dome at the art/ movie-maker scene of Weimar, over the long term in whole thuringia and bordering states of Germany, because Weimar is a really central place. Because of the relatively small size of the current full-dome scene, we also expect to be a driving partner in international collaborations on the EU and international level, to the extent where we can eventually help offset the funding costs associated with the production of such films with the support of EU Media and EU Culture programs. Of course it will also be interesting to see to what extent our work enables others to undertake similar projects, and participate in the cross-pollination that arises out of sharing ideas and resources.<br />
|participants=During the first phase of the project, we expect around thirty to forty people to help create the physical dome and its technical infrastructure. The vast majority of these people have a vested interest in the project and collaborate with the Artists' House on a volunteer basis, although several specialists will be paid for their work. After the Dome is finished, it is guaranteed that the community will grow faster every month due to artist/ filmmakers/ full-dome fanatics and students who will have the possibility to create their own content for the Dome, who will naturally spread the word to other interested people -- especially via our proximity and cooperation with Bauhaus-University Weimar and the Full-Dome-festival in Jena. (See other notes.)<br />
|impact=Full-dome is still a quite exclusive and closed medium due to many factors:<br />
<br />
The makers need:<br />
1) Knowledge of and money for the tools to create, render and present the films,<br />
2) The connections to a full-dome for testing and presenting,<br />
3) To efficiently manage the gigantic data flow which is needed for creating content for the Dome.<br />
<br />
For the audience:<br />
1) Absurdly high licensing fees for "professional" full-dome films make their presentation an incredible expense for planetariums and quickly over-saturate the market with films of a primarily scientific nature.<br />
2) Weimar (and a majority of other mid-size cites across the planet) do not have such facilities, forcing the audience to travel<br />
<br />
The CC-dome in Weimar will give everyone who is interested in sharing creative output the possibility to use a professional render-farm, to have non-bureaucratic access to a Dome for testing and presenting their work and it will finally take the Dome out of the planetarium and open it for everyone who is searching for new media formats in a friendly, open and sharing context. Furthermore, the knowledge we will have gained in the process will be returned to the community to be reworked, improved and shared.<br />
|tech needs=We will be building the dome with aluminum and PVC sheeting. We will use 8 small speakers in order to create surround sound. Video projection will be controlled by a 64bit computer built for is role as "video projection & audio services manager" and useful in the future during non-presentation times as queue-manager for the render farm / Beowulf server. We are audio-video professionals with a variety of backgrounds ranging from coding to fine art, who have come together to find an elegant solution to a rather simple (but to date more or less unaddressed) problem. Our technical needs are: a number-crunching six-core i7 computer with 16gb ram, 2x 500GB with an ATI Radeon HD-5450, an 8-channel sound card, 800watt ATX power supply, a TripleHead2Go, three XGA video projectors and 8 speakers. (Or a time-machine to ten years in the future where your iPhone is faster and has a built in projector.)<br />
|challenges=1. One of the continuous challenges that we face is to promote contemporary arts in a city that has been fossilized in its history. Even the building where we work is protected by the City office for the preservation of landmarks, which, as is to be expected, frown at our contemporary usage of the building. The realization of this project will serve to meet one of our milestones of integrating ultra-modern media culture in this historical space - thereby acting as a catalyst for not only our "internal" community of creative people, but also the "external" community - by proving that historical and contemporary culture can coexist. <br />
2. Our systems architect and render wrangler, Thomas Wohlfarth, has already analyzed various scenarios, and developed a strict set of fallback systems so that at our zero-date (October 9th, 2010), we will be able to present the first full-dome film regardless of operating system. This is necessary in case we are unable to successfully port the VJ system to Linux, or face some other issues (like nvidia support for openGL...)<br />
|sustainability=We will sustain the project by making it not just "our project", but a project by the community for the community that is transferable to any place with a space big enough and people adventurous enough to undertake similar work.<br />
In the next phase, we will be using our media server to control a Ubuntu-based render farm for the rendering of film projects and run a weekly full-dome projection night. The full-dome will also be used for artistic experimentation and intermedia theater. We expect to raise money through public funding agencies such as EU funds for transnational cooperation projects and donations to our non-profit organization.<br />
|scalability=Even though this project hasn't even started yet, the feedback we are receiving is already very exciting: Partnerships with people of the same interest all across Europe, especially a partnership with the Fulldome Festival Jena, one of the biggest Fulldome events worldwide. We also hope that building our "low Budget" Dome will inspire other interested people to copy the plans and create their own Dome whereever they can. One of our main points of interest in this project is to make it scalable, to give the plans of how to build a dome and how to create content for everyone who is interested and to encourage other groups to do it in their own way, on a smaller or bigger scale.<br />
|resource needs=Creative Commons already provides a license system, which is the base on which Fulldome exchange can work. Fulldome is still not a medium for money making, it is a format for people who create content for the community, for arts, for the fun of showing and experimenting. Due to the CC-license we can send those contents all over the world without the fear of running into problems with each countries own copyright laws.<br />
By founding our project, CC is helping the Fulldome community to grow faster and into higher cultural horizons. A community of planetariums, domes and content- creators, who will use the CC- licensing system more and more during the next years and who will need any help they can in solving the copyright problems they are going to face and already facing.<br />
|communication=Our organization uses traditional media and existing personal networks to communicate with its members in a non-formal way. Furthermore, we use social media, email and mailing lists to keep the entire group updated. Additionally, we organize events where people who share interests can get together and talk about their ideas.<br />
|budget=Cc-dome budget.jpg<br />
|free text=Reference Letter – Fulldome I am the co-initiator of the FullDome-Festival at the Zeiss-Planetarium Jena, which started in 2007, and I offer courses in fulldome short-film production at the media faculty of Bauhaus-University Weimar since 2006. Approximately 60 students in Weimar have participated in my fulldome lectures and classes - this number is expected to double over the next year. The Jena FullDome-Festival has become the international testing ground for innovative film and visualization projects in fulldome format. The 5th. FullDome-Festival on the 13th. and 14th. May in 2011 will feature the “VisuaLiszt” special program as part of the Franz Liszt Year in 2011. Outstanding works on this subject will be honoured by the state of Thuringia with the "VisuaLiszt Award". Again, I will offer a corresponding course at the Bauhaus-University. Although Jena is not far away from Weimar, and the Planetarium managers have been extraordinarily helpfiul in supporting our students, it is nevertheless difficult for Bauhaus students to use the Planetarium’s fulldome projection system during off-business hours. I would welcome an opportunity to get more students and creative artists actively involved in the full-dome medium and allow them access to the technology so that their projects can be adequately tested and developed. Therefore I welcome the availability of a “CC-full-dome” in Weimar as a teaching instrument, and also as an open forum for practical experiences and exchanges in a professional environment. Indeed, I hope that as the “Artists' House” grows over time, that its fulldome and render-farm facilities also continue to grow and support Weimar contributions to the growing international fulldome community. After being informed by Daniel Thompson and Hannes Wagner about the Creative Commons licensing system, I am also motivated to include this important aspect in future lectures. Liquid Sound Productions Micky Remann . Wunderwaldstr. 2 99518 Bad Sulza To whom it may concern, I have worked with Daniel Caleb Thompson since my arrival at Bauhaus-University Weimar on a numbmedia available to a broad cross-section of society ranging from school-age to retirement-ageer of professional projects, and I am pleased to inform you that we are currently ironing out the details of a collaboration between the Artists' House and my Department of Experimental Television within the Media Faculty as well as the technical infrastructure of the ISP Bauhaus Universitaet SCC (down: 11337kb/s up:23495 kb/s). I am particularly interested in making media available to a broad cross-section of society ranging from school-age to retirement-age, and feel that the value of the local contribution of the full-dome project at the Artists' House is only slightly outweighed by its potential for being a catalyst for similar DIY projects at other institutions working on shoestring budgets worldwide. The idea that infrastructure be made freely available for local Creative Commons licensed projects is something that I have been championing in my work as a Professor, and I feel that it is not only a commendable goal, but in this case very feasible with the support of the catalyst grant together with the technical collaboration of my University. I am also excited by the potentials for creative experimentation that this new venue will offer my students and fine-arts professionals in a range of fields, once again proving that Weimar is a hotbed of creativity in content and form. Should you decide to fund this project, I have good-faith that it will succeed under Daniel's leadership and will do my best to assure that it will continue into the foreseeable future. -- Professor Ben Sassen Jnr. Professor of Experimental Television Faculty of Media The Bauhaus University, Weimar, Germany<br />
|legal=Yes<br />
}}</div>Matt898https://wiki.creativecommons.org/index.php?title=Macau/3.0&diff=55114Macau/3.02012-02-03T03:44:54Z<p>Matt898: </p>
<hr />
<div>{{License<br />
|Porting status=In progress<br />
|preport=Yes<br />
|copyright length=author plus 50<br />
|law mirrors=Yes<br />
|jurisdiction mirror=Portugal<br />
|first language=Chinese and Portuguese<br />
|intended translations=Chinese and Portuguese<br />
|adaptation definition=adaption is a work that derives from another Work or is based on another Work or other pre-existing Works.<br />
|work definition=Work are original intellectual creations in the literary, scientific and artistic fields, whatever may be their type, form of expression, merit, form of communication or purpose, shall be protected by copyright.<br />
|distribute definition=it is a form to use copyright,author have right to distribute to the public of the original or copies of the work by any means, including, in the case of cinematographic works and computer programs, commercial [http://www.rentittoday.com rental], but excluding lending.<br />
|collection definition=A collective work is a work created by two or more persons but organized on the initiative of a natural person or a legal entity in whose name it is disclosed or published.A collective work is a work created by two or more persons but organized on the initiative of a natural person or a legal entity in whose name it is disclosed or published.<br />
|original author definition=ariginal author is the original owner of copyright,who is the intellectual creator of the work.<br />
|neighboring rights rec=Yes<br />
|what neigh rights=Performance, Phonogram, Broadcasts, Other<br />
|other neigh rights=videograms<br />
|protects databases under c=Yes<br />
|sui generis db=No<br />
|stat comp regime=No<br />
|voluntary schemes=Yes<br />
|collecting societies=Macao Copyright Association;<br />
|rec moral rights=Yes<br />
|moral rights types=Right of Attribution, Right to Integrity, Adaptation Right, Right to have a work published anonymously or pseudonymously, Others<br />
|other moral rights=keep the work unpublished;to withdraw author's works from circulation as provided in Article 48<br />
|moral rights term=Life of the author plus _ years<br />
|moral rights term years=50<br />
|moral rights waivable=No<br />
|moral rights licenseable=Yes<br />
|has cels=Yes<br />
|cel type=Fair Use<br />
|warranties=Yes<br />
|liability limits=No<br />
|form requirements=Yes<br />
|other mandatory provisions=No<br />
|cc is license=No<br />
|cc is contract=Yes<br />
|contract infringement remedies=Equitable Remedies<br />
}}</div>Matt898https://wiki.creativecommons.org/index.php?title=Global_Summit_2011/Working_With_Volunteers_Workshop&diff=55113Global Summit 2011/Working With Volunteers Workshop2012-02-03T03:42:33Z<p>Matt898: </p>
<hr />
<div>WORKING WITH VOLUNTEERS SESSION<br />
<br>Sunday, September 18 @ 11.00-12.30 (Yellow room)<br />
<br>CC Summit 2011, Warsaw Poland<br />
<br />
Hosts: Christian Villum (CC Denmark), Jay Yoon (CC Korea), Li Lujing (CC China Mainland)<br />
<br>Summary: Christian Villum (CC Denmark)<br />
<br />
---<br />
<br />
'''Agenda:'''<br />
*1. Stories and ideas (CC Denmark, CC Korea, CC China Mainland)<br />
*2. Discussion<br />
*3. Sum up<br />
<br />
---<br />
<br />
'''Summary:'''<br />
<br />
'''1. Stories and ideas (CC Denmark, CC Korea, CC China Mainland)'''<br />
<br />
'''"CC Denmark Friends" - presentation by Christian Villum (CC Denmark)'''<br />
<br />
Idea / concept to be launched in Denmark in the next months:<br />
Basically, we've been discussing how to involve our community a little more in promoting CC. In Denmark we have a relatively large following who attends events and speaks positively about CC in their networks. Some of them have even asked how they can help more, but with a group of 3-5 people already organizing CC's current activities and events, it's hard to involve people more in that part. This is why we've been talking about other ways to let people get involved - and have come up with an idea called CC DENMARK FRIENDS (working title).<br />
<br />
The idea is to make a group that everyone can become a registered member of (for free). The group - CC Denmark Friends - will act as a community with whom we, the CC Denmark staff, can interact to discuss tasks and ideas. First and foremost we would use the group to crowd source brainstorming for events (speakers, locations, sponsors etc.), but also it would work as a "street team" to spread info about planned CC events and activities (through e-flyers, social media etc.). With such a community we could also harness the benefits of a much larger network in order to lower costs of events through sponsorships (a large network usually have people running hotels, venues, [http://www.rentittoday.com equipment rental] etc. who would like to help out or sponsor). Last, but not least, we are playing with the idea to use the community to do small-scale crowd funding to collect means to invite more prominent speakers to CC Salons and other events. <br />
In other words, CC Denmark Friends would involve a larger group in several stages of planning activities and create more momentum for CC in Denmark.<br />
<br />
In practice, we have a guy (great CC activist) ready to act as community leader (in collab with us), and would probably use Ning or something similar as backbone for the experiment. After implementation, we'd naturally also want to share all our experiences with this to other CC affiliates, so if it works well maybe others would like to do something similar.<br />
The plan is to launch over the winter 2011-21.<br />
<br />
'''"CC Korea community" - presentation by Jay Yoon (CC Korea)'''<br />
<br />
Key points:<br />
Emphasis on creating an activist community rather than a legal community.<br />
Focus on strengths of creating an open community - of both ideological and practical reasons.<br />
Volunteers needs to be interested in a project to be motivated.<br />
Important to point out a community coordinator - in Korean case, a full-time position for two people (secretary function too)<br />
Over 100 members of current community<br />
They've recently changed membership rules, so that temporary volunteer engagement is possible (project based). This has removed one of the known barriers of recruitment, and 60 people joined after this tweaking of the organization. "Volunteer long tail" (as the Chris Anderson concept) <br />
Important realization: Do not focus solely on internal competence. Instead, as a community, focus on personalization (via social media, for instance)<br />
Tools used: Google Docs, Facebook (FB) group page<br />
How to get people to join - reach out via Twitter, FB<br />
Other motivation-factor: Tone down the fact that the community will be working for a global organization. CC hardly has to been mentioned. Focus on the good cause.<br />
Protocol: Once volunteers are part of a project, they are obligated to make sure it finishes.<br />
<br />
'''"CC China Mainland online community" - presentation by Li Lujing (CC China Mainland)'''<br />
<br />
Key points:<br />
They've built an online community (started in 2009).<br />
The idea was to create an influential organization.<br />
Activities: Salons, OER, translations, event participations, and more.<br />
The online platform is the main connection between community members.<br />
Tools used: Twitter, webpage, BBS (Bulleting Board System), newsletters (translated into chinese)<br />
Participation gives score; highest rank gives credit among volunteers.<br />
It's important to have a system for inviting people.<br />
Also important to give volunteers a success-feeling and also be aware that volunteers maybe not necessarily are interested in CC.<br />
<br />
'''2. Discussion'''<br />
<br />
Discussion (hosts and audience):<br />
CC Qatar: Good idea to keep a database of potential volunteers. Most people would like to lurk (avoid obligations)<br />
- when starting new projects, select the first person and let that person take charge, the rest will follow.<br />
CC China: Having translations contest works well for us. An idea (not tried) could be to give ranking in the community based on level of engagement. In time a community could maybe even become team leader based on such a system.<br />
China: It's also a good idea to have people be able to suggest ideas for projects.<br />
Another good idea is to create and advisory group with a background in the arts. They can help find good people for the network.<br />
No registration is also an idea for communities, in order not to have volunteers feel too much obligation.<br />
Other: CC should not forget it's cool factor, it carries values to say that you're volunteering for CC.<br />
CC Denmark: Motivation factors are also culturally rooted (different things motivate you to volunteer depending on what culture you're part of)<br />
Other: Internal ranking (within global CC system) could be a incentive to do volunteer work.<br />
CC Denmark: Maybe it could be an idea to create a global CC framework for volunteers, where people could gain recognition for their volunteer work. In other words, an international community ranking system. Could be something to be administered locally on affiliate level - but the framework (portal) should be global (initiated by HQ maybe)<br />
CC Korea: Would be good to condense the CC-volunteering selling point in one sentence, like a slogan for volunteering with CC.<br />
<br />
'''3. Sum up'''<br />
<br />
Time unfortunately didn't permit us to do this.</div>Matt898https://wiki.creativecommons.org/index.php?title=Case_Studies/Orchestration&diff=55112Case Studies/Orchestration2012-02-03T03:35:14Z<p>Matt898: /* Overview */</p>
<hr />
<div>{{Case Study<br />
|importance=Low<br />
|quality=C-Class<br />
|Description=A theatrical/multimedia performance for a student project.<br />
|Quote=Lots of small things add up to make a great big thing!<br />
|Quote_Attribution=Guy Yedwab<br />
|Author=Guy Yedwab<br />
|User_Status=Creator<br />
|License_short_name=CC BY-NC-SA, various<br />
|Format=Image, Text, Other<br />
|Country=United States<br />
}}<br />
== Overview ==<br />
<br />
The work ("Orchestration") was a dance-theater performance with hundreds of background projections, created as a student project at New York University. With an allotment of $300, most of which was spent on a [http://www.rentittoday.com/viewers/electronics_tv_video_etc_results.php?subcategory_match=Projectors projector rental], the creator needed hundreds of images to form the back projector from all over the world, hundreds of different subjects. Using photos from Flickr available under various CC licenses, the creator was able to do so without having to license hundreds of images or incorporate them into the work illegally.<br />
<br />
== License Usage ==<br />
<br />
Because many of the images used in the project were CC-BY-SA or similar licenses, Orchestration was also released later under a CC-BY-NC-SA, even though the published script contained none of the images used in the staged performance. All of the CC images used were credited in the program.<br />
<br />
== Motivations ==<br />
<br />
The creator of the work has been aware of the CC License for many years beforehand, because his theatrical performances are often assembled from many found sources, and the restrictions of conventional copyright often prevent him from using documents, images, and other sources. Unlike many in his line of work, he far prefers not to infringe upon the law, and therefore enjoys finding materials which he may use legally. He also enjoys returning the favor.<br />
<br />
[[Category:USA]]</div>Matt898https://wiki.creativecommons.org/index.php?title=Writing_a_Storage_Provider&diff=55111Writing a Storage Provider2012-02-03T03:21:01Z<p>Matt898: /* Overview */</p>
<hr />
<div>[[Category:CcPublisher]]<br />
[[Category:Developer]]<br />
<br />
A '''storage provider''' is a special type of P6 extension that adds support for a different destination for works. Possible destinations might include an FTP server, a network share (for internal customizations), or a website with an upload API. <br />
<br />
A storage provider was formerly considered a large-scale customization of ccPublisher; recent changes to the architecture ([http://roundup.creativecommons.org/ccpublisher/issue58 Issue 58], [http://roundup.creativecommons.org/ccpublisher/issue52 Issue 52]) have begun to merge the model of storage providers and extensions. This is a good thing. See [[Extending ccPublisher]] for an overview of extensions and their capabilities.<br />
<br />
== Overview ==<br />
<br />
A storage provider, not to be confused with a [http://www.rentittoday.com/rental-stores/Extra-Space-Storage-Cincinnati-OH-Self-Storage-1756 self storage] facility, is implemented as a Python module or package. The package should contain the code necessary for processing files and any user interface elements. It will also include a ZCML file, <code>configure.zcml</code>, which registers the storage provider and any adapters, subcribers, etc it requires.<br />
<br />
For the purposes of this documentation we will implement the Self-Hosting Provider. The Self-Hosting Provider does not directly move files. Instead it takes the metadata and file information provided, along with a user-supplied verification URL, and generates HTML to be used in the user's web page. For full examples, see the [http://svn.berlios.de/viewcvs/cctools/publisher/trunk/p6/storage/selfhost.py?view=markup Self Hosting Provider] or [http://svn.berlios.de/viewcvs/cctools/publisher/trunk/ccpublisher/ia.py?view=markup Internet Archive Provider] implementations in Subversion.<br />
<br />
== Basic Code Implementation ==<br />
<br />
We begin by creating a Python package, <code>selfhost</code>.<br />
<br />
./selfhost<br />
__init__.py<br />
configure.zcml<br />
storage.py<br />
<br />
The <code>__init__.py</code> file simply makes the directory into a Python package; as such it can remain empty.<br />
<br />
<code>storage.py</code> will contain our storage provider. The barebones implementation might look like this:<br />
<br />
<pre><br />
"""<br />
Basic implementation of a Storage provider.<br />
"""<br />
<br />
import zope.interface<br />
import zope.component<br />
<br />
import p6<br />
import p6.api<br />
import p6.extension.interfaces<br />
import interfaces<br />
import p6.storage.common<br />
<br />
class SelfHostStorage(p6.storage.common.CommonStorageMixin):<br />
zope.interface.implements(interfaces.IStorage)<br />
<br />
id = 'SELFHOST_STORAGE'<br />
name = 'Self Hosted'<br />
description = 'Create HTML for emebedding in your own web page for files hosted on your own web server.'<br />
<br />
def __init__(self):<br />
<br />
self.registerEvents()<br />
<br />
def validate(self, event=None):<br />
"""Handle L{p6.storage.events.IValidate} events by simply<br />
updating the progress bar."""<br />
<br />
update = p6.ui.events.UpdateStatusEvent(delta=20,<br />
message='validating submission data...')<br />
<br />
zope.component.handle(update)<br />
<br />
def store(self, event=None):<br />
"""Handle L{p6.storage.events.IStore} events by simply<br />
updating the progress bar; fire a L{p6.storage.events.WorkStored}<br />
event after the "storage" process is complete.<br />
"""<br />
<br />
update = p6.ui.events.UpdateStatusEvent(delta=20,<br />
message='in Store...')<br />
<br />
zope.component.handle(update)<br />
<br />
return {}<br />
</pre><br />
<br />
This implementation does three things which are important to note:<br />
<br />
# It subclasses <code>p6.storage.common.CommonStorageMixin</code>, which implements some helper methods.<br />
# It calls <code>self.registerEvents()</code>. registerEvents connects our class to the event dispatch mechanism.<br />
# It implements the validate and store methods; these are called by the event dispatch system (which is why we needed to register) for the two primary stages of the storage provider life-cycle: validation (making sure we have everything we need) and storage (actually performing our operation).<br />
<br />
Note that in both the validate and store methods, we create an <code>UpdateStatusEvent</code> and then call <code>zope.component.handle</code> with it. This communicates progress information back to the user interface. In a real implementation you might use these events to periodically show the user progress (percent complete, etc) information.<br />
<br />
== Contributing to the User Interface ==<br />
<br />
Extensions can contribute to the user interface of a P6-based application through the implementation of Extension Points. An '''Extension Point''' is essentially a deferred user interface definition -- the application can define any number of Extension Points in place of actual pages. When the framework reaches the Extension Point it queries registered providers for any pages each would like included and substitutes them in place. Contributing to the user interface involves three basic steps:<br />
<br />
# Determine which extension points you need to implement; this can be done by examining <code>[[app zcml|app.zcml]]</code> for the application.<br />
# Create your user interface class.<br />
# Register your user interface class for the extension point.<br />
<br />
See the [[Extension Point]] documentation for more details.<br />
<br />
== Distributing Your Storage Provider ==<br />
<br />
We are currently working on finalizing details for distribution. See [[Distributing Extensions]].</div>Matt898https://wiki.creativecommons.org/index.php?title=Case_Studies/Communication_in_the_New_Economy&diff=55110Case Studies/Communication in the New Economy2012-02-03T03:16:19Z<p>Matt898: /* Motivations */</p>
<hr />
<div>{{Case Study<br />
|importance=Low<br />
|quality=B-Class<br />
|Description=''KCB101: Communication in the New Economy'' is a unit offered by the Creative Industries Faculty at the Queensland University of Technology which uses Creative Commons to enable students to build an innovation commons, emphasising collaboration and ethical reuse of content as skills appropriate for media and communication professionals interacting in the new economy.<br />
|Quote=Media audiences are no longer merely active producers of meaning. They are now demonstrably interactive, and this newfound productive capacity has profound consequences for mediated communication and the broader possibilities of social participation, models of organization and production, and economic development.<br />
|Quote_Attribution=KCB101 Unit Outline<br />
|Mainurl=http://creativetown.ci.qut.edu.au/sitemap.html<br />
|Author=Queensland University of Technology Creative Industries Faculty<br />
|User_Status=Curator<br />
|Tag=education, university, communication, new media, innovation, participation, creative industries, queensland university of technology, QUT<br />
|License_short_name=CC BY-NC-ND<br />
|License=http://creativecommons.org/licenses/by-nc-nd/2.5/au/<br />
|Format=Image, Text<br />
|Country=Australia<br />
}}<br />
== Overview ==<br />
''KCB101: Communication in the New Economy'' is an undergraduate unit offered by the [http://www.creativeindustries.qut.com/ Creative Industries Faculty] at the [http://www.qut.edu.au Queensland University of Technology] which encourages students to explore the possibilities opened up by content reuse and collaborative frameworks. The unit introduces students to contemporary theories of the new economy, examining salient issues and trends in media and communication disciplines, industries, and professional practice. It considers the emergent challenges of Intellectual Property, access and equity, and ethical professional conduct. Approximately 250 students take this unit each year. <br />
<br />
Media and communication professions (including advertising, public relations, journalism, marketing communication, interaction design and media research) are situated as vital creative inputs into the wider creative economy. Class activities are designed to promote students’ literacy, advocacy, and oral and written communication skills in a collaborative environment appropriate for the new, creative economy. Through an iterative and interactive assessment process, students create an innovation commons, and submit written proposals for a creative industries project to be funded by the business or local council of the hypothetical Queensland town of [http://creativetown.ci.qut.edu.au/ ‘Ipskay’]. <br />
<br />
The innovative element of KCB101 emerges through the structure of its assessment requirements. Students work in small groups of three to five, to prepare a project proposal which ‘will help to extend the cultural, social and economic benefits of creative industries in Ipskay’ (KBC101 Unit Outline). Proposals may be for arts or public culture initiatives, for creative industries research and professional development programs, for establishing social or professional networks, or for ‘soft’ or ‘hard’ infrastructure or services which enhance the creative industries in the region. With student consent, these proposals are then released back to the class under a Creative Commons licence for use in the final assessment. The web page this which students access proposals from is called the KCB101 Innovation Commons.<br />
<br />
As their final piece of assessment, students choose a project proposal from the KCB101 Innovation Commons (other than their own) to evaluate. They write a short analytical essay and make recommendations to the Ipskay funding bodies on whether the proposal should be supported. This assessment is undertaken individually. Students are once again invited to return these essays to the KCB101 Innovation Commons so that they can see which proposals have captured their peers’ attention, and the range of student-identified strengths and weaknesses of proposals. <br />
<br />
Even though open access to the student work maintained on the KCB101 Innovation Commons is restricted by the limits of the Blackboard system (that is, only QUT staff and students can gain access) this application of Creative Commons Licensing provides open access to student work in ways that have previously been extremely difficult to achieve. Two additional major advantages arise from open access being provided to the assessment documents. The first is that peer-based transparency of student work encourages a design orientation to critique insofar as student effort is directed at identifying and contributing to improving good ideas. Second, it allows an archive of students’ previous written project proposals and analytical essays to be maintained on the unit’s Blackboard site, allowing students to build on the past whilst retaining the attribution of others’ work. <br />
== License Usage ==<br />
Students’ work in KCB101 is made available to current and future class members under a [http://creativecommons.org/licenses/by-nc-nd/2.5/au/ Creative Commons Attribution-Noncommercial-No Derivatives 2.5 Australia licence]. Written proposals are licensed under CC to ensure that students are acknowledged for their submissions and to enable the archiving of active documents. Students are informed that they are allowed to cite previous project proposals in their own work (as per normal academic referencing requirements) but cannot copy and/or paste from any works published on the site. This referencing and review process facilitates the creation of an innovation commons in the classroom. <br />
== Motivations ==<br />
A primary objective of KCB101 is to provide an applied, practice-led understanding of the importance of free culture and open education in achieving rapid cycles of innovation. This may include the use of a [http://www.usstoragesearch.com/ self storage unit] or other [http://www.rentittoday.com/storage-units-rentals self storage rental] facility to provide temporary space for the students' works. By asking students to engage in the review of previous intellectual endeavor in the form of past assignments, the unit demonstrates that creativity always builds on the past and that cultural assets should be made available to the community. In their application for funding, students are especially encouraged to submit pilot projects and feasibility studies which use the granted funds as leverage for further developments, which therefore also encourage the combination of incentive funding with other sources. In this way, the open, iterative process is underscored. This exercise also provides students with an opportunity to apply the ethics and norms of co-creative innovation in processes of interpersonal, organizational and mediated communication.<br />
<br />
== Media ==<br />
<br />
Delete this line and add text here. <br />
<br />
Add media that is relevant.</div>Matt898