Creative Commons - User contributions [en]

CC Ports by Jurisdiction

2014-10-02T22:41:20Z

LuisVilla: Make table sortable, at request of Kat. Romania is weirdly screwy for some reason, though?

{| class="wikitable sortable" style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Jurisdiction || style="background-color:#CCCCCC;" | Most Recent Ported Version || style="background-color:#CCCCCC;" | Earlier Ported Versions || style="background-color:#CCCCCC;"| 3.0 Public Discussion || style="background-color:#CCCCCC;" | 3.0 Launch Date
|-
| Argentina || 2.5 || none || ||
|-
| Australia || 3.0 || 2.5, 2.1, 2.0 || 12 June 2008 || 8 June 2010
|-
| Austria || 3.0 || 2.0 || 11 Feb 2008 || 14 Aug 2008
|-
| Belgium|| 2.0 || none || ||
|-
| Brazil || 3.0 || 2.5, 2.0 || || 29 Jan 2010
|-
| Bulgaria || 2.5 || none || ||
|-
| Canada || 2.5 || 2.0 || ||
|-
| Chile || 3.0 || 2.0 || 28 May 2008 || 22 Aug 2010
|-
| China || 3.0 || 2.5 || 12 Apr 2011 || 30 Aug 2012
|-
| Colombia || 2.5 || none || ||
|-
| Costa Rica || 3.0 || none || 28 July 2010 || 12 Jan 2011
|-
| Croatia || 3.0 || 2.5, 2.0 || || 19 March 2008
|-
| Czech Republic || 3.0 || none || 12 Jan 2009 || 16 Apr 2009
|-
| Denmark || 2.5 || none || ||
|-
| Ecuador || 3.0 || none || 21 Feb 2008 || 22 Apr 2008
|-
| Egypt || 3.0 || none || 1 Feb 2010 || 30 Apr 2013
|-
| England and Wales || 2.0 || none || ||
|-
| Estonia || 3.0 || none || 1 Jun 2010 || 6 Jan 2011
|-
| Finland || 1.0 || none || ||
|-
| France || 3.0 || 2.0 || 15 Sep 2011 || 11 Apr 2012
|-
| Germany || 3.0 || 2.0 || 18 Dec 2007 || 24 July 2008
|-
| Greece || 3.0 || none || 7 Mar 2007 || 13 Oct 2007
|-
| Guatemala || 3.0 || none || 2 May 2008 || 23 Oct 2008
|-
| Hong Kong || 3.0 || none || 3 Jan 2008 || 25 Oct 2008
|-
| Hungary || 2.5 || none || ||
|-
| India || 2.5 || none || ||
|-
| Intergovernmental organization ("IGO") || 3.0 || none || || 6 Dec 2013
|-
| Ireland || 3.0 || none || 2 Mar 2011 || 27 Feb 2012
|-
| Israel || 2.5 || 1.0 || ||
|-
| Italy || 3.0 || 2.5, 2.0 || 27 Oct 2009 || 10 June 2011
|-
| Japan || 2.1 || 2.0 || ||
|-
| Luxembourg || 3.0 || none || || 15 Oct 2007
|-
| Macedonia || 2.5 || none || ||
|-
| Malaysia || 2.5 || none || ||
|-
| Malta || 2.5 || none || ||
|-
| Mexico || 2.5 || none || ||
|-
| Netherlands || 3.0 || 2.5, 2.0, 1.0 || || 31 July 2007
|-
| New Zealand || 3.0 || none || 25 Aug 2007 || 27 Oct 2007
|-
| Norway || 3.0 || none || 21 Feb 2008 || 6 Jun 2008
|-
| Peru || 2.5 || none || ||
|-
| Philippines || 3.0 || none || || 15 Dec 2007
|-
| Poland || 3.0 || 2.5, 2.0 || 5 Dec 2007 || 23 Jul 2009
|-
| Portugal|| 3.0 || 2.5 || 23 Nov 2010 || 14 Oct 2011
|-
| Puerto Rico || 3.0 || none || Jul 2007 || 22 Feb 2008
|-
| Romania || 3.0 || none || 29 Jan 2008 || 2 Sept 2008
|-
| Scotland || 2.5 || none || ||
|-
| Serbia || 3.0 || none || 14 Nov 2007 || 15 Dec 2007
|-
| Singapore || 3.0 || none || 23 Jun 2008 || 25 Jul 2008
|-
| Slovenia || 2.5 || none || ||
|-
| South Africa || 3.0 || 2.5 || || 23 Jun 2014
|-
| South Korea || 2.0 || none || ||
|-
| Spain || 3.0 || 2.5, 2.1, 2.0 || 24 Feb 2007 || 17 Nov 2008
|-
| Sweden || 2.5 || none || ||
|-
| Switzerland || 3.0 || 2.5 || none || 16 April 2012
|-
| Taiwan || 3.0 || 2.5, 2.0 || || 31 Oct 2009
|-
| Thailand || 3.0 || none || 26 Nov 2007 || 2 Apr 2009
|-
| Uganda || 3.0 || none || 4 Jan 2012 || 28 Nov 2012
|-
| United States || 3.0 || none || || 23 Feb 2007
|-
| Venezuela || 3.0 || none || 2 Feb 2012 || 29 Nov 2013
|-
| Vietnam || 3.0 || none || 9 Jul 2009 || 7 May 2010
|-
|}
[[Category:Legal]]

CC Ports by Jurisdiction

2014-10-02T18:03:47Z

LuisVilla: Fix table.

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Jurisdiction || style="background-color:#CCCCCC;" | Most Recent Ported Version || style="background-color:#CCCCCC;" | Earlier Ported Versions || style="background-color:#CCCCCC;"| 3.0 Public Discussion || style="background-color:#CCCCCC;" | 3.0 Launch Date
|-
| Argentina || 2.5 || none || ||
|-
| Australia || 3.0 || 2.5, 2.1, 2.0 || 12 June 2008 || 8 June 2010
|-
| Austria || 3.0 || 2.0 || 11 Feb 2008 || 14 Aug 2008
|-
| Belgium|| 2.0 || none || ||
|-
| Brazil || 3.0 || 2.5, 2.0 || || 29 Jan 2010
|-
| Bulgaria || 2.5 || none || ||
|-
| Canada || 2.5 || 2.0 || ||
|-
| Chile || 3.0 || 2.0 || 28 May 2008 || 22 Aug 2010
|-
| China || 3.0 || 2.5 || 12 Apr 2011 || 30 Aug 2012
|-
| Colombia || 2.5 || none || ||
|-
| Costa Rica || 3.0 || none || 28 July 2010 || 12 Jan 2011
|-
| Croatia || 3.0 || 2.5, 2.0 || || 19 March 2008
|-
| Czech Republic || 3.0 || none || 12 Jan 2009 || 16 Apr 2009
|-
| Denmark || 2.5 || none || ||
|-
| Ecuador || 3.0 || none || 21 Feb 2008 || 22 Apr 2008
|-
| Egypt || 3.0 || none || 1 Feb 2010 || 30 Apr 2013
|-
| England and Wales || 2.0 || none || ||
|-
| Estonia || 3.0 || none || 1 Jun 2010 || 6 Jan 2011
|-
| Finland || 1.0 || none || ||
|-
| France || 3.0 || 2.0 || 15 Sep 2011 || 11 Apr 2012
|-
| Germany || 3.0 || 2.0 || 18 Dec 2007 || 24 July 2008
|-
| Greece || 3.0 || none || 7 Mar 2007 || 13 Oct 2007
|-
| Guatemala || 3.0 || none || 2 May 2008 || 23 Oct 2008
|-
| Hong Kong || 3.0 || none || 3 Jan 2008 || 25 Oct 2008
|-
| Hungary || 2.5 || none || ||
|-
| India || 2.5 || none || ||
|-
| Intergovernmental organization ("IGO") || 3.0 || none || || 6 Dec 2013
|-
| Ireland || 3.0 || none || 2 Mar 2011 || 27 Feb 2012
|-
| Israel || 2.5 || 1.0 || ||
|-
| Italy || 3.0 || 2.5, 2.0 || 27 Oct 2009 || 10 June 2011
|-
| Japan || 2.1 || 2.0 || ||
|-
| Luxembourg || 3.0 || none || || 15 Oct 2007
|-
| Macedonia || 2.5 || none || ||
|-
| Malaysia || 2.5 || none || ||
|-
| Malta || 2.5 || none || ||
|-
| Mexico || 2.5 || none || ||
|-
| Netherlands || 3.0 || 2.5, 2.0, 1.0 || || 31 July 2007
|-
| New Zealand || 3.0 || none || 25 Aug 2007 || 27 Oct 2007
|-
| Norway || 3.0 || none || 21 Feb 2008 || 6 Jun 2008
|-
| Peru || 2.5 || none || ||
|-
| Philippines || 3.0 || none || || 15 Dec 2007
|-
| Poland || 3.0 || 2.5, 2.0 || 5 Dec 2007 || 23 Jul 2009
|-
| Portugal|| 3.0 || 2.5 || 23 Nov 2010 || 14 Oct 2011
|-
| Puerto Rico || 3.0 || none || Jul 2007 || 22 Feb 2008
|-
| Romania || 3.0 || none || 29 Jan 2008 || 2 Sept 2008
|-
| Scotland || 2.5 || none || ||
|-
| Serbia || 3.0 || none || 14 Nov 2007 || 15 Dec 2007
|-
| Singapore || 3.0 || none || 23 Jun 2008 || 25 Jul 2008
|-
| Slovenia || 2.5 || none || ||
|-
| South Africa || 2.5 || none || ||
|-
| South Korea || 2.0 || none || ||
|-
| Spain || 3.0 || 2.5, 2.1, 2.0 || 24 Feb 2007 || 17 Nov 2008
|-
| Sweden || 2.5 || none || ||
|-
| Switzerland || 3.0 || 2.5 || none || 16 April 2012
|-
| Taiwan || 3.0 || 2.5, 2.0 || || 31 Oct 2009
|-
| Thailand || 3.0 || none || 26 Nov 2007 || 2 Apr 2009
|-
| Uganda || 3.0 || none || 4 Jan 2012 || 28 Nov 2012
|-
| United States || 3.0 || none || || 23 Feb 2007
|-
| Venezuela || 3.0 || none || 2 Feb 2012 || 29 Nov 2013
|-
| Vietnam || 3.0 || none || 9 Jul 2009 || 7 May 2010
|-
|}
[[Category:Legal]]

CC Friendly Lawyers

2014-09-18T21:41:24Z

LuisVilla: Add Italian lawyer

<span style="color: red">Please note that CC does not provide referral services, and that we do not necessarily endorse or recommend anyone on this list for any particular client or circumstance.</span>

== Canada ==
* [http://artistslegaloutreach.ca/ Artists' Legal Outreach]

== United States ==

* Withrow & Betinol Law (Los Angeles, CA): info@wibelaw.com. [http://www.wibelaw.com www.wibelaw.com]
* '''Michael Sullivan''' (San Jose, CA): msullivan@mikesullivanlaw.com [http://www.mikesullivanlaw.com/creative-commons-license-questions.html Law Office of Michael J. Sullivan]
* [http://www.lilabailey.com/ Lila Bailey]
* [https://www.linkedin.com/in/aureliajschultz Aurelia Schultz]

== Sweden ==
* Morus konsult AB: info@morus.se [http://morus.se/en/ http://morus.se/en/]

== Germany ==
* [http://jbb.de JBB Rechtsanwälte] including [http://www.jbb.de/anwaelte/till-jaeger/ Till Jaeger]

== Italy ==
* [http://www.array.eu/#people Array], including Carlo Piana

CC Friendly Lawyers

2014-09-18T21:20:49Z

LuisVilla:

CC Friendly Lawyers

2014-09-18T21:16:39Z

LuisVilla: Remove two lawyers with broken links/no longer seem to practice in this area; add German firm

<span style="color: red">Please note that CC does not provide referral services, and that we do not necessarily endorse or recommend anyone on this list for any particular client or circumstance.</span>

== Canada ==
* [http://artistslegaloutreach.ca/ Artists' Legal Outreach]

== United States ==

* Withrow & Betinol Law (Los Angeles, CA): info@wibelaw.com. [http://www.wibelaw.com www.wibelaw.com]
* '''Michael Sullivan''' (San Jose, CA): msullivan@mikesullivanlaw.com [http://www.mikesullivanlaw.com/creative-commons-license-questions.html Law Office of Michael J. Sullivan]
* [Lila Bailey http://www.lilabailey.com/]
* [https://www.linkedin.com/in/aureliajschultz Aurelia Schultz]

== Sweden ==
* Morus konsult AB: info@morus.se [http://morus.se/en/ http://morus.se/en/]

== Germany ==
* [http://jbb.de JBB Rechtsanwälte] including [http://www.jbb.de/anwaelte/till-jaeger/ Till Jaeger]

Making TOS Work With CC

2014-04-18T22:20:07Z

LuisVilla: /* 2. content owned by contributors */ - clarify opening sentence

While we try to make CC licensing as simple as possible, the fact remains that copyright is complicated, and there are lots of things to consider when you decide to integrate CC licensing to your website. This page addresses one of the necessary components -- offering guidelines and considerations to help you update your website terms of service to make them work with your use of CC licenses.

===Categories of content===
There are three buckets of content to consider when integrating CC licensing to your site:
# content owned by you, the platform provider;
#content owned by contributors; and
#third party content uploaded by you and your contributors.

CC licensing can be used for any or all of these buckets. For each bucket of content, regardless of whether you use CC licensing, the terms of service should define the universe of applicable content, and address ownership of the content and its applicable licensing terms, and the conditions of upload where relevant.

===1. content owned by you as platform provider===
If you choose to apply a CC license to this category of content, you should --
:*make sure you have [http://wiki.creativecommons.org/Considerations_for_licensors_and_licensees#Clear_rights_needed_to_use_the_material. the rights you need] to license it under a CC license; and

:*remove provisions from the TOS that limit or impose additional conditions on uses the CC license permits. For example, the TOS must not have more burdensome attribution requirements than what is required by the CC license.

:'''Representations & warranties:''' Although the CC license itself does not include any reps or warranties, the license does not prohibit you, as the rights holder, from including reps and warranties about the content in the TOS.

===2. content owned by contributors===
If you want to require contributors to CC-license the content they upload to your platform under the TOS, there are two different approaches --
:*The simplest approach is to insert a provision into the TOS that requires contributors to grant a CC license to their content upon upload to the site. In that scenario, you (the platform provider) get the same rights to use the content under copyright as the public under the CC license.

:*The alternative (and more common) approach is used when a platform provider needs more rights from contributors under copyright than the relevant CC license grants – for example, if the platform provider needs to obtain commercial rights from the author but wants to have uploaders grant a CC license allowing content to be used for noncommercial purposes only. In that case, the TOS should include a separate license to the content from contributors to the platform provider and include the provision requiring contributors to grant a CC license to their content upon upload to the site.

:With either approach:

:'''Representations & warranties''' - You may get reps and warranties from uploaders or ask uploaders to agree to particular terms and conditions via the TOS. For example, the TOS may ask contributors to provide assurances that they own the necessary rights to upload and license the content, or they may require uploaders to agree to be attributed in a particular manner.

::''Sample language:'' "You represent, warrant, and agree that no Content posted or otherwise shared by you on any of the Websites, violates or infringes upon the rights of any third party, including copyright, trademark, privacy, publicity, or other personal or proprietary rights, or contains libelous, defamatory, or otherwise unlawful material."

:'''Automatic upgrade clause:''' Since only the rights holder can apply a license to the content, it is important to obtain permission to use contributor content under '''future versions''' of the relevant CC license at the time of upload.

::''Sample language:'' “You hereby agree that all Content you own and voluntarily post on the Websites may be used under the terms of the Creative Commons Attribution 4.0 International license or any later version of a Creative Commons Attribution International License.”

===3. third party content (i.e. content owned by someone other than the uploader)===

There are several types of third party content that can be allowed for upload via TOS:
*content that the uploader has permission to upload (including CC-licensed content),
*content that falls outside of copyright (i.e. is in the public domain), and
*content that the uploader has the right to upload because of an exception or limitation to copyright (e.g., fair use).

Each category carries with it a different level of risk and related considerations. For each category:

:'''Require clear marking.''' If you allow upload of third party content, the TOS should require uploaders to mark the content appropriately so that users of the website can discern the relevant copyright status and attribution information. [Note that appropriate marking is also important for third party content uploaded by you.]

::''Sample language:'' “All Content you supply must be appropriately marked with licensing (or other permission status) and attribution information.”

For the upload of third party CC-licensed content:

:'''Consider whether marking will be effective.''' If you allow upload of CC-licensed content owned by someone other than the uploader, you should consider whether it will be easy for users of the site to determine what content is available under what license. In some cases, such as with photos or other media, it is simple to mark specific content with licensing information, so there is no need to limit the type of CC-licensed content that is uploaded. In others cases, such as with textual content, it may be prudent to limit upload of third party content to content available under the exact CC license (or at least a compatible license) to that used on contributor content. For example, if you require BY-SA for contributor content, then you could allow upload of third party content only if it is licensed under BY or BY-SA.

::''Sample language:'' “If Content you do not own is not available under these terms, you must not post it on the Websites, except that you may upload media files that are available under any Creative Commons license or if you are authorized by law to do so, for example, under the fair use doctrine.”

:'''Do not ask for a sublicense.''' Importantly, CC licenses don't give licensees the right to grant a sublicense directly to others without the permission of the licensor. This means uploaders of third party CC-licensed content would not be granting you (or the public) any rights directly. Therefore, enabling upload of third party CC-licensed content requires that the TOS not require a direct license to the content from the uploader.

::''Sample language:'' “For Content you post on the Websites that is not owned by you, you agree that all such Content must be available under the Creative Commons Attribution 4.0 International license, or be in the public domain (such as Content that is not copyrightable or Content made available under CC0).”

'''Note and Disclaimer: Creative Commons is not a law firm. CC does not provide legal advice. Any information provided or linked to here is for general informational purposes only, and must not be relied upon as legal advice. You should consult your own lawyer if you need legal advice.'''

Making TOS Work With CC

2014-04-18T22:19:00Z

LuisVilla: /* 1. content owned by you as platform provider */ - slightly clarify this sentence about reps and warranties

While we try to make CC licensing as simple as possible, the fact remains that copyright is complicated, and there are lots of things to consider when you decide to integrate CC licensing to your website. This page addresses one of the necessary components -- offering guidelines and considerations to help you update your website terms of service to make them work with your use of CC licenses.

===Categories of content===
There are three buckets of content to consider when integrating CC licensing to your site:
# content owned by you, the platform provider;
#content owned by contributors; and
#third party content uploaded by you and your contributors.

CC licensing can be used for any or all of these buckets. For each bucket of content, regardless of whether you use CC licensing, the terms of service should define the universe of applicable content, and address ownership of the content and its applicable licensing terms, and the conditions of upload where relevant.

===1. content owned by you as platform provider===
If you choose to apply a CC license to this category of content, you should --
:*make sure you have [http://wiki.creativecommons.org/Considerations_for_licensors_and_licensees#Clear_rights_needed_to_use_the_material. the rights you need] to license it under a CC license; and

:*remove provisions from the TOS that limit or impose additional conditions on uses the CC license permits. For example, the TOS must not have more burdensome attribution requirements than what is required by the CC license.

:'''Representations & warranties:''' Although the CC license itself does not include any reps or warranties, the license does not prohibit you, as the rights holder, from including reps and warranties about the content in the TOS.

===2. content owned by contributors===
If you want to require contributors to CC-license their content, there are two different approaches --
:*The simplest approach is to insert a provision into the TOS that requires contributors to grant a CC license to their content upon upload to the site. In that scenario, you (the platform provider) get the same rights to use the content under copyright as the public under the CC license.

:*The alternative (and more common) approach is used when a platform provider needs more rights from contributors under copyright than the relevant CC license grants – for example, if the platform provider needs to obtain commercial rights from the author but wants to have uploaders grant a CC license allowing content to be used for noncommercial purposes only. In that case, the TOS should include a separate license to the content from contributors to the platform provider and include the provision requiring contributors to grant a CC license to their content upon upload to the site.

:With either approach:

:'''Representations & warranties''' - You may get reps and warranties from uploaders or ask uploaders to agree to particular terms and conditions via the TOS. For example, the TOS may ask contributors to provide assurances that they own the necessary rights to upload and license the content, or they may require uploaders to agree to be attributed in a particular manner.

::''Sample language:'' "You represent, warrant, and agree that no Content posted or otherwise shared by you on any of the Websites, violates or infringes upon the rights of any third party, including copyright, trademark, privacy, publicity, or other personal or proprietary rights, or contains libelous, defamatory, or otherwise unlawful material."

:'''Automatic upgrade clause:''' Since only the rights holder can apply a license to the content, it is important to obtain permission to use contributor content under '''future versions''' of the relevant CC license at the time of upload.

::''Sample language:'' “You hereby agree that all Content you own and voluntarily post on the Websites may be used under the terms of the Creative Commons Attribution 4.0 International license or any later version of a Creative Commons Attribution International License.”

===3. third party content (i.e. content owned by someone other than the uploader)===

There are several types of third party content that can be allowed for upload via TOS:
*content that the uploader has permission to upload (including CC-licensed content),
*content that falls outside of copyright (i.e. is in the public domain), and
*content that the uploader has the right to upload because of an exception or limitation to copyright (e.g., fair use).

Each category carries with it a different level of risk and related considerations. For each category:

:'''Require clear marking.''' If you allow upload of third party content, the TOS should require uploaders to mark the content appropriately so that users of the website can discern the relevant copyright status and attribution information. [Note that appropriate marking is also important for third party content uploaded by you.]

::''Sample language:'' “All Content you supply must be appropriately marked with licensing (or other permission status) and attribution information.”

For the upload of third party CC-licensed content:

:'''Consider whether marking will be effective.''' If you allow upload of CC-licensed content owned by someone other than the uploader, you should consider whether it will be easy for users of the site to determine what content is available under what license. In some cases, such as with photos or other media, it is simple to mark specific content with licensing information, so there is no need to limit the type of CC-licensed content that is uploaded. In others cases, such as with textual content, it may be prudent to limit upload of third party content to content available under the exact CC license (or at least a compatible license) to that used on contributor content. For example, if you require BY-SA for contributor content, then you could allow upload of third party content only if it is licensed under BY or BY-SA.

::''Sample language:'' “If Content you do not own is not available under these terms, you must not post it on the Websites, except that you may upload media files that are available under any Creative Commons license or if you are authorized by law to do so, for example, under the fair use doctrine.”

:'''Do not ask for a sublicense.''' Importantly, CC licenses don't give licensees the right to grant a sublicense directly to others without the permission of the licensor. This means uploaders of third party CC-licensed content would not be granting you (or the public) any rights directly. Therefore, enabling upload of third party CC-licensed content requires that the TOS not require a direct license to the content from the uploader.

::''Sample language:'' “For Content you post on the Websites that is not owned by you, you agree that all such Content must be available under the Creative Commons Attribution 4.0 International license, or be in the public domain (such as Content that is not copyrightable or Content made available under CC0).”

'''Note and Disclaimer: Creative Commons is not a law firm. CC does not provide legal advice. Any information provided or linked to here is for general informational purposes only, and must not be relied upon as legal advice. You should consult your own lawyer if you need legal advice.'''

Marking your work with a CC license

2013-10-17T02:19:05Z

LuisVilla: /* Marking third-party content in your work */ - remove spam

==Best Practices for Marking Content with CC Licenses: Creators ==

<div style="padding: 2%;margin:0em 0em 1em 0em; border:1px dotted red; background:#eee; width:60%">
NOTE: This page is for creators and copyright owners who are looking to CC license their own work. If you are looking for the best way to mark CC-licensed work as a user, see http://wiki.creativecommons.org/Marking/Users. If you own a content-sharing site or platform that hosts works by other creators and are interested in enabling CC licensing for your users, see http://wiki.creativecommons.org/Web_Integration.
</div>

As a creator using a CC license, it is important to properly note the license you have chosen so that others know what they can and can't do with your work. No matter what the context, CC licenses should be clearly cited to enable their full potential as a legal tool.

==Marking on Your Site==
Our [http://creativecommons.org/choose/ license chooser] is designed to make this process simple - answer a few questions and a formatted HTML code will be generated for you:

# Insert this HTML code into your webpage so that your work is clearly marked.
# This HTML code includes [http://wiki.creativecommons.org/Rdfa RDFa], a very important aspect of marking your work so that others can find it easily.

The specifics of inserting the code depend on how you edit your website. The block of code should be inserted into the page HTML - most desktop website tools like Dreamweaver, Frontpage, or GoLive offer a "code view" that lets you see the code that makes up your page. Near the end of the page before you see </body></html>, paste the HTML code in directly.

If all of the resources you are publishing on a single website are licensed under the same CC license, it makes sense to paste the HTML code into your website’s template (e.g., in a footer or sidebar area). After saving the template, the chosen license information should appear everywhere on your site. Whether you add license information to a single page or an entire [http://contactspro.net/purple-contacts/ site], once live on the Internet, the license information will be displayed and the machines will be able to detect the license status automatically.

From there, here are three steps to license notice perfection:

# The full URI (link) to the license. Example: http://creativecommons.org/licenses/by/3.0/us/.
# A visible notation (most commonly text) that states the license being used. Example: Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution 3.0 License.
# Optionally, the appropriate Creative Commons license button or CC icon and license property icon(s).

{| cellspacing="5" cellpadding="10" style="padding: 2%;margin:0em 0em 1em 0em; border:1px dotted red; background:#eee; width:100%"
|
NOTE: Because each CC license represents a different set of permissions and restrictions, it is important to note the specific license used. Displaying only the CC icon, “Creative Commons”, or “Some Rights Reserved” is insufficient; always include the full URL.
|}
In order for others to credit you for your work, it is preferable to provide an attribution name and URI. The [http://creativecommons.org/choose/ license chooser] provides the proper license button (if you fill in attribution fields) as well as RDFa attribution data. Alternatively, high resolution buttons and license icons are available from [http://creativecommons.org/about/downloads our logo download page].

For example, see the following screenshot of a license notification that incorporates these best practices:

[[Image:By_small.jpg]]
<br/><small>This work by [http://opencontent.org/blog David Wiley] is licensed under a [http://creativecommons.org/licenses/by/3.0/us/ Creative Commons Attribution 3.0 United States].</small>

If you visit David's [http://opencontent.org/blog/ blog], you will see this notice at the bottom of the page. The license icon links to the license deed that includes attribution information specific to David. In this case, David filled out the attribution fields in the [http://creativecommons.org/choose/ license chooser], which provided the proper license button and formatted attribution information. He then pasted the resulting HTML code with RDFa into his webpage and included the textual notation of attribution and the specific license that you see above.

Still confused? Take a look at our visual guide. See [[Website/Publish]] for step by step visuals of copying and pasting the HTML code. This page also contains the same information for pages that host a specific type of media ([[Publish/Audio|audio]], [[Publish/Video|video]], [[Publish/Images|images]], and [[Publish/Text|text]] -- which includes various [[Publish/Text#Blog|blogging]] platforms).

If your work is a derivative of another original CC-licensed work, be sure to look at our [http://wiki.creativecommons.org/Marking/Users Marking for Users] primer as well.

== Marking Specific Media ==

While remaining similar in intent, marking will vary depending on the medium. The following are some helpful tips on making sure your media is marked correctly.

For offline works in general, consider publishing a web page with licensing information about your material. Doing so enables your work to be found by search engines and other web discovery tools.

Below are general examples for each medium. If a more technical explanation is your goal, please see [http://wiki.creativecommons.org/Marking_works Marking Works (technical)]:

<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
{{PageColumn|
===Offline Text===
<small>(for online text see [[Marking/Creators#Marking_on_Your_Site|Marking on Your Site]])</small>
*For documents that are meant to be shared in print format (not read online) it is suggested to use a title and/or copyright page to include the Copyright notice and CC license information.
**After going through the [http://creativecommons.org/choose/ license chooser], you can click on "Mark a document not on the web, add this text to your work" in the lower right column.
**And/or you can refer to this sample copyright notice: "Copyright (c) 2009 by Greg Grossmeier. This work is made available under the terms of the Creative Commons Attribution-ShareAlike 3.0 license, http://creativecommons.org/licenses/by-sa/3.0/."
*It is also suggested that you use a visual license notice. Here is a collection of visual markers that can be used:
**[[CC markers]] and [http://creativecommons.org/about/downloads/ official CC license icons]
**[[User submitted markers]]
* [[Publish/Text | Advanced Instructions: Text]]

===Image===
*Adding a watermark or other visual marker on an image can ultimately detract from the original. If you choose to, a safe method of indicating license choice consists of two actions:
**When publishing the image on a website, make sure that your license choice is clearly visible, preferably indicated with one of our [http://creativecommons.org/about/downloads/ license icons].
**Ensure search engines can see it also via the use of [[RDFa]], which you can copy and paste from the HTML code given to you by the [http://creativecommons.org/choose/ license chooser].
*Additionally, you can ensure that the image has [[XMP]] metadata support with your name, date, and license choice.
*[[Publish/Image| Advanced Instructions: Image]]
}}
{{PageColumn|
===Audio===
*For audio files, two actions are recommended:
**When publishing the audio file on a website, make sure that your license choice is clearly visible, preferably using one of our [http://creativecommons.org/about/downloads/ license icons].
**Ensure search engines can find it via the use of [[RDFa]], which you can copy and paste from the HTML code provided by the [http://creativecommons.org/choose/ license chooser].
*Additionally, you may want to ensure that the audio file has metadata support with your name, date, and license choice.
**One easy way to do this is to upload your file to music sharing site that has enabled CC licensing. See [[Marking/Creators#Marking on Other Sites|Marking on Other Sites]] below.
**Alternatively, you can use your favorite audio player to add in the information. To learn more see [[Embedded_Metadata]]. You can also see how to add ID3 tags to a common audio file type, such as the [[MP3]], or browse other [[UsingMarkup|file types]].
*Also, if it is practical to do so (for podcasts, for instance, not song tracks), add an audio bumper to the beginning of the file to indicate your choice of license. Here are some [http://creativecommons.org/podcasting intro bumpers] which you can use to build upon.
*[[Publish/Audio| Advanced Instructions: Audio]]

===Video===
*For movie formats that have the ability to include a 2-5 second copyright frame, it is advisable to use the same format as what is suggested for textual works:
**Sample Copyright notice: Copyright (c) 2009 by Greg Grossmeier. This work is made available under the terms of the Creative Commons Attribution-ShareAlike 3.0 license, http://creativecommons.org/licenses/by-sa/3.0/.
*Here is a collection of stills which can be used as license bumpers:
**[http://wiki.creativecommons.org/CC_video_bumpers Official CC bumpers]
**[http://wiki.creativecommons.org/User_submitted_bumpers Community Submitted bumpers]
*[[Publish/Video| Advanced Instructions: Video]]
}}
</div>

== Marking Specific Formats ==
* CC-[[OpenOfficeOrg Addin]] for [http://openoffice.org OpenOffice].
* To mark a Microsoft Office word document, you can use the Microsoft Office add-ins for [http://www.microsoft.com/downloads/details.aspx?familyid=113b53dd-1cc0-4fbe-9e1d-b91d07c76504&displaylang=en Office 2003/XP] or [http://www.microsoft.com/downloads/details.aspx?FamilyID=d1ddbdc8-627f-415a-9b0a-97362bc9b480&displaylang=en Office 2007]

== Marking on Other Sites ==

===[[Publish]]===

One way to increase visibility and access to your work is to share it with an existing community. Many content platforms have already enabled CC licensing, making it easy for you to indicate the license along with other information, such as who to attribute. In addition, search engines like Google and Yahoo! will index your work as CC licensed if the [[metadata]] is properly attached.

[[Publish]] your work in an existing community.

== Marking third-party content in your work ==
Marking best practices also apply for any third party content your work incorporates. If you are incorporating another person's work, even if used under fair use or other exception or limitation to copyright, then you should be sure you are allowed to incorporate that work. Third party content may be offered under the same or different terms, such as other CC licenses or "all-rights-reserved" copyright. If you are permitted to use the work and it is offered under a CC license, then you should consider adhering to best practices for marking that content as a user, available at [[Marking/Users]]. We also offer additional explanation and tips on [[Marking/Creators/Marking_third_party_content|marking third-party content]]. Note that for all third party material accompanying or used with your CC-licensed work, that material is not covered by the terms and conditions of the CC license that '''''you''''' apply, it remains under the terms of the license (if any) that applies to it.

== External Links ==

*[http://creativecommons.org.au/marking/examples Marking Examples] explaining metadata from [http://creativecommons.org.au Creative Commons Australia]

== Things to note ==
When marking your work, remember that any restriction or modification to the original license cannot be labeled a 'Creative Commons’ license. See http://creativecommons.org/policies#license.

{{Best Practice}}

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]

4.0/Technical protection measures

2012-01-25T04:01:37Z

LuisVilla:

{{4.0 Issue}}

Since Version 1.0, the CC licenses have contained language prohibiting imposition of TPMs on CC-licensed works. The current language in [https://creativecommons.org/licenses/by-sa/3.0/legalcode CC BY-SA 3.0 4(a)] is the following:
:::You may not impose any effective technological measures on the Work that restrict the ability of a recipient of the Work from You to exercise the rights granted to that recipient under the terms of the License.

(Similar language is in 4(b).)

Within the CC and libre licensing communities, this language has been controversial for a long time, in part because it potentially (and paradoxically, given the clause's purpose) limits users' freedoms and complicates use of CC-licensed material in widely used platforms that have TPMs built in.

Outside of the CC and libre licensing communities, awareness of this clause may be minimal. Reasons for this apparently include the choice not to mention this language in the license chooser and human-readable deeds.

One potential solution (the addition of a "parallel distribution" requirement) was extensively discussed, but rejected, for 3.0. For extensive review of the discussion which led up to that rejection, see [[Version 3#DRM]].

Since the creation of the original CC TPM language, TPMs have become more commonplace. For example:

* Several popular game and media distribution platforms, such as the PlayStation and most modern digital TVs (via HDMI/[http://en.wikipedia.org/wiki/High-bandwidth_Digital_Content_Protection HDCP]), require TPMs.

* Apple's iOS App Store app distribution platform uses the combination of FairPlay TPM (and perhaps other measures) to control use of iOS apps. This limitation may constitute an effective technological measure on the content stored within iOS apps, so distribution of CC-licensed materials via the App Store may constitute a violation of the license. Further research on this issue would be welcome; in particular, it would be good to understand under what conditions (if ever), and to what extent, FairPlay or other TPMs in iOS "restrict the ability of a recipient ... to exercise the rights granted" by the CC licenses. A potential starting point for such research, describing various security mechanisms in iOS, including FairPlay and on-disk encryption, may be found [http://trailofbits.files.wordpress.com/2011/08/ios-security-evaluation.pdf here].

* All Japanese terrestrial broadcasting is protected by a TPM. As a result, CC Japan receives inquiries about use of CC-licensed materials in Japanese TV at least monthly, if not more frequently. CC Japan's answers to this question include the point that "you cannot use the image without creating adaptation, (or find a way not to impose TPM for the segment)." When the image is CC-BY-ND, it is impossible to comply with the current language and broadcast CC materials over terrestrial TV in Japan. Friends of CC have heard from an industry source that not imposing a TPM on a particular Japanese terrestrial broadcast is technically possible, but practically impossible. This conflict between the anti-TPM clause and digital TV was raised in 2008 Summit's Legal Day. At the time, the problem was expected but somewhat theoretical. Now that all terrestrial TV broadcasting became digital-only for most of Japan, it is real. Some at the time pointed out that TPM would not be sustainable so we could simply wait and the TPM would disappear. That prediction is not right so far.

== Proposals for 4.0 ==
''For ease of reference on discussion lists, please do not alter proposal numbers.''

'''''TPM Proposal No. 1:''''' '''Drop prohibition of effective technical protection measures, and add permission to circumvent, possibly using GPLv3's Sec. 3's well vetted language as closely as possible.'''

After several years of discussion, GPL version 3, Sec. 3 ("Protecting Users' Legal Rights From Anti-Circumvention Law") attempts to allow circumvention of TPMs that either (1) incorporate the GPL-licensed work as part of their functionality or (2) are used to restrict access to the GPL-licensed work. The actual language is as follows:

::: ''No covered work shall be deemed part of an effective technological measure ..."
:::
::: ''When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.''

The GNU project offers an in-depth [https://www.gnu.org/licenses/quick-guide-gplv3.html#neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm explanation of this clause]. FSF-E has a summary of several talks on the subject by Richard Stallman and Eben Moglen, as well as drafts of earlier versions of this language [https://fsfe.org/projects/gplv3/drm-and-gplv3 here].

The first and third portions of the GPL language focus on the use of the licensed work as ''a functional component'' a TPM, rather than application of a TPM ''to'' the licensed work. Since CC-licensed works are unlikely to be a functional component of a TPM, these portions are likely inapplicable to Creative Commons licenses. Eliminating those portions leaves the following language (adjusted for terminology in CC 3.0):

::: When you Distribute a Work, You waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the Work.

'''Pros:'''
* This clause places no new obligations on the distributor, so compliance is easier when compared to a parallel distribution obligation or similar clause that requires a proactive step by the licensee.

'''Cons:'''
* Permitting circumvention is, in practice, not equivalent to ensuring access, because many TPMs may be difficult or illegal to circumvent. (For example, in Japan, such sales, manufacturing, and other acts related to circumvention device are a crime punishable up to 3 years in prison, etc., according to [http://www.cric.or.jp/cric_e/clj/cl8.html#cl7+A120bis Art.120bis of Japanese copyright law].)

Note that a clause of this type could be used in parallel to the existing language; i.e., the license could both prohibit application of TPM and permit circumvention if a TPM was applied.

It is also possible to drop the TPM clause in only some licenses; e.g., it may make sense to make CC-BY a more "pure" "attribution is the only requirement" license by dropping the TPM provision altogether, while keeping the requirement in CC-BY-SA. For more discussion of this, see [http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/006586.html this mailing list thread, among others.]

'''''TPM Proposal No. 2:''''' '''Allow parallel distribution in place of total TPM prohibition.'''

'''Pros:'''
* Allow copying of a digital image under CC-BY into increasingly common TPM-protected distribution channels, such as the Japanese TV programs discussed above.

'''Cons:'''
* It was explicitly rejected during the 3.0 discussion. There were a variety of reasons for this, including negative reception by CC's international affiliate teams. [[Version_3#DRM]] contains extensive review of those discussions.

''Please add other TPM proposals here, and number them sequentially.''

== Related debate ==
''We encourage you to sign up for the license discussion mailing list, where we will be debating this and other 4.0 proposals. HQ will provide links to related email threads from the license discussion mailing list here.''
*DRM proposals for 4.0 are also discussed [[4.0/Games_3d_printing_and_functional_content#DRM_in_BY-SA_but_not_BY| here]].
*[http://lists.ibiblio.org/pipermail/cc-community/2011-December/thread.html#6559 2011-12 discussion on cc-community]
*[http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/subject.html#6582 debate about parallel distribution on cc-licenses]
*[http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/006586.html proposal for removing TPM restriction in BY on cc-licenses]
*[http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/subject.html#6588 summary of DRM issue on cc-licenses]

== Relevant references ==
''Please add citations that ought to inform this 4.0 issue below.''

4.0/Technical protection measures

2012-01-25T03:17:38Z

LuisVilla: Extensive revision, inc. more links to outside sources.

{{4.0 Issue}}

Since Version 1.0, the CC licenses have contained language prohibiting imposition of TPMs on CC-licensed works. The current language in CC BY-SA 3.0 [https://creativecommons.org/licenses/by-sa/3.0/legalcode 4(a)] is the following:
:::You may not impose any effective technological measures on the Work that restrict the ability of a recipient of the Work from You to exercise the rights granted to that recipient under the terms of the License.

(Similar language is in 4(b).)

Within the CC and libre licensing communities, this language has been controversial for a long time, in part because it potentially (and paradoxically, given the clause's purpose) limits users' freedoms and complicates use of CC-licensed material in widely used platforms that have TPMs built in.

Outside of the CC and libre licensing communities, awareness of this clause may be minimal. Reasons for this apparently include the choice not to mention this language in the license chooser and human-readable deeds.

One potential solution (the addition of a "parallel distribution" requirement) was extensively discussed, but rejected, for 3.0. For extensive review of the discussion which led up to that rejection, see [[Version 3#DRM]].

Since the creation of the original CC TPM language, TPMs have become more commonplace. For example:

* Several popular game and media distribution platforms, such as the PlayStation and most modern digital TVs (via HDMI/[http://en.wikipedia.org/wiki/High-bandwidth_Digital_Content_Protection HDCP]), require TPMs.

* Apple's iOS App Store app distribution platform uses the combination of FairPlay TPM (and perhaps other measures) to control use of iOS apps. This limitation may constitute an effective technological measure on the content stored within iOS apps, so distribution of CC-licensed materials via the App Store may constitute a violation of the license. Further research on this issue would be welcome; in particular, it would be good to understand under what conditions (if ever), and to what extent, FairPlay or other TPMs in iOS "restrict the ability of a recipient ... to exercise the rights granted" by the CC licenses. A potential starting point for such research, describing various security mechanisms in iOS, including FairPlay and on-disk encryption, may be found [http://trailofbits.files.wordpress.com/2011/08/ios-security-evaluation.pdf here].

* All Japanese terrestrial broadcasting is protected by a TPM. As a result, CC Japan receives inquiries about use of CC-licensed materials in Japanese TV at least monthly, if not more frequently. CC Japan's answers to this question include the point that "you cannot use the image without creating adaptation, (or find a way not to impose TPM for the segment)." When the image is CC-BY-ND, it is impossible to comply with the current language and broadcast CC materials over terrestrial TV in Japan. Friends of CC have heard from an industry source that not imposing a TPM on a particular Japanese terrestrial broadcast is technically possible, but practically impossible. This conflict between the anti-TPM clause and digital TV was raised in 2008 Summit's Legal Day. At the time, the problem was expected but somewhat theoretical. Now that all terrestrial TV broadcasting became digital-only for most of Japan, it is real. Some at the time pointed out that TPM would not be sustainable so we could simply wait and the TPM would disappear. That prediction is not right so far.

== Proposals for 4.0 ==
''For ease of reference on discussion lists, please do not alter proposal numbers.''

'''''TPM Proposal No. 1:''''' '''Drop prohibition of effective technical protection measures, and add permission to circumvent, possibly using GPLv3's Sec. 3's well vetted language as closely as possible.'''

After several years of discussion, GPL version 3, Sec. 3 ("Protecting Users' Legal Rights From Anti-Circumvention Law") attempts to allow circumvention of TPMs that either (1) incorporate the GPL-licensed work as part of their functionality or (2) are used to restrict access to the GPL-licensed work. The actual language is as follows:

::: ''No covered work shall be deemed part of an effective technological measure ..."
:::
::: ''When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.''

The GNU project offers an in-depth [https://www.gnu.org/licenses/quick-guide-gplv3.html#neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm explanation of this clause]. FSF-E has a summary of several talks on the subject by Richard Stallman and Eben Moglen, as well as drafts of earlier versions of this language [https://fsfe.org/projects/gplv3/drm-and-gplv3 here].

The first and third portions of the GPL language focus on the use of the licensed work as ''a functional component'' a TPM, rather than application of a TPM ''to'' the licensed work. Since CC-licensed works are unlikely to be a functional component of a TPM, these portions are likely inapplicable to Creative Commons licenses. Eliminating those portions leaves the following language (adjusted for terminology in CC 3.0):

::: When you Distribute a Work, You waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the Work.

'''Pros:'''
* This clause places no new obligations on the distributor, so compliance is easier when compared to a parallel distribution obligation or similar clause that requires a proactive step by the licensee.

'''Cons:'''
* Permitting circumvention is, in practice, not equivalent to ensuring access, because many TPMs may be difficult or illegal to circumvent. (For example, in Japan, such sales, manufacturing, and other acts related to circumvention device are a crime punishable up to 3 years in prison, etc., according to [http://www.cric.or.jp/cric_e/clj/cl8.html#cl7+A120bis Art.120bis of Japanese copyright law].)

Note that a clause of this type could be used in parallel to the existing language; i.e., the license could both prohibit application of TPM and permit circumvention if a TPM was applied.

It is also possible to drop the TPM clause in only some licenses; e.g., it may make sense to make CC-BY a more "pure" "attribution is the only requirement" license by dropping the TPM provision altogether, while keeping the requirement in CC-BY-SA. For more discussion of this, see [http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/006586.html this mailing list thread, among others.]

'''''TPM Proposal No. 2:''''' '''Allow parallel distribution in place of total TPM prohibition.'''

'''Pros:'''
* Allow copying of a digital image under CC-BY into increasingly common TPM-protected distribution channels, such as the Japanese TV programs discussed above.

'''Cons:'''
* It was explicitly rejected during the 3.0 discussion. There were a variety of reasons for this, including negative reception by CC's international affiliate teams. [[Version_3#DRM]] contains extensive review of those discussions.

''Please add other TPM proposals here, and number them sequentially.''

== Related debate ==
''We encourage you to sign up for the license discussion mailing list, where we will be debating this and other 4.0 proposals. HQ will provide links to related email threads from the license discussion mailing list here.''
*DRM proposals for 4.0 are also discussed [[4.0/Games_3d_printing_and_functional_content#DRM_in_BY-SA_but_not_BY| here]].
*[http://lists.ibiblio.org/pipermail/cc-community/2011-December/thread.html#6559 2011-12 discussion on cc-community]
*[http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/subject.html#6582 debate about parallel distribution on cc-licenses]
*[http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/006586.html proposal for removing TPM restriction in BY on cc-licenses]
*[http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/subject.html#6588 summary of DRM issue on cc-licenses]

== Relevant references ==
''Please add citations that ought to inform this 4.0 issue below.''

4.0/Technical protection measures

2012-01-23T22:28:54Z

LuisVilla: /* Proposals for 4.0 */

{{4.0 Issue}}

Since Version 1.0, the CC licenses have contained language prohibiting imposition of TPMs on CC-licensed works. The current language in CC BY-SA 3.0 [https://creativecommons.org/licenses/by-sa/3.0/legalcode 4(a)] and similar in 4(b) is the following:
:::You may not impose any effective technological measures on the Work that restrict the ability of a recipient of the Work from You to exercise the rights granted to that recipient under the terms of the License.

This has been controversial for a long time, potentially unnecessarily (and paradoxically, given anti-DRM clause meant to protect) limiting users' freedoms and complicating use of CC-licensed material in widely used platforms that have DRM built in.

One potential solution (the addition of a "parallel distribution" requirement) was extensively discussed, but rejected, for [[Version 3#DRM]].

Since the creation of the original CC TPM language, TPMs have become more commonplace. For example:

* All Japanese terrestrial broadcasting is protected by a TPM. As a result, CC Japan receives inquiries about use of CC-licensed materials in Japanese TV at least monthly, if not more frequently. CC Japan's answers to this question include the point that "you cannot use the image without creating adaptation, (or find a way not to impose TPM for the segment)." When the image is CC-BY-ND, it is impossible to comply with the current language and broadcast CC materials over terrestrial TV in Japan. Friends of CC have heard from an industry source that not imposing a TPM on a particular Japanese terrestrial broadcast is technically possible, but practically impossible. This conflict between the anti-TPM clause and digital TV was raised in 2008 Summit's Legal Day. At the time, the problem was expected but somewhat theoretical. Now that all terrestrial TV broadcasting became digital-only for most of Japan, it is real. Some at the time pointed out that TPM would not be sustainable so we could simply wait and the TPM would disappear. That prediction is not right so far.

* Several popular game and media distribution platforms, such as the PlayStation, require TPMs.

* It has been argued that the combination of iOS, iOS applications, and the App Store constitute an effective technological measure, so distribution of CC-licensed materials to iPhones and iPads may constitute a violation of the license. (Further research needs to be conducted on this point, and to confirm that this is the case.)

== Proposals for 4.0 ==
''For ease of reference on discussion lists, please do not alter proposal numbers.''

'''''TPM Proposal No. 1:''''' '''Drop prohibition of effective technical protection measures, add permission to circumvent, possibly using GPLv3's Sec. 3's well vetted language as closely as possible.'''

After several years of discussion, GPL version 3, Sec. 3 ("Protecting Users' Legal Rights From Anti-Circumvention Law") attempts to allow circumvention of TPMs that either (1) incorporate the GPL-licensed work as part of their functionality or (2) are used to restrict access to the GPL-licensed work. The actual language is as follows:

::: ''No covered work shall be deemed part of an effective technological measure ..."
:::
::: ''When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.''

The GNU project offers an in-depth [https://www.gnu.org/licenses/quick-guide-gplv3.html#neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm explanation]. FSF-E has a summary of several talks on the subject by Richard Stallman and Eben Moglen, as well as drafts of earlier versions of this language [https://fsfe.org/projects/gplv3/drm-and-gplv3 here].

Because CC has historically focused on expressive works (i.e., "content") rather than functional works (i.e., software), it may make sense to ignore the portions of the GPL language that focuses on whether or not the work is used as part of a TPM. This would leave the following language (adjusted for terminology in CC 3.0):

::: When you Distribute a Work, You waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the Work.

'''Pros:'''
* This clause places no new obligations on the distributor, so compliance is easier when compared to a parallel distribution obligation or similar clause that requires a proactive step by the licensee.

'''Cons:'''
* Permitting circumvention is, in practice, not equivalent to ensuring access, because many TPMs may be difficult or illegal to circumvent. (For example, in Japan, such sales, manufacturing, and other acts related to circumvention device are a crime punishable up to 3 years in prison, etc., according to [http://www.cric.or.jp/cric_e/clj/cl8.html#cl7+A120bis Art.120bis] of Japanese copyright law).

Note that a clause of this type could be used in parallel to the existing language; i.e., the license could both prohibit application of TPM and permit circumvention if a TPM was applied.

'''''TPM Proposal No. 2:''''' '''Allow parallel distribution in place of total TPM prohibition.'''
'''Pros:'''
* Allow copying of a digital image under CC-BY into increasingly common TPM-protected distribution channels, such as the Japanese TV programs discussed above.

'''Cons:'''
* It was explicitly rejected during the 3.0 discussion. There were a variety of reasons for this, including negative reception by CC's affiliate teams around the world. [[Version_3#DRM]] contains extensive review of those discussions.

''Please add other TPM proposals here, and number them sequentially.''

== Related debate ==
''We encourage you to sign up for the license discussion mailing list, where we will be debating this and other 4.0 proposals. HQ will provide links to related email threads from the license discussion mailing list here.''
*DRM proposals for 4.0 are also discussed [[4.0/Games_3d_printing_and_functional_content#DRM_in_BY-SA_but_not_BY| here]].
*[http://lists.ibiblio.org/pipermail/cc-community/2011-December/thread.html#6559 2011-12 discussion on cc-community]
*[http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/subject.html#6582 debate about parallel distribution on cc-licenses]
*[http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/006586.html proposal for removing TPM restriction in BY on cc-licenses]
*[http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/subject.html#6588 summary of DRM issue on cc-licenses]

== Relevant references ==
''Please add citations that ought to inform this 4.0 issue below.''

4.0/Technical protection measures

2012-01-23T22:27:59Z

LuisVilla: Reorganize and simplify.Very little new content (mostly better-explaining the GPL references), but entire page is reorganized.

{{4.0 Issue}}

Since Version 1.0, the CC licenses have contained language prohibiting imposition of TPMs on CC-licensed works. The current language in CC BY-SA 3.0 [https://creativecommons.org/licenses/by-sa/3.0/legalcode 4(a)] and similar in 4(b) is the following:
:::You may not impose any effective technological measures on the Work that restrict the ability of a recipient of the Work from You to exercise the rights granted to that recipient under the terms of the License.

This has been controversial for a long time, potentially unnecessarily (and paradoxically, given anti-DRM clause meant to protect) limiting users' freedoms and complicating use of CC-licensed material in widely used platforms that have DRM built in.

One potential solution (the addition of a "parallel distribution" requirement) was extensively discussed, but rejected, for [[Version 3#DRM]].

Since the creation of the original CC TPM language, TPMs have become more commonplace. For example:

* All Japanese terrestrial broadcasting is protected by a TPM. As a result, CC Japan receives inquiries about use of CC-licensed materials in Japanese TV at least monthly, if not more frequently. CC Japan's answers to this question include the point that "you cannot use the image without creating adaptation, (or find a way not to impose TPM for the segment)." When the image is CC-BY-ND, it is impossible to comply with the current language and broadcast CC materials over terrestrial TV in Japan. Friends of CC have heard from an industry source that not imposing a TPM on a particular Japanese terrestrial broadcast is technically possible, but practically impossible. This conflict between the anti-TPM clause and digital TV was raised in 2008 Summit's Legal Day. At the time, the problem was expected but somewhat theoretical. Now that all terrestrial TV broadcasting became digital-only for most of Japan, it is real. Some at the time pointed out that TPM would not be sustainable so we could simply wait and the TPM would disappear. That prediction is not right so far.

* Several popular game and media distribution platforms, such as the PlayStation, require TPMs.

* It has been argued that the combination of iOS, iOS applications, and the App Store constitute an effective technological measure, so distribution of CC-licensed materials to iPhones and iPads may constitute a violation of the license. (Further research needs to be conducted on this point, and to confirm that this is the case.)

== Proposals for 4.0 ==
''For ease of reference on discussion lists, please do not alter proposal numbers.''

'''''TPM Proposal No. 1:''''' '''Drop prohibition of effective technical protection measures, add permission to circumvent, possibly using GPLv3's Sec. 3's well vetted language as closely as possible.'''

After several years of discussion, GPL version 3, Sec. 3 ("Protecting Users' Legal Rights From Anti-Circumvention Law") attempts to allow circumvention of TPMs that either (1) incorporate the GPL-licensed work as part of their functionality or (2) are used to restrict access to the GPL-licensed work. The actual language is as follows:

::: ''No covered work shall be deemed part of an effective technological measure ..."
:::
::: ''When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.''

The GNU project offers an in-depth [https://www.gnu.org/licenses/quick-guide-gplv3.html#neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm explanation]. FSF-E has a summary of several talks on the subject by Richard Stallman and Eben Moglen, as well as drafts of earlier versions of this language [https://fsfe.org/projects/gplv3/drm-and-gplv3 here].

Because CC has historically focused on expressive works (i.e., "content") rather than functional works (i.e., software), it may make sense to ignore the portions of the GPL language that focuses on whether or not the work is used as part of a TPM. This would leave the following language (adjusted for terminology in CC 3.0):

::: When you Distribute a Work, You waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the Work.

'''Pros:'''
* This clause places no new obligations on the distributor, so compliance is easier when compared to a parallel distribution obligation or similar clause that requires a proactive step by the licensor.

'''Cons:'''
* Permitting circumvention is, in practice, not equivalent to ensuring access, because many TPMs may be difficult or illegal to circumvent. (For example, in Japan, such sales, manufacturing, and other acts related to circumvention device are a crime punishable up to 3 years in prison, etc., according to [http://www.cric.or.jp/cric_e/clj/cl8.html#cl7+A120bis Art.120bis] of Japanese copyright law).

Note that a clause of this type could be used in parallel to the existing language; i.e., the license could both prohibit application of TPM and permit circumvention if a TPM was applied.

'''''TPM Proposal No. 2:''''' '''Allow parallel distribution in place of total TPM prohibition.'''
'''Pros:'''
* Allow copying of a digital image under CC-BY into increasingly common TPM-protected distribution channels, such as the Japanese TV programs discussed above.

'''Cons:'''
* It was explicitly rejected during the 3.0 discussion. There were a variety of reasons for this, including negative reception by CC's affiliate teams around the world. [[Version_3#DRM]] contains extensive review of those discussions.

''Please add other TPM proposals here, and number them sequentially.''

== Related debate ==
''We encourage you to sign up for the license discussion mailing list, where we will be debating this and other 4.0 proposals. HQ will provide links to related email threads from the license discussion mailing list here.''
*DRM proposals for 4.0 are also discussed [[4.0/Games_3d_printing_and_functional_content#DRM_in_BY-SA_but_not_BY| here]].
*[http://lists.ibiblio.org/pipermail/cc-community/2011-December/thread.html#6559 2011-12 discussion on cc-community]
*[http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/subject.html#6582 debate about parallel distribution on cc-licenses]
*[http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/006586.html proposal for removing TPM restriction in BY on cc-licenses]
*[http://lists.ibiblio.org/pipermail/cc-licenses/2012-January/subject.html#6588 summary of DRM issue on cc-licenses]

== Relevant references ==
''Please add citations that ought to inform this 4.0 issue below.''

LiveContent

2007-07-20T13:07:54Z

LuisVilla: /* proposed additions/deletions to applications */

[[Category:Technology]]
[[Category:Developer Challenges]]
[[Category:Developer]]
[[Category:freesoftware]]
[[Category:opensource]]
[[Category:ccLiveCD]]
[[Category:LiveContent]]

LiveContent is an umbrella idea which aims to connect and expand Creative Commons and open source communities. LiveContent works to identify creators and content providers working to share their creations more easily with others. LiveContent works to support developers and others who build better technology to distribute these works. LiveContent is up-to-the-minute creativity, "alive" by being licensed Creative Commons, which allows others to better interact with the content.

LiveContent can be delivered in a variety of ways. The first incarnation of LiveContent will deliver content as a LiveCD. LiveCDs are equivalent to what is called a [http://en.wikipedia.org/wiki/LiveDistro LiveDistro]. LiveCDs have traditionally been a vehicle to test an operating system or applications live. Operating systems and/or applications are directly booted from a CD or other type of media without needing to install the actual software on a machine. LiveContent aims to add value to LiveDistros by providing dynamically-generated content that can be added

== Contribute! ==

Creative Commons encourages others to provide ideas, feedback, comments and connections to other projects on this wiki page. There are many ways to contribute:

#Sign up for an account on this wiki and begin adding to the community - your knowledge, ideas and contributions are welcome
#IRC - Channel #CC at http://irc.freenode.net - general chatter from CC-ers, affiliates, guests - http://wiki.creativecommons.org/IRC
#cc-devel listserv - Creative Commons developers email list - http://wiki.creativecommons.org/Mailing_Lists

==Roadmap==

=== June 11===
* Brainstorming "best-of" CC-licensed content to include with the LiveCD
* Connect with other organizations - ALA, LITA, FOSS
* blog post about the project

===June 18===
* (DONE) talk to scott about helping us with builds with the correct sizing
* trying out different spins (tvol)
* bug jon to get test computer (tvol)

===June 25===
* figure out packaging of physical CD (cardboard insert/cd burns/how many/how long it will take to get manufactured/how much) (tvol + alex))
** (DONE) need to schedule meeting with alex for this week (Monday)
** Explaining CC on the packaging
* make public web page requirements on the wiki (tvol)
** (live.creativecommons.org or creativecommons.org/livecontent or creativecommons.org/live ... maybe for now just redirect to wiki page) (tvol)
** NOTECH: just clean up this wiki page (tvol)
* get the automated fedora build system working! (tannewt)

===July 2===
* Have daily builds running on redhat infrastructure (tannewt)
* planning what docs we need to collect for documentation for Fedora, apps, CC-licenses (tvol)
**pull from documentation on sites--don't reinvent the wheel, utilize wikis, but try to distill important info, especially for new users
**we want the most of these to be present as documentation within the cd, not in print
* conceptualize how to have auto-curated packages (pick one package in each media) (tannewt/tvol) - LiveContent takes off
** what are the top [[Content_Curators|Content Curators]] to have, one each for audio, video, image, and text, education. (tvol)
** develop icons for each of these categories? (alex?)

===July 9===
* have basic liveCD build completed (tannewt)

===July 16===

* Have all top auto-curated packages building on redhat infrastructure (tannewt)
* Test out auto-curated packages and communicate with tannewt (tvol)

===July 23===
* (HIGH PRIORITY) Send off CD for printing early week
*build up steam for the release
*library distribution options
**how many will get sent out?
**which libraries?

===July 30===
*press release about the project -work with worldlabel, redhat

===August 6===
*LiveCD rollout at Linuxworld - San Francisco

===August 8th===
*LiveCD rollout CC Salon - San Francisco

== Formats for distribution of LiveContent==

=== USB ===
The LiveContent could also be made to fit onto a usb stick so that it can be plugged into computers and boot straight into Linux and/or have Creative Commons licensed content on this thumbdrive.

=== DVD ===
The Free Me project has already produced a [http://questionsplease.org/freeme live DVD] with almost exactly the same ideas behind it. More than willing to lend a hand with this :D. Contact me at [mailto:jonathan.roberts.uk@googlemail.com] if you think I could be of use.

=== CD ===
We're currently working on creating an ISO image for a bootable system that would be filled with free open source software (FOSS) and CC-licensed content. Creative Commons will team with [http://fedoraproject.org Fedora] (technical support) and [http://www.worldlabel.com/ Worldlabel.com] (development and distribution support) in order to produce a LiveCD.

==ccLiveContent v1.0 - testing feedback==

*Please help CC make LiveContent the best it can be! Provide feedback under the following categories, or create your own!

===interface===
* desktop icons look like part of the background- they should somehow be raised or otherwise be made to look like an icon, rather than part of the background.
* not clear that using two desktops makes sense; just one more thing for people to click on and be confused by. Make it only one desktop by default, and remove the applet from the panel.
* make CC the default search in FF.
* if there is a global CC ical file, the calendar should be subscribed to it so that it shows up in the calendar in the panel clock.
* folders that are 'bookmarked' show up in the 'Places' menus; would be good to bookmark the various Audio/Video/etc. folders, I think.
* nautilus thumbnails certain media types. The thumbnails should be pre-generated so that there isn't excessive drive access and clock icons when people open the folders for the first time. (They are in .thumbnails, I believe.)
* nautilus can put icons on individual files. I suggest that perhaps nautilus should include icons representing the licenses, and then each media/content file can have the license represented as an icon on the file. (Either as a supplement to, or a replacement for, the ugly license.txt file. The license.txt can be hidden with by placing it in .hidden, as in http://svn.gnome.org/viewcvs/livecd-project/trunk/locales/en_US/home/Desktop/Images%20from%20GNOME%20community%20events/.hidden?view=markup)
* nautilus can reorder and remember the order of files; would be good to order the content directories something like content / web links / license.txt. (That information is stored in ~/.nautilus/metafiles/ if you need to back it up.)
* the pictures should be titled with names/author ('foo by Steve Bar.jpg'), instead of 1.jpg, 2.jpg, etc.
* web icons should have the globe replaced with the sites favico or something like it. (There is a way to do this, but I admit I don't recall what it is.)

===content (audio/video/image/text/education)===

* no Free Culture in Texts? :)
* in Education, probably a link to Curriki would be good. Ditto perhaps http://www.introecon.com/ ?
* perhaps the various CC comics, both http://www.law.duke.edu/cspd/comics/ and http://creativecommons.org/about/licenses/comics1/ ? Not sure where those would go.

===proposed additions/deletions to applications===
* would remove DOM Inspector plugin from FF, and add the MozCC plugin.
* why OpenOffice? Abiword and Gnumeric fit onto a liveCD much, much better- could fit another several dozen megs of content, at least, if you made that swap. (I seem to recall the difference was over 100 megs when I was working on the old GNOME liveCDs.)
* I'd remove gnome-terminal, at least from the final build. No need to have it clutter up the iso or the menus for this target audience.
* the screensaver should be turned on, and set by default to use the pictures in the Images directory.

===bugs===

*wireless is not supported on all machines [not fixable by CC]
*system time is incorrect [system does not know the timezone, so never going to know it correctly. Perhaps remove the clock altogether?]
*is there printing support?

===comments/questions===

==ccLiveContent v2.0 - Libraries==

=== Rationale ===

We believe that the LiveContent CD can be a gateway distribution device to test the waters of using free open source software within library settings. It will also help to spread the message about Creative Commons and provide examples of different media that has been licensed under Creative Commons. We wish to promote network effects for open source in general - get more people involved with supporting FOSS, CC.

=== Target ===

Our first LiveContent CD will be created for librarians to test for public terminals at libraries. The object is to get as many libraries to install Free and Open Source Software (FOSS) on their current systems. We will be aiming the implementation at librarians and library administrators.

We strongly believe that libraries are a great way to plant seeds in the community to help the FOSS movement expand. This project will help bring more awareness to open source by providing an example of an operating system and free open source applications that could be implemented on library patron terminals. If the ideas can catch on, the long-range effects might be that libraries would begin to implement free open source software on machines permanently, thus providing a wealth of benefits both to patrons in terms of a more free computing environment and severing the long-standing ties between libraries and proprietary software license fees.

At this time, it seems that CDs provide the best media format that is accessible to most library computer terminals.

=== potential benefits ===

*libraries
**save money on proprietary software licensing - total cost of ownership (tco) is less
**libraries can be seen as cutting edge in adoption of open source
**more control over computing environment
**can test on machines without installing
**can also install directly from a desktop image
**most productivity and creativity applications have a free open source counterpart
**increase services to user by offering more software

=== potential concerns ===

*public libraries vs academic libraries - public libraries have less resources, less staff time to examine new products and test out - at the same time FOSS might most benefit small public libraries, especially rural
*academic libraries are often equipped for more research, and might be better geared towards having the resources for testing and future development
*what kinds of agreements do libraries have with software providers now, if any?
*make the cds very intuitive, well-labeled, good supporting documentation - fedora has a lot of good documentation, +/- of liveCD
*will we only make spins for i386? - probably the architecture of most library terminal machines, unless some use older macs - ppc
*how do we distribute without spamming?
*will libraries trust what we send to them?
*will libraries notice it or have time to look at it?
*less to do with the software and more to do with presentation and documentation
*focus on low income areas, rural?
*will CC put on material that covers all the different licenses? or least restrictive? - attribution only
*different libraries have different budgets which allow for a vast range in hardware and training
*The mailing will have a mail back questionaire asking did they install software and other general questions. - rethink this idea due to spamming/response issues? - think about other ways to gather feedback
*what about adding the CDs to library collections? - might be a good way for people to install or use at home, but doesn't align too well with the applications and content becoming obsolete
*accessibility
**http://ui.openoffice.org/accessibility/disabilities.html
**http://developer.gnome.org/projects/gap/at-types.html

=== What is the current landscape for library computing? ===

*at San Francisco Public Library (SFPL) main branch, there are two types of computer terminals:
**those that are used solely for card catalog lookup - no other features provided
**those where patrons can access the internet (via internet explorer) and use the Microsoft Office 2003 suite (Word, Excel, Powerpoint) - there are no other applications that are accessible through the tailored, limited-view interface

===Proposed LiveCD Contents ===

==== Fedora 7 ====
Fedora 7 is the Linux operating system that will be running live from the CD. Fedora 7 can be customized by creating "spins." Spins are custom builds of the CD with applications and features that meet the users' needs. A specific spin can be documented by including a "build date" on the CD and its packaging. Any user who has installed Fedora on their machine can spin custom LiveCDs.

Documentation at http://fedoraproject.org/wiki/FedoraLiveCD/

There are differnt ways to create LiveCDs with Fedora:
*Graphical User Interface (GUI) - Revisor (comes loaded in Fedora)
*Command Line Interface (CLI) - livecd-creator (creates liveCDs), [https://hosted.fedoraproject.org/projects/pungi Pungi] (creates installation disks)
*users who wish to contribute to Fedora's internal build system need an account - create account @ http://admin.fedoraproject.org/accounts
*Koji is Fedora's server that tracks recent builds - http://koji.fedoraproject.org
*testing notes:
**fedora 7 LiveCD Gnome runs extremely slow on a 256MB test machine
**note - productivity and creativity apps cannot be installed at terminals without first installing Fedora - aka liveCD doesn't support application installs before full OS install

==== FOSS Productivity/creativity/entertainment apps ====

*[http://www.openoffice.org Openoffice] - Complete version
*[http://www.mozilla.com/en-US/firefox/ FireFox] - web browser
*[http://www.gimp.org/ Gimp] - raster graphics editor
*[http://www.inkscape.org/ Inkscape] - vector graphics editor
*[http://www.worldlabel.com Worldlabel.com] Blank Opendocument Format Label Templates and collection of pre-designed label templates: address, shipping, filing, CD - licensed public domain
*Collection of clipart from [http://www.openclipart.org Open Clip Art Library]?
*Totem - audio and video viewer
*gThum - image viewer
*Evince PDF Viewer. Possible PDF editor, Openoffice has excellent PDF export
*SVG Viewer - Gimp

*For Kids (possible inclusion)
**http://www.linuxforkids.org/
**[http://www.tuxpaint.org/ Tuxpaint]
**[http://gcompris.net/-en- qcompris]
**[http://tuxtype.sourceforge.net Tuxtype]
**[http://www.schooltool.org/ Schooltool]

*A good idea might be to include some promotional information like http://why.openoffice.org/why_nfp.html but also for all the other applications, Why Gimp, Why Inscape, etc.

*note that all these FOSS applications are also available for installation on machines running proprietary operating systems (windows, osx), not just linux machines

==== Creative Commons-licensed content ====
We want to provide examples from each category (audio, video, text, image, education) to showcase on the LiveContent CD. We will develop a system that can automatically pull top content from the sites that we choose (and these sites can change as well).

We'll feature one website/service/cc-content provider from each of the 5 categories for this initial run. We should provide examples of cc-licensed materials from each. don't know how many--we'll see how much room is left on the cd:

*audio - jamendo
**[[Audio#Featured_Audio_Sites|more audio]]
*video - blip.tv
**[[Video#Featured_Video_Sites|more video]]
*image - flickr
**[[Image#Featured_Image_Sites|more image]]
*text - lulu
**[[Text#Featured_Text_sites|more text]]
*education - connexions
**[[Education#Featured_Education_sites|more education]]

*[[Multiple_Formats|even more]]

*what about cc-videos?
*possible inclusion of a CC plugin pre-installed in Openoffice.org
*inclusion of CC plug-in for Firefox?

==== Documentation ====

*http://opendocumentfellowship.org/
*explanation of licenses like from the Free Me DVD - http://questionsplease.org/freeme/free-culture/the-licenses/
*obvious CC explanations - to be displayed in an initial pop-up browser page?
**this should mirror the info we have on the inside of the cd packaging - a redirect to the visual on the website
**http://creativecommons.org/about/licenses/meet-the-licenses
**http://creativecommons.org/about/licenses
* tutorials
**http://www.tutorialsforopenoffice.org/
**http://docs.fedoraproject.org/
**http://www.gimp.org/docs/
**http://www.inkscape.org/doc/index.php

=== Interface and Display Options ===

==== Themeing ====
*Gnome with cc desktop, content icons, share/reuse/remix icons

==== Initial Pop-up Screen ====
This screen will be loaded upon booting the CD to welcome users and give an overview of the LiveCD.

Some things to include:
*what is a LiveCD
*what is on the cd
**pointer to Fedora docs
**pointer to App docs
**pointer to CC docs
*instructions about how to open applications
*how to save
*how to quit?

==== how to access cc content ====
*cc icons on the desktop - utilize icons for the content categories (audio, video, text, image, education)
* digging deeper - how do we provide more examples? - possibly through the inclusion of examples of how users can share/remix/reuse content using cc - users can click on these icons to pull up a webpage that explains more

=== Distribution Options ===

We will investigate options for getting the CDs into the hands of the libraries we wish to target. While we wish to provide a quality LiveContent CD to the most libraries we can, we realize that mass mailing may not be the best way to accomplish this distribution goal, especially since this may be considered a type of spamming. Ideas other than mailing include hosting the contents online and doing outreach to libraries and other interested parties through a widespread press release, listservs, hand out at events, or get an in through professional organizations like the American Library Association.

While we are working towards a deliverable LiveContent CD by August 8, further exploration of a dynamic, automated system should be examined. This type of system could be automated to pull updated content from various sources , current application versions and OS patches and build a CD extremely easily. In this way, users could download the most current build at any time.

During development, we hope to provide preliminary builds and demos that we can send to various organization and libraries so that they can review the LiveContent CD and provide input for further development. Later reviews hopefully will be published in numerous ALA publications. Reviews could be sent with the CD in the mailing so that there is neutral positive influence behind the CD.

==== Resources ====

===== Groups =====

*OCLC
**http://www.oclc.org/default.htm
**http://www.oclc.org/research/staff/default.htm
**http://www.oclc.org/research/software/default.htm
**http://www.oclc.org/research/software/opensource.htm

*American Library Association http://www.ala.org

*Library Information Technology Association (LITA) http://www.lita.org

*Open Source Systems interest group http://www.ala.org/ala/lita/litamembership/litaigs/opensourcesystem/opensourcesystems.cfm

*OpenOffice http://marketing.openoffice.org/ and http://distribution.openoffice.org/

===== People =====

*Jack Aboutboul - Redhat mailto:jaa@redhat.com - Redhat will provide the themeing and customized builds of the CDs containing the OS, open source apps, Worldlabel documentation, CC content

*Jonathan Roberts - Free Me DVD - http://questionsplease.org/freeme/

*Mr. Alex Choong of Innotech Resources Pte Ltd (worldlabel.com.sg) will cover the cost of duplication of master Library CD. 8000 to 10000pcs with jewel box or sleedve. He wants will also implement a program in Singapore and Malaysia to distribute the CD to libraries. He mentioned wanting reference to this in press releases.

*project managers for oo marketing: john mccressh-mailto:jpmcc@openoffice.org, cristin driga-mailto:cdriga@openoffice.org
*Mr. Louis Suarez-Potts (Community Manager): mailto:luispo@gmail.com
*distribution-mailto:cdrom@distribution.openoffice.org

*Simon Spero at Sun in North Carolina, who might be willing to provide server space to maintain a dynamic build system

*John Rutherford of Lita/ALA Chairman of Opensource for Lita - IT division of ALA
**http://www.ala.org/ala/lita/litamembership/litacommittees/roster.cfm?committee=lit-igopens
**mailto:jrutherford @ wayne.edu
**Phone: (313) 577-0367
**will be at ALA conference in Washington DC end of June

*David Bretthauer
**http://www.lita.org/ala/lita/litapublications/ital/2101bretthauer.cfm, can be a big help, especially giving ideas which libraries to target for mailings and other stuff.
**mailto:Dave.Bretthauer@uconn.edu
**Tel: 860-486-6494

*Ms. Carrie Russell mailto:crussell@alawash.org
**Copyright Specialist, ALA, Office for Information Technology Policy

===== Reading =====

*ALA public library funding & technology access study
**http://www.ala.org/ala/ors/publiclibraryfundingtechnologyaccessstudy/pullibfunandtechaccstudy.htm
*public libraries and the internet
**http://www.ii.fsu.edu/plinternet_findings.cfm
*http://www.infomotions.com/musings/ossnlibraries-workshop/ossnlibraries-workshop.html
*http://www.newsforge.com/article.pl?sid=03/12/14/1545216&mode=thread&tid=132&tid=151&tid=82
*http://webjunction.org/do/DisplayContent?id=1216
*Article on Open Source in libaries by Gates Foundation: http://webjunction.org/do/DisplayContent?id=734
*Abstract by Siobhan Stevenson, an assistant professor at the Faculty of Information Studies University of Toronto http://www.firstmonday.org/issues/issue12_5/stevenson/index.html

*information on licensing issues for libraries: - http://www.librarycopyright.net/

===== LiveCD Examples =====

* [http://debian-live.alioth.debian.org/ Debian Live] - Debian LiveCDs
* [http://www.knoppix.org/ KNOPPIX] - Well-known LiveCD
* [http://www.slax.org/ Slax] - Slackware-based LiveCD
* [http://www.ubuntu.com/ Ubuntu] - Popular LiveCD
* [http://questionsplease.org/freeme Free Me] - Live DVD promoting free culture in the same way

===== LiveCD Resources =====

* [http://debian-live.alioth.debian.org/ Debian Live]
* [http://www.frozentech.com/content/livecd.php Live CD List] - Long List of LiveCDs
* [http://www.livedistro.org LiveDistro] - [http://www.livedistro.org/taxonomy/term/378/list Build Tools], [http://www.livedistro.org/taxonomy/term/370/list Howtos], [http://www.livedistro.org/vocabulary/18/list Releases]
* [http://reconstructor.aperantis.com/ Reconstructor] - Remaster Ubuntu LiveCDs
* [http://en.wikipedia.org/wiki/Comparison_of_Linux_LiveDistros Wikipedia Linux LiveDistro Comparison]
* [http://en.wikipedia.org/wiki/LiveCD Wikipedia LiveCD]
* [http://uck.sourceforge.net/ Ubuntu Customization Kit] - Make custom Ubuntu LiveCDs
* [http://revisor.fedoraunity.org/ Revisor] - Graphical tool for creating Fedora Live CDs/DVDs/USBs and installation media

==== future ====

*Researching 3 libraries in Putnam County, N.Y. in upscale districts, the 3 libraries had Openoffice.org, Firefox and Gimp installed. Further research in under privileged areas will be done. Visited private library which relies on Donations in Cold Springs, NY. Had no FOSS installed and where extremely receptive to the CD idea.

*how can we expand the idea to more libraries, and which are the best to target
*school integration? k-12, universities?

LiveContent

2007-07-20T01:51:05Z

LuisVilla: /* bugs */ - couple comments on the bugs.

[[Category:Technology]]
[[Category:Developer Challenges]]
[[Category:Developer]]
[[Category:freesoftware]]
[[Category:opensource]]
[[Category:ccLiveCD]]
[[Category:LiveContent]]

LiveContent is an umbrella idea which aims to connect and expand Creative Commons and open source communities. LiveContent works to identify creators and content providers working to share their creations more easily with others. LiveContent works to support developers and others who build better technology to distribute these works. LiveContent is up-to-the-minute creativity, "alive" by being licensed Creative Commons, which allows others to better interact with the content.

LiveContent can be delivered in a variety of ways. The first incarnation of LiveContent will deliver content as a LiveCD. LiveCDs are equivalent to what is called a [http://en.wikipedia.org/wiki/LiveDistro LiveDistro]. LiveCDs have traditionally been a vehicle to test an operating system or applications live. Operating systems and/or applications are directly booted from a CD or other type of media without needing to install the actual software on a machine. LiveContent aims to add value to LiveDistros by providing dynamically-generated content that can be added

== Contribute! ==

Creative Commons encourages others to provide ideas, feedback, comments and connections to other projects on this wiki page. There are many ways to contribute:

#Sign up for an account on this wiki and begin adding to the community - your knowledge, ideas and contributions are welcome
#IRC - Channel #CC at http://irc.freenode.net - general chatter from CC-ers, affiliates, guests - http://wiki.creativecommons.org/IRC
#cc-devel listserv - Creative Commons developers email list - http://wiki.creativecommons.org/Mailing_Lists

==Roadmap==

=== June 11===
* Brainstorming "best-of" CC-licensed content to include with the LiveCD
* Connect with other organizations - ALA, LITA, FOSS
* blog post about the project

===June 18===
* (DONE) talk to scott about helping us with builds with the correct sizing
* trying out different spins (tvol)
* bug jon to get test computer (tvol)

===June 25===
* figure out packaging of physical CD (cardboard insert/cd burns/how many/how long it will take to get manufactured/how much) (tvol + alex))
** (DONE) need to schedule meeting with alex for this week (Monday)
** Explaining CC on the packaging
* make public web page requirements on the wiki (tvol)
** (live.creativecommons.org or creativecommons.org/livecontent or creativecommons.org/live ... maybe for now just redirect to wiki page) (tvol)
** NOTECH: just clean up this wiki page (tvol)
* get the automated fedora build system working! (tannewt)

===July 2===
* Have daily builds running on redhat infrastructure (tannewt)
* planning what docs we need to collect for documentation for Fedora, apps, CC-licenses (tvol)
**pull from documentation on sites--don't reinvent the wheel, utilize wikis, but try to distill important info, especially for new users
**we want the most of these to be present as documentation within the cd, not in print
* conceptualize how to have auto-curated packages (pick one package in each media) (tannewt/tvol) - LiveContent takes off
** what are the top [[Content_Curators|Content Curators]] to have, one each for audio, video, image, and text, education. (tvol)
** develop icons for each of these categories? (alex?)

===July 9===
* have basic liveCD build completed (tannewt)

===July 16===

* Have all top auto-curated packages building on redhat infrastructure (tannewt)
* Test out auto-curated packages and communicate with tannewt (tvol)

===July 23===
* (HIGH PRIORITY) Send off CD for printing early week
*build up steam for the release
*library distribution options
**how many will get sent out?
**which libraries?

===July 30===
*press release about the project -work with worldlabel, redhat

===August 6===
*LiveCD rollout at Linuxworld - San Francisco

===August 8th===
*LiveCD rollout CC Salon - San Francisco

== Formats for distribution of LiveContent==

=== USB ===
The LiveContent could also be made to fit onto a usb stick so that it can be plugged into computers and boot straight into Linux and/or have Creative Commons licensed content on this thumbdrive.

=== DVD ===
The Free Me project has already produced a [http://questionsplease.org/freeme live DVD] with almost exactly the same ideas behind it. More than willing to lend a hand with this :D. Contact me at [mailto:jonathan.roberts.uk@googlemail.com] if you think I could be of use.

=== CD ===
We're currently working on creating an ISO image for a bootable system that would be filled with free open source software (FOSS) and CC-licensed content. Creative Commons will team with [http://fedoraproject.org Fedora] (technical support) and [http://www.worldlabel.com/ Worldlabel.com] (development and distribution support) in order to produce a LiveCD.

==ccLiveContent v1.0 - testing feedback==

*Please help CC make LiveContent the best it can be! Provide feedback under the following categories, or create your own!

===interface===
* desktop icons look like part of the background- they should somehow be raised or otherwise be made to look like an icon, rather than part of the background.
* not clear that using two desktops makes sense; just one more thing for people to click on and be confused by. Make it only one desktop by default, and remove the applet from the panel.
* make CC the default search in FF.
* if there is a global CC ical file, the calendar should be subscribed to it so that it shows up in the calendar in the panel clock.
* folders that are 'bookmarked' show up in the 'Places' menus; would be good to bookmark the various Audio/Video/etc. folders, I think.
* nautilus thumbnails certain media types. The thumbnails should be pre-generated so that there isn't excessive drive access and clock icons when people open the folders for the first time. (They are in .thumbnails, I believe.)
* nautilus can put icons on individual files. I suggest that perhaps nautilus should include icons representing the licenses, and then each media/content file can have the license represented as an icon on the file. (Either as a supplement to, or a replacement for, the ugly license.txt file. The license.txt can be hidden with by placing it in .hidden, as in http://svn.gnome.org/viewcvs/livecd-project/trunk/locales/en_US/home/Desktop/Images%20from%20GNOME%20community%20events/.hidden?view=markup)
* nautilus can reorder and remember the order of files; would be good to order the content directories something like content / web links / license.txt. (That information is stored in ~/.nautilus/metafiles/ if you need to back it up.)
* the pictures should be titled with names/author ('foo by Steve Bar.jpg'), instead of 1.jpg, 2.jpg, etc.
* web icons should have the globe replaced with the sites favico or something like it. (There is a way to do this, but I admit I don't recall what it is.)

===content (audio/video/image/text/education)===

* no Free Culture in Texts? :)
* in Education, probably a link to Curriki would be good. Ditto perhaps http://www.introecon.com/ ?
* perhaps the various CC comics, both http://www.law.duke.edu/cspd/comics/ and http://creativecommons.org/about/licenses/comics1/ ? Not sure where those would go.

===proposed additions/deletions to applications===
* would remove DOM Inspector plugin from FF, and add the MozCC plugin.
* why OpenOffice? Abiword and Gnumeric fit onto a liveCD much, much better- could fit another several dozen megs of content, at least, if you made that swap. (I seem to recall the difference was over 100 megs when I was working on the old GNOME liveCDs.)
* I'd remove gnome-terminal, at least from the final build. No need to have it clutter up the iso or the menus for this target audience.

===bugs===

*wireless is not supported on all machines [not fixable by CC]
*system time is incorrect [system does not know the timezone, so never going to know it correctly. Perhaps remove the clock altogether?]
*is there printing support?

===comments/questions===

==ccLiveContent v2.0 - Libraries==

=== Rationale ===

We believe that the LiveContent CD can be a gateway distribution device to test the waters of using free open source software within library settings. It will also help to spread the message about Creative Commons and provide examples of different media that has been licensed under Creative Commons. We wish to promote network effects for open source in general - get more people involved with supporting FOSS, CC.

=== Target ===

Our first LiveContent CD will be created for librarians to test for public terminals at libraries. The object is to get as many libraries to install Free and Open Source Software (FOSS) on their current systems. We will be aiming the implementation at librarians and library administrators.

We strongly believe that libraries are a great way to plant seeds in the community to help the FOSS movement expand. This project will help bring more awareness to open source by providing an example of an operating system and free open source applications that could be implemented on library patron terminals. If the ideas can catch on, the long-range effects might be that libraries would begin to implement free open source software on machines permanently, thus providing a wealth of benefits both to patrons in terms of a more free computing environment and severing the long-standing ties between libraries and proprietary software license fees.

At this time, it seems that CDs provide the best media format that is accessible to most library computer terminals.

=== potential benefits ===

*libraries
**save money on proprietary software licensing - total cost of ownership (tco) is less
**libraries can be seen as cutting edge in adoption of open source
**more control over computing environment
**can test on machines without installing
**can also install directly from a desktop image
**most productivity and creativity applications have a free open source counterpart
**increase services to user by offering more software

=== potential concerns ===

*public libraries vs academic libraries - public libraries have less resources, less staff time to examine new products and test out - at the same time FOSS might most benefit small public libraries, especially rural
*academic libraries are often equipped for more research, and might be better geared towards having the resources for testing and future development
*what kinds of agreements do libraries have with software providers now, if any?
*make the cds very intuitive, well-labeled, good supporting documentation - fedora has a lot of good documentation, +/- of liveCD
*will we only make spins for i386? - probably the architecture of most library terminal machines, unless some use older macs - ppc
*how do we distribute without spamming?
*will libraries trust what we send to them?
*will libraries notice it or have time to look at it?
*less to do with the software and more to do with presentation and documentation
*focus on low income areas, rural?
*will CC put on material that covers all the different licenses? or least restrictive? - attribution only
*different libraries have different budgets which allow for a vast range in hardware and training
*The mailing will have a mail back questionaire asking did they install software and other general questions. - rethink this idea due to spamming/response issues? - think about other ways to gather feedback
*what about adding the CDs to library collections? - might be a good way for people to install or use at home, but doesn't align too well with the applications and content becoming obsolete
*accessibility
**http://ui.openoffice.org/accessibility/disabilities.html
**http://developer.gnome.org/projects/gap/at-types.html

=== What is the current landscape for library computing? ===

*at San Francisco Public Library (SFPL) main branch, there are two types of computer terminals:
**those that are used solely for card catalog lookup - no other features provided
**those where patrons can access the internet (via internet explorer) and use the Microsoft Office 2003 suite (Word, Excel, Powerpoint) - there are no other applications that are accessible through the tailored, limited-view interface

===Proposed LiveCD Contents ===

==== Fedora 7 ====
Fedora 7 is the Linux operating system that will be running live from the CD. Fedora 7 can be customized by creating "spins." Spins are custom builds of the CD with applications and features that meet the users' needs. A specific spin can be documented by including a "build date" on the CD and its packaging. Any user who has installed Fedora on their machine can spin custom LiveCDs.

Documentation at http://fedoraproject.org/wiki/FedoraLiveCD/

There are differnt ways to create LiveCDs with Fedora:
*Graphical User Interface (GUI) - Revisor (comes loaded in Fedora)
*Command Line Interface (CLI) - livecd-creator (creates liveCDs), [https://hosted.fedoraproject.org/projects/pungi Pungi] (creates installation disks)
*users who wish to contribute to Fedora's internal build system need an account - create account @ http://admin.fedoraproject.org/accounts
*Koji is Fedora's server that tracks recent builds - http://koji.fedoraproject.org
*testing notes:
**fedora 7 LiveCD Gnome runs extremely slow on a 256MB test machine
**note - productivity and creativity apps cannot be installed at terminals without first installing Fedora - aka liveCD doesn't support application installs before full OS install

==== FOSS Productivity/creativity/entertainment apps ====

*[http://www.openoffice.org Openoffice] - Complete version
*[http://www.mozilla.com/en-US/firefox/ FireFox] - web browser
*[http://www.gimp.org/ Gimp] - raster graphics editor
*[http://www.inkscape.org/ Inkscape] - vector graphics editor
*[http://www.worldlabel.com Worldlabel.com] Blank Opendocument Format Label Templates and collection of pre-designed label templates: address, shipping, filing, CD - licensed public domain
*Collection of clipart from [http://www.openclipart.org Open Clip Art Library]?
*Totem - audio and video viewer
*gThum - image viewer
*Evince PDF Viewer. Possible PDF editor, Openoffice has excellent PDF export
*SVG Viewer - Gimp

*For Kids (possible inclusion)
**http://www.linuxforkids.org/
**[http://www.tuxpaint.org/ Tuxpaint]
**[http://gcompris.net/-en- qcompris]
**[http://tuxtype.sourceforge.net Tuxtype]
**[http://www.schooltool.org/ Schooltool]

*A good idea might be to include some promotional information like http://why.openoffice.org/why_nfp.html but also for all the other applications, Why Gimp, Why Inscape, etc.

*note that all these FOSS applications are also available for installation on machines running proprietary operating systems (windows, osx), not just linux machines

==== Creative Commons-licensed content ====
We want to provide examples from each category (audio, video, text, image, education) to showcase on the LiveContent CD. We will develop a system that can automatically pull top content from the sites that we choose (and these sites can change as well).

We'll feature one website/service/cc-content provider from each of the 5 categories for this initial run. We should provide examples of cc-licensed materials from each. don't know how many--we'll see how much room is left on the cd:

*audio - jamendo
**[[Audio#Featured_Audio_Sites|more audio]]
*video - blip.tv
**[[Video#Featured_Video_Sites|more video]]
*image - flickr
**[[Image#Featured_Image_Sites|more image]]
*text - lulu
**[[Text#Featured_Text_sites|more text]]
*education - connexions
**[[Education#Featured_Education_sites|more education]]

*[[Multiple_Formats|even more]]

*what about cc-videos?
*possible inclusion of a CC plugin pre-installed in Openoffice.org
*inclusion of CC plug-in for Firefox?

==== Documentation ====

*http://opendocumentfellowship.org/
*explanation of licenses like from the Free Me DVD - http://questionsplease.org/freeme/free-culture/the-licenses/
*obvious CC explanations - to be displayed in an initial pop-up browser page?
**this should mirror the info we have on the inside of the cd packaging - a redirect to the visual on the website
**http://creativecommons.org/about/licenses/meet-the-licenses
**http://creativecommons.org/about/licenses
* tutorials
**http://www.tutorialsforopenoffice.org/
**http://docs.fedoraproject.org/
**http://www.gimp.org/docs/
**http://www.inkscape.org/doc/index.php

=== Interface and Display Options ===

==== Themeing ====
*Gnome with cc desktop, content icons, share/reuse/remix icons

==== Initial Pop-up Screen ====
This screen will be loaded upon booting the CD to welcome users and give an overview of the LiveCD.

Some things to include:
*what is a LiveCD
*what is on the cd
**pointer to Fedora docs
**pointer to App docs
**pointer to CC docs
*instructions about how to open applications
*how to save
*how to quit?

==== how to access cc content ====
*cc icons on the desktop - utilize icons for the content categories (audio, video, text, image, education)
* digging deeper - how do we provide more examples? - possibly through the inclusion of examples of how users can share/remix/reuse content using cc - users can click on these icons to pull up a webpage that explains more

=== Distribution Options ===

We will investigate options for getting the CDs into the hands of the libraries we wish to target. While we wish to provide a quality LiveContent CD to the most libraries we can, we realize that mass mailing may not be the best way to accomplish this distribution goal, especially since this may be considered a type of spamming. Ideas other than mailing include hosting the contents online and doing outreach to libraries and other interested parties through a widespread press release, listservs, hand out at events, or get an in through professional organizations like the American Library Association.

While we are working towards a deliverable LiveContent CD by August 8, further exploration of a dynamic, automated system should be examined. This type of system could be automated to pull updated content from various sources , current application versions and OS patches and build a CD extremely easily. In this way, users could download the most current build at any time.

During development, we hope to provide preliminary builds and demos that we can send to various organization and libraries so that they can review the LiveContent CD and provide input for further development. Later reviews hopefully will be published in numerous ALA publications. Reviews could be sent with the CD in the mailing so that there is neutral positive influence behind the CD.

==== Resources ====

===== Groups =====

*OCLC
**http://www.oclc.org/default.htm
**http://www.oclc.org/research/staff/default.htm
**http://www.oclc.org/research/software/default.htm
**http://www.oclc.org/research/software/opensource.htm

*American Library Association http://www.ala.org

*Library Information Technology Association (LITA) http://www.lita.org

*Open Source Systems interest group http://www.ala.org/ala/lita/litamembership/litaigs/opensourcesystem/opensourcesystems.cfm

*OpenOffice http://marketing.openoffice.org/ and http://distribution.openoffice.org/

===== People =====

*Jack Aboutboul - Redhat mailto:jaa@redhat.com - Redhat will provide the themeing and customized builds of the CDs containing the OS, open source apps, Worldlabel documentation, CC content

*Jonathan Roberts - Free Me DVD - http://questionsplease.org/freeme/

*Mr. Alex Choong of Innotech Resources Pte Ltd (worldlabel.com.sg) will cover the cost of duplication of master Library CD. 8000 to 10000pcs with jewel box or sleedve. He wants will also implement a program in Singapore and Malaysia to distribute the CD to libraries. He mentioned wanting reference to this in press releases.

*project managers for oo marketing: john mccressh-mailto:jpmcc@openoffice.org, cristin driga-mailto:cdriga@openoffice.org
*Mr. Louis Suarez-Potts (Community Manager): mailto:luispo@gmail.com
*distribution-mailto:cdrom@distribution.openoffice.org

*Simon Spero at Sun in North Carolina, who might be willing to provide server space to maintain a dynamic build system

*John Rutherford of Lita/ALA Chairman of Opensource for Lita - IT division of ALA
**http://www.ala.org/ala/lita/litamembership/litacommittees/roster.cfm?committee=lit-igopens
**mailto:jrutherford @ wayne.edu
**Phone: (313) 577-0367
**will be at ALA conference in Washington DC end of June

*David Bretthauer
**http://www.lita.org/ala/lita/litapublications/ital/2101bretthauer.cfm, can be a big help, especially giving ideas which libraries to target for mailings and other stuff.
**mailto:Dave.Bretthauer@uconn.edu
**Tel: 860-486-6494

*Ms. Carrie Russell mailto:crussell@alawash.org
**Copyright Specialist, ALA, Office for Information Technology Policy

===== Reading =====

*ALA public library funding & technology access study
**http://www.ala.org/ala/ors/publiclibraryfundingtechnologyaccessstudy/pullibfunandtechaccstudy.htm
*public libraries and the internet
**http://www.ii.fsu.edu/plinternet_findings.cfm
*http://www.infomotions.com/musings/ossnlibraries-workshop/ossnlibraries-workshop.html
*http://www.newsforge.com/article.pl?sid=03/12/14/1545216&mode=thread&tid=132&tid=151&tid=82
*http://webjunction.org/do/DisplayContent?id=1216
*Article on Open Source in libaries by Gates Foundation: http://webjunction.org/do/DisplayContent?id=734
*Abstract by Siobhan Stevenson, an assistant professor at the Faculty of Information Studies University of Toronto http://www.firstmonday.org/issues/issue12_5/stevenson/index.html

*information on licensing issues for libraries: - http://www.librarycopyright.net/

===== LiveCD Examples =====

* [http://debian-live.alioth.debian.org/ Debian Live] - Debian LiveCDs
* [http://www.knoppix.org/ KNOPPIX] - Well-known LiveCD
* [http://www.slax.org/ Slax] - Slackware-based LiveCD
* [http://www.ubuntu.com/ Ubuntu] - Popular LiveCD
* [http://questionsplease.org/freeme Free Me] - Live DVD promoting free culture in the same way

===== LiveCD Resources =====

* [http://debian-live.alioth.debian.org/ Debian Live]
* [http://www.frozentech.com/content/livecd.php Live CD List] - Long List of LiveCDs
* [http://www.livedistro.org LiveDistro] - [http://www.livedistro.org/taxonomy/term/378/list Build Tools], [http://www.livedistro.org/taxonomy/term/370/list Howtos], [http://www.livedistro.org/vocabulary/18/list Releases]
* [http://reconstructor.aperantis.com/ Reconstructor] - Remaster Ubuntu LiveCDs
* [http://en.wikipedia.org/wiki/Comparison_of_Linux_LiveDistros Wikipedia Linux LiveDistro Comparison]
* [http://en.wikipedia.org/wiki/LiveCD Wikipedia LiveCD]
* [http://uck.sourceforge.net/ Ubuntu Customization Kit] - Make custom Ubuntu LiveCDs
* [http://revisor.fedoraunity.org/ Revisor] - Graphical tool for creating Fedora Live CDs/DVDs/USBs and installation media

==== future ====

*Researching 3 libraries in Putnam County, N.Y. in upscale districts, the 3 libraries had Openoffice.org, Firefox and Gimp installed. Further research in under privileged areas will be done. Visited private library which relies on Donations in Cold Springs, NY. Had no FOSS installed and where extremely receptive to the CD idea.

*how can we expand the idea to more libraries, and which are the best to target
*school integration? k-12, universities?

LiveContent

2007-07-20T01:49:20Z

LuisVilla: /* proposed additions/deletions to applications */

[[Category:Technology]]
[[Category:Developer Challenges]]
[[Category:Developer]]
[[Category:freesoftware]]
[[Category:opensource]]
[[Category:ccLiveCD]]
[[Category:LiveContent]]

LiveContent is an umbrella idea which aims to connect and expand Creative Commons and open source communities. LiveContent works to identify creators and content providers working to share their creations more easily with others. LiveContent works to support developers and others who build better technology to distribute these works. LiveContent is up-to-the-minute creativity, "alive" by being licensed Creative Commons, which allows others to better interact with the content.

LiveContent can be delivered in a variety of ways. The first incarnation of LiveContent will deliver content as a LiveCD. LiveCDs are equivalent to what is called a [http://en.wikipedia.org/wiki/LiveDistro LiveDistro]. LiveCDs have traditionally been a vehicle to test an operating system or applications live. Operating systems and/or applications are directly booted from a CD or other type of media without needing to install the actual software on a machine. LiveContent aims to add value to LiveDistros by providing dynamically-generated content that can be added

== Contribute! ==

Creative Commons encourages others to provide ideas, feedback, comments and connections to other projects on this wiki page. There are many ways to contribute:

#Sign up for an account on this wiki and begin adding to the community - your knowledge, ideas and contributions are welcome
#IRC - Channel #CC at http://irc.freenode.net - general chatter from CC-ers, affiliates, guests - http://wiki.creativecommons.org/IRC
#cc-devel listserv - Creative Commons developers email list - http://wiki.creativecommons.org/Mailing_Lists

==Roadmap==

=== June 11===
* Brainstorming "best-of" CC-licensed content to include with the LiveCD
* Connect with other organizations - ALA, LITA, FOSS
* blog post about the project

===June 18===
* (DONE) talk to scott about helping us with builds with the correct sizing
* trying out different spins (tvol)
* bug jon to get test computer (tvol)

===June 25===
* figure out packaging of physical CD (cardboard insert/cd burns/how many/how long it will take to get manufactured/how much) (tvol + alex))
** (DONE) need to schedule meeting with alex for this week (Monday)
** Explaining CC on the packaging
* make public web page requirements on the wiki (tvol)
** (live.creativecommons.org or creativecommons.org/livecontent or creativecommons.org/live ... maybe for now just redirect to wiki page) (tvol)
** NOTECH: just clean up this wiki page (tvol)
* get the automated fedora build system working! (tannewt)

===July 2===
* Have daily builds running on redhat infrastructure (tannewt)
* planning what docs we need to collect for documentation for Fedora, apps, CC-licenses (tvol)
**pull from documentation on sites--don't reinvent the wheel, utilize wikis, but try to distill important info, especially for new users
**we want the most of these to be present as documentation within the cd, not in print
* conceptualize how to have auto-curated packages (pick one package in each media) (tannewt/tvol) - LiveContent takes off
** what are the top [[Content_Curators|Content Curators]] to have, one each for audio, video, image, and text, education. (tvol)
** develop icons for each of these categories? (alex?)

===July 9===
* have basic liveCD build completed (tannewt)

===July 16===

* Have all top auto-curated packages building on redhat infrastructure (tannewt)
* Test out auto-curated packages and communicate with tannewt (tvol)

===July 23===
* (HIGH PRIORITY) Send off CD for printing early week
*build up steam for the release
*library distribution options
**how many will get sent out?
**which libraries?

===July 30===
*press release about the project -work with worldlabel, redhat

===August 6===
*LiveCD rollout at Linuxworld - San Francisco

===August 8th===
*LiveCD rollout CC Salon - San Francisco

== Formats for distribution of LiveContent==

=== USB ===
The LiveContent could also be made to fit onto a usb stick so that it can be plugged into computers and boot straight into Linux and/or have Creative Commons licensed content on this thumbdrive.

=== DVD ===
The Free Me project has already produced a [http://questionsplease.org/freeme live DVD] with almost exactly the same ideas behind it. More than willing to lend a hand with this :D. Contact me at [mailto:jonathan.roberts.uk@googlemail.com] if you think I could be of use.

=== CD ===
We're currently working on creating an ISO image for a bootable system that would be filled with free open source software (FOSS) and CC-licensed content. Creative Commons will team with [http://fedoraproject.org Fedora] (technical support) and [http://www.worldlabel.com/ Worldlabel.com] (development and distribution support) in order to produce a LiveCD.

==ccLiveContent v1.0 - testing feedback==

*Please help CC make LiveContent the best it can be! Provide feedback under the following categories, or create your own!

===interface===
* desktop icons look like part of the background- they should somehow be raised or otherwise be made to look like an icon, rather than part of the background.
* not clear that using two desktops makes sense; just one more thing for people to click on and be confused by. Make it only one desktop by default, and remove the applet from the panel.
* make CC the default search in FF.
* if there is a global CC ical file, the calendar should be subscribed to it so that it shows up in the calendar in the panel clock.
* folders that are 'bookmarked' show up in the 'Places' menus; would be good to bookmark the various Audio/Video/etc. folders, I think.
* nautilus thumbnails certain media types. The thumbnails should be pre-generated so that there isn't excessive drive access and clock icons when people open the folders for the first time. (They are in .thumbnails, I believe.)
* nautilus can put icons on individual files. I suggest that perhaps nautilus should include icons representing the licenses, and then each media/content file can have the license represented as an icon on the file. (Either as a supplement to, or a replacement for, the ugly license.txt file. The license.txt can be hidden with by placing it in .hidden, as in http://svn.gnome.org/viewcvs/livecd-project/trunk/locales/en_US/home/Desktop/Images%20from%20GNOME%20community%20events/.hidden?view=markup)
* nautilus can reorder and remember the order of files; would be good to order the content directories something like content / web links / license.txt. (That information is stored in ~/.nautilus/metafiles/ if you need to back it up.)
* the pictures should be titled with names/author ('foo by Steve Bar.jpg'), instead of 1.jpg, 2.jpg, etc.
* web icons should have the globe replaced with the sites favico or something like it. (There is a way to do this, but I admit I don't recall what it is.)

===content (audio/video/image/text/education)===

* no Free Culture in Texts? :)
* in Education, probably a link to Curriki would be good. Ditto perhaps http://www.introecon.com/ ?
* perhaps the various CC comics, both http://www.law.duke.edu/cspd/comics/ and http://creativecommons.org/about/licenses/comics1/ ? Not sure where those would go.

===proposed additions/deletions to applications===
* would remove DOM Inspector plugin from FF, and add the MozCC plugin.
* why OpenOffice? Abiword and Gnumeric fit onto a liveCD much, much better- could fit another several dozen megs of content, at least, if you made that swap. (I seem to recall the difference was over 100 megs when I was working on the old GNOME liveCDs.)
* I'd remove gnome-terminal, at least from the final build. No need to have it clutter up the iso or the menus for this target audience.

===bugs===

*wireless is not supported on all machines
*system time is incorrect
*is there printing support?

===comments/questions===

==ccLiveContent v2.0 - Libraries==

=== Rationale ===

We believe that the LiveContent CD can be a gateway distribution device to test the waters of using free open source software within library settings. It will also help to spread the message about Creative Commons and provide examples of different media that has been licensed under Creative Commons. We wish to promote network effects for open source in general - get more people involved with supporting FOSS, CC.

=== Target ===

Our first LiveContent CD will be created for librarians to test for public terminals at libraries. The object is to get as many libraries to install Free and Open Source Software (FOSS) on their current systems. We will be aiming the implementation at librarians and library administrators.

We strongly believe that libraries are a great way to plant seeds in the community to help the FOSS movement expand. This project will help bring more awareness to open source by providing an example of an operating system and free open source applications that could be implemented on library patron terminals. If the ideas can catch on, the long-range effects might be that libraries would begin to implement free open source software on machines permanently, thus providing a wealth of benefits both to patrons in terms of a more free computing environment and severing the long-standing ties between libraries and proprietary software license fees.

At this time, it seems that CDs provide the best media format that is accessible to most library computer terminals.

=== potential benefits ===

*libraries
**save money on proprietary software licensing - total cost of ownership (tco) is less
**libraries can be seen as cutting edge in adoption of open source
**more control over computing environment
**can test on machines without installing
**can also install directly from a desktop image
**most productivity and creativity applications have a free open source counterpart
**increase services to user by offering more software

=== potential concerns ===

*public libraries vs academic libraries - public libraries have less resources, less staff time to examine new products and test out - at the same time FOSS might most benefit small public libraries, especially rural
*academic libraries are often equipped for more research, and might be better geared towards having the resources for testing and future development
*what kinds of agreements do libraries have with software providers now, if any?
*make the cds very intuitive, well-labeled, good supporting documentation - fedora has a lot of good documentation, +/- of liveCD
*will we only make spins for i386? - probably the architecture of most library terminal machines, unless some use older macs - ppc
*how do we distribute without spamming?
*will libraries trust what we send to them?
*will libraries notice it or have time to look at it?
*less to do with the software and more to do with presentation and documentation
*focus on low income areas, rural?
*will CC put on material that covers all the different licenses? or least restrictive? - attribution only
*different libraries have different budgets which allow for a vast range in hardware and training
*The mailing will have a mail back questionaire asking did they install software and other general questions. - rethink this idea due to spamming/response issues? - think about other ways to gather feedback
*what about adding the CDs to library collections? - might be a good way for people to install or use at home, but doesn't align too well with the applications and content becoming obsolete
*accessibility
**http://ui.openoffice.org/accessibility/disabilities.html
**http://developer.gnome.org/projects/gap/at-types.html

=== What is the current landscape for library computing? ===

*at San Francisco Public Library (SFPL) main branch, there are two types of computer terminals:
**those that are used solely for card catalog lookup - no other features provided
**those where patrons can access the internet (via internet explorer) and use the Microsoft Office 2003 suite (Word, Excel, Powerpoint) - there are no other applications that are accessible through the tailored, limited-view interface

===Proposed LiveCD Contents ===

==== Fedora 7 ====
Fedora 7 is the Linux operating system that will be running live from the CD. Fedora 7 can be customized by creating "spins." Spins are custom builds of the CD with applications and features that meet the users' needs. A specific spin can be documented by including a "build date" on the CD and its packaging. Any user who has installed Fedora on their machine can spin custom LiveCDs.

Documentation at http://fedoraproject.org/wiki/FedoraLiveCD/

There are differnt ways to create LiveCDs with Fedora:
*Graphical User Interface (GUI) - Revisor (comes loaded in Fedora)
*Command Line Interface (CLI) - livecd-creator (creates liveCDs), [https://hosted.fedoraproject.org/projects/pungi Pungi] (creates installation disks)
*users who wish to contribute to Fedora's internal build system need an account - create account @ http://admin.fedoraproject.org/accounts
*Koji is Fedora's server that tracks recent builds - http://koji.fedoraproject.org
*testing notes:
**fedora 7 LiveCD Gnome runs extremely slow on a 256MB test machine
**note - productivity and creativity apps cannot be installed at terminals without first installing Fedora - aka liveCD doesn't support application installs before full OS install

==== FOSS Productivity/creativity/entertainment apps ====

*[http://www.openoffice.org Openoffice] - Complete version
*[http://www.mozilla.com/en-US/firefox/ FireFox] - web browser
*[http://www.gimp.org/ Gimp] - raster graphics editor
*[http://www.inkscape.org/ Inkscape] - vector graphics editor
*[http://www.worldlabel.com Worldlabel.com] Blank Opendocument Format Label Templates and collection of pre-designed label templates: address, shipping, filing, CD - licensed public domain
*Collection of clipart from [http://www.openclipart.org Open Clip Art Library]?
*Totem - audio and video viewer
*gThum - image viewer
*Evince PDF Viewer. Possible PDF editor, Openoffice has excellent PDF export
*SVG Viewer - Gimp

*For Kids (possible inclusion)
**http://www.linuxforkids.org/
**[http://www.tuxpaint.org/ Tuxpaint]
**[http://gcompris.net/-en- qcompris]
**[http://tuxtype.sourceforge.net Tuxtype]
**[http://www.schooltool.org/ Schooltool]

*A good idea might be to include some promotional information like http://why.openoffice.org/why_nfp.html but also for all the other applications, Why Gimp, Why Inscape, etc.

*note that all these FOSS applications are also available for installation on machines running proprietary operating systems (windows, osx), not just linux machines

==== Creative Commons-licensed content ====
We want to provide examples from each category (audio, video, text, image, education) to showcase on the LiveContent CD. We will develop a system that can automatically pull top content from the sites that we choose (and these sites can change as well).

We'll feature one website/service/cc-content provider from each of the 5 categories for this initial run. We should provide examples of cc-licensed materials from each. don't know how many--we'll see how much room is left on the cd:

*audio - jamendo
**[[Audio#Featured_Audio_Sites|more audio]]
*video - blip.tv
**[[Video#Featured_Video_Sites|more video]]
*image - flickr
**[[Image#Featured_Image_Sites|more image]]
*text - lulu
**[[Text#Featured_Text_sites|more text]]
*education - connexions
**[[Education#Featured_Education_sites|more education]]

*[[Multiple_Formats|even more]]

*what about cc-videos?
*possible inclusion of a CC plugin pre-installed in Openoffice.org
*inclusion of CC plug-in for Firefox?

==== Documentation ====

*http://opendocumentfellowship.org/
*explanation of licenses like from the Free Me DVD - http://questionsplease.org/freeme/free-culture/the-licenses/
*obvious CC explanations - to be displayed in an initial pop-up browser page?
**this should mirror the info we have on the inside of the cd packaging - a redirect to the visual on the website
**http://creativecommons.org/about/licenses/meet-the-licenses
**http://creativecommons.org/about/licenses
* tutorials
**http://www.tutorialsforopenoffice.org/
**http://docs.fedoraproject.org/
**http://www.gimp.org/docs/
**http://www.inkscape.org/doc/index.php

=== Interface and Display Options ===

==== Themeing ====
*Gnome with cc desktop, content icons, share/reuse/remix icons

==== Initial Pop-up Screen ====
This screen will be loaded upon booting the CD to welcome users and give an overview of the LiveCD.

Some things to include:
*what is a LiveCD
*what is on the cd
**pointer to Fedora docs
**pointer to App docs
**pointer to CC docs
*instructions about how to open applications
*how to save
*how to quit?

==== how to access cc content ====
*cc icons on the desktop - utilize icons for the content categories (audio, video, text, image, education)
* digging deeper - how do we provide more examples? - possibly through the inclusion of examples of how users can share/remix/reuse content using cc - users can click on these icons to pull up a webpage that explains more

=== Distribution Options ===

We will investigate options for getting the CDs into the hands of the libraries we wish to target. While we wish to provide a quality LiveContent CD to the most libraries we can, we realize that mass mailing may not be the best way to accomplish this distribution goal, especially since this may be considered a type of spamming. Ideas other than mailing include hosting the contents online and doing outreach to libraries and other interested parties through a widespread press release, listservs, hand out at events, or get an in through professional organizations like the American Library Association.

While we are working towards a deliverable LiveContent CD by August 8, further exploration of a dynamic, automated system should be examined. This type of system could be automated to pull updated content from various sources , current application versions and OS patches and build a CD extremely easily. In this way, users could download the most current build at any time.

During development, we hope to provide preliminary builds and demos that we can send to various organization and libraries so that they can review the LiveContent CD and provide input for further development. Later reviews hopefully will be published in numerous ALA publications. Reviews could be sent with the CD in the mailing so that there is neutral positive influence behind the CD.

==== Resources ====

===== Groups =====

*OCLC
**http://www.oclc.org/default.htm
**http://www.oclc.org/research/staff/default.htm
**http://www.oclc.org/research/software/default.htm
**http://www.oclc.org/research/software/opensource.htm

*American Library Association http://www.ala.org

*Library Information Technology Association (LITA) http://www.lita.org

*Open Source Systems interest group http://www.ala.org/ala/lita/litamembership/litaigs/opensourcesystem/opensourcesystems.cfm

*OpenOffice http://marketing.openoffice.org/ and http://distribution.openoffice.org/

===== People =====

*Jack Aboutboul - Redhat mailto:jaa@redhat.com - Redhat will provide the themeing and customized builds of the CDs containing the OS, open source apps, Worldlabel documentation, CC content

*Jonathan Roberts - Free Me DVD - http://questionsplease.org/freeme/

*Mr. Alex Choong of Innotech Resources Pte Ltd (worldlabel.com.sg) will cover the cost of duplication of master Library CD. 8000 to 10000pcs with jewel box or sleedve. He wants will also implement a program in Singapore and Malaysia to distribute the CD to libraries. He mentioned wanting reference to this in press releases.

*project managers for oo marketing: john mccressh-mailto:jpmcc@openoffice.org, cristin driga-mailto:cdriga@openoffice.org
*Mr. Louis Suarez-Potts (Community Manager): mailto:luispo@gmail.com
*distribution-mailto:cdrom@distribution.openoffice.org

*Simon Spero at Sun in North Carolina, who might be willing to provide server space to maintain a dynamic build system

*John Rutherford of Lita/ALA Chairman of Opensource for Lita - IT division of ALA
**http://www.ala.org/ala/lita/litamembership/litacommittees/roster.cfm?committee=lit-igopens
**mailto:jrutherford @ wayne.edu
**Phone: (313) 577-0367
**will be at ALA conference in Washington DC end of June

*David Bretthauer
**http://www.lita.org/ala/lita/litapublications/ital/2101bretthauer.cfm, can be a big help, especially giving ideas which libraries to target for mailings and other stuff.
**mailto:Dave.Bretthauer@uconn.edu
**Tel: 860-486-6494

*Ms. Carrie Russell mailto:crussell@alawash.org
**Copyright Specialist, ALA, Office for Information Technology Policy

===== Reading =====

*ALA public library funding & technology access study
**http://www.ala.org/ala/ors/publiclibraryfundingtechnologyaccessstudy/pullibfunandtechaccstudy.htm
*public libraries and the internet
**http://www.ii.fsu.edu/plinternet_findings.cfm
*http://www.infomotions.com/musings/ossnlibraries-workshop/ossnlibraries-workshop.html
*http://www.newsforge.com/article.pl?sid=03/12/14/1545216&mode=thread&tid=132&tid=151&tid=82
*http://webjunction.org/do/DisplayContent?id=1216
*Article on Open Source in libaries by Gates Foundation: http://webjunction.org/do/DisplayContent?id=734
*Abstract by Siobhan Stevenson, an assistant professor at the Faculty of Information Studies University of Toronto http://www.firstmonday.org/issues/issue12_5/stevenson/index.html

*information on licensing issues for libraries: - http://www.librarycopyright.net/

===== LiveCD Examples =====

* [http://debian-live.alioth.debian.org/ Debian Live] - Debian LiveCDs
* [http://www.knoppix.org/ KNOPPIX] - Well-known LiveCD
* [http://www.slax.org/ Slax] - Slackware-based LiveCD
* [http://www.ubuntu.com/ Ubuntu] - Popular LiveCD
* [http://questionsplease.org/freeme Free Me] - Live DVD promoting free culture in the same way

===== LiveCD Resources =====

* [http://debian-live.alioth.debian.org/ Debian Live]
* [http://www.frozentech.com/content/livecd.php Live CD List] - Long List of LiveCDs
* [http://www.livedistro.org LiveDistro] - [http://www.livedistro.org/taxonomy/term/378/list Build Tools], [http://www.livedistro.org/taxonomy/term/370/list Howtos], [http://www.livedistro.org/vocabulary/18/list Releases]
* [http://reconstructor.aperantis.com/ Reconstructor] - Remaster Ubuntu LiveCDs
* [http://en.wikipedia.org/wiki/Comparison_of_Linux_LiveDistros Wikipedia Linux LiveDistro Comparison]
* [http://en.wikipedia.org/wiki/LiveCD Wikipedia LiveCD]
* [http://uck.sourceforge.net/ Ubuntu Customization Kit] - Make custom Ubuntu LiveCDs
* [http://revisor.fedoraunity.org/ Revisor] - Graphical tool for creating Fedora Live CDs/DVDs/USBs and installation media

==== future ====

*Researching 3 libraries in Putnam County, N.Y. in upscale districts, the 3 libraries had Openoffice.org, Firefox and Gimp installed. Further research in under privileged areas will be done. Visited private library which relies on Donations in Cold Springs, NY. Had no FOSS installed and where extremely receptive to the CD idea.

*how can we expand the idea to more libraries, and which are the best to target
*school integration? k-12, universities?

LiveContent

2007-07-20T01:48:17Z

LuisVilla: /* interface */

[[Category:Technology]]
[[Category:Developer Challenges]]
[[Category:Developer]]
[[Category:freesoftware]]
[[Category:opensource]]
[[Category:ccLiveCD]]
[[Category:LiveContent]]

LiveContent is an umbrella idea which aims to connect and expand Creative Commons and open source communities. LiveContent works to identify creators and content providers working to share their creations more easily with others. LiveContent works to support developers and others who build better technology to distribute these works. LiveContent is up-to-the-minute creativity, "alive" by being licensed Creative Commons, which allows others to better interact with the content.

LiveContent can be delivered in a variety of ways. The first incarnation of LiveContent will deliver content as a LiveCD. LiveCDs are equivalent to what is called a [http://en.wikipedia.org/wiki/LiveDistro LiveDistro]. LiveCDs have traditionally been a vehicle to test an operating system or applications live. Operating systems and/or applications are directly booted from a CD or other type of media without needing to install the actual software on a machine. LiveContent aims to add value to LiveDistros by providing dynamically-generated content that can be added

== Contribute! ==

Creative Commons encourages others to provide ideas, feedback, comments and connections to other projects on this wiki page. There are many ways to contribute:

#Sign up for an account on this wiki and begin adding to the community - your knowledge, ideas and contributions are welcome
#IRC - Channel #CC at http://irc.freenode.net - general chatter from CC-ers, affiliates, guests - http://wiki.creativecommons.org/IRC
#cc-devel listserv - Creative Commons developers email list - http://wiki.creativecommons.org/Mailing_Lists

==Roadmap==

=== June 11===
* Brainstorming "best-of" CC-licensed content to include with the LiveCD
* Connect with other organizations - ALA, LITA, FOSS
* blog post about the project

===June 18===
* (DONE) talk to scott about helping us with builds with the correct sizing
* trying out different spins (tvol)
* bug jon to get test computer (tvol)

===June 25===
* figure out packaging of physical CD (cardboard insert/cd burns/how many/how long it will take to get manufactured/how much) (tvol + alex))
** (DONE) need to schedule meeting with alex for this week (Monday)
** Explaining CC on the packaging
* make public web page requirements on the wiki (tvol)
** (live.creativecommons.org or creativecommons.org/livecontent or creativecommons.org/live ... maybe for now just redirect to wiki page) (tvol)
** NOTECH: just clean up this wiki page (tvol)
* get the automated fedora build system working! (tannewt)

===July 2===
* Have daily builds running on redhat infrastructure (tannewt)
* planning what docs we need to collect for documentation for Fedora, apps, CC-licenses (tvol)
**pull from documentation on sites--don't reinvent the wheel, utilize wikis, but try to distill important info, especially for new users
**we want the most of these to be present as documentation within the cd, not in print
* conceptualize how to have auto-curated packages (pick one package in each media) (tannewt/tvol) - LiveContent takes off
** what are the top [[Content_Curators|Content Curators]] to have, one each for audio, video, image, and text, education. (tvol)
** develop icons for each of these categories? (alex?)

===July 9===
* have basic liveCD build completed (tannewt)

===July 16===

* Have all top auto-curated packages building on redhat infrastructure (tannewt)
* Test out auto-curated packages and communicate with tannewt (tvol)

===July 23===
* (HIGH PRIORITY) Send off CD for printing early week
*build up steam for the release
*library distribution options
**how many will get sent out?
**which libraries?

===July 30===
*press release about the project -work with worldlabel, redhat

===August 6===
*LiveCD rollout at Linuxworld - San Francisco

===August 8th===
*LiveCD rollout CC Salon - San Francisco

== Formats for distribution of LiveContent==

=== USB ===
The LiveContent could also be made to fit onto a usb stick so that it can be plugged into computers and boot straight into Linux and/or have Creative Commons licensed content on this thumbdrive.

=== DVD ===
The Free Me project has already produced a [http://questionsplease.org/freeme live DVD] with almost exactly the same ideas behind it. More than willing to lend a hand with this :D. Contact me at [mailto:jonathan.roberts.uk@googlemail.com] if you think I could be of use.

=== CD ===
We're currently working on creating an ISO image for a bootable system that would be filled with free open source software (FOSS) and CC-licensed content. Creative Commons will team with [http://fedoraproject.org Fedora] (technical support) and [http://www.worldlabel.com/ Worldlabel.com] (development and distribution support) in order to produce a LiveCD.

==ccLiveContent v1.0 - testing feedback==

*Please help CC make LiveContent the best it can be! Provide feedback under the following categories, or create your own!

===interface===
* desktop icons look like part of the background- they should somehow be raised or otherwise be made to look like an icon, rather than part of the background.
* not clear that using two desktops makes sense; just one more thing for people to click on and be confused by. Make it only one desktop by default, and remove the applet from the panel.
* make CC the default search in FF.
* if there is a global CC ical file, the calendar should be subscribed to it so that it shows up in the calendar in the panel clock.
* folders that are 'bookmarked' show up in the 'Places' menus; would be good to bookmark the various Audio/Video/etc. folders, I think.
* nautilus thumbnails certain media types. The thumbnails should be pre-generated so that there isn't excessive drive access and clock icons when people open the folders for the first time. (They are in .thumbnails, I believe.)
* nautilus can put icons on individual files. I suggest that perhaps nautilus should include icons representing the licenses, and then each media/content file can have the license represented as an icon on the file. (Either as a supplement to, or a replacement for, the ugly license.txt file. The license.txt can be hidden with by placing it in .hidden, as in http://svn.gnome.org/viewcvs/livecd-project/trunk/locales/en_US/home/Desktop/Images%20from%20GNOME%20community%20events/.hidden?view=markup)
* nautilus can reorder and remember the order of files; would be good to order the content directories something like content / web links / license.txt. (That information is stored in ~/.nautilus/metafiles/ if you need to back it up.)
* the pictures should be titled with names/author ('foo by Steve Bar.jpg'), instead of 1.jpg, 2.jpg, etc.
* web icons should have the globe replaced with the sites favico or something like it. (There is a way to do this, but I admit I don't recall what it is.)

===content (audio/video/image/text/education)===

* no Free Culture in Texts? :)
* in Education, probably a link to Curriki would be good. Ditto perhaps http://www.introecon.com/ ?
* perhaps the various CC comics, both http://www.law.duke.edu/cspd/comics/ and http://creativecommons.org/about/licenses/comics1/ ? Not sure where those would go.

===proposed additions/deletions to applications===
* would remove DOM Inspector plugin from FF, and add the MozCC plugin.
* why OpenOffice? Abiword and Gnumeric fit onto a liveCD much, much better- could fit another several dozen megs of content, at least, if you made that swap.

===bugs===

*wireless is not supported on all machines
*system time is incorrect
*is there printing support?

===comments/questions===

==ccLiveContent v2.0 - Libraries==

=== Rationale ===

We believe that the LiveContent CD can be a gateway distribution device to test the waters of using free open source software within library settings. It will also help to spread the message about Creative Commons and provide examples of different media that has been licensed under Creative Commons. We wish to promote network effects for open source in general - get more people involved with supporting FOSS, CC.

=== Target ===

Our first LiveContent CD will be created for librarians to test for public terminals at libraries. The object is to get as many libraries to install Free and Open Source Software (FOSS) on their current systems. We will be aiming the implementation at librarians and library administrators.

We strongly believe that libraries are a great way to plant seeds in the community to help the FOSS movement expand. This project will help bring more awareness to open source by providing an example of an operating system and free open source applications that could be implemented on library patron terminals. If the ideas can catch on, the long-range effects might be that libraries would begin to implement free open source software on machines permanently, thus providing a wealth of benefits both to patrons in terms of a more free computing environment and severing the long-standing ties between libraries and proprietary software license fees.

At this time, it seems that CDs provide the best media format that is accessible to most library computer terminals.

=== potential benefits ===

*libraries
**save money on proprietary software licensing - total cost of ownership (tco) is less
**libraries can be seen as cutting edge in adoption of open source
**more control over computing environment
**can test on machines without installing
**can also install directly from a desktop image
**most productivity and creativity applications have a free open source counterpart
**increase services to user by offering more software

=== potential concerns ===

*public libraries vs academic libraries - public libraries have less resources, less staff time to examine new products and test out - at the same time FOSS might most benefit small public libraries, especially rural
*academic libraries are often equipped for more research, and might be better geared towards having the resources for testing and future development
*what kinds of agreements do libraries have with software providers now, if any?
*make the cds very intuitive, well-labeled, good supporting documentation - fedora has a lot of good documentation, +/- of liveCD
*will we only make spins for i386? - probably the architecture of most library terminal machines, unless some use older macs - ppc
*how do we distribute without spamming?
*will libraries trust what we send to them?
*will libraries notice it or have time to look at it?
*less to do with the software and more to do with presentation and documentation
*focus on low income areas, rural?
*will CC put on material that covers all the different licenses? or least restrictive? - attribution only
*different libraries have different budgets which allow for a vast range in hardware and training
*The mailing will have a mail back questionaire asking did they install software and other general questions. - rethink this idea due to spamming/response issues? - think about other ways to gather feedback
*what about adding the CDs to library collections? - might be a good way for people to install or use at home, but doesn't align too well with the applications and content becoming obsolete
*accessibility
**http://ui.openoffice.org/accessibility/disabilities.html
**http://developer.gnome.org/projects/gap/at-types.html

=== What is the current landscape for library computing? ===

*at San Francisco Public Library (SFPL) main branch, there are two types of computer terminals:
**those that are used solely for card catalog lookup - no other features provided
**those where patrons can access the internet (via internet explorer) and use the Microsoft Office 2003 suite (Word, Excel, Powerpoint) - there are no other applications that are accessible through the tailored, limited-view interface

===Proposed LiveCD Contents ===

==== Fedora 7 ====
Fedora 7 is the Linux operating system that will be running live from the CD. Fedora 7 can be customized by creating "spins." Spins are custom builds of the CD with applications and features that meet the users' needs. A specific spin can be documented by including a "build date" on the CD and its packaging. Any user who has installed Fedora on their machine can spin custom LiveCDs.

Documentation at http://fedoraproject.org/wiki/FedoraLiveCD/

There are differnt ways to create LiveCDs with Fedora:
*Graphical User Interface (GUI) - Revisor (comes loaded in Fedora)
*Command Line Interface (CLI) - livecd-creator (creates liveCDs), [https://hosted.fedoraproject.org/projects/pungi Pungi] (creates installation disks)
*users who wish to contribute to Fedora's internal build system need an account - create account @ http://admin.fedoraproject.org/accounts
*Koji is Fedora's server that tracks recent builds - http://koji.fedoraproject.org
*testing notes:
**fedora 7 LiveCD Gnome runs extremely slow on a 256MB test machine
**note - productivity and creativity apps cannot be installed at terminals without first installing Fedora - aka liveCD doesn't support application installs before full OS install

==== FOSS Productivity/creativity/entertainment apps ====

*[http://www.openoffice.org Openoffice] - Complete version
*[http://www.mozilla.com/en-US/firefox/ FireFox] - web browser
*[http://www.gimp.org/ Gimp] - raster graphics editor
*[http://www.inkscape.org/ Inkscape] - vector graphics editor
*[http://www.worldlabel.com Worldlabel.com] Blank Opendocument Format Label Templates and collection of pre-designed label templates: address, shipping, filing, CD - licensed public domain
*Collection of clipart from [http://www.openclipart.org Open Clip Art Library]?
*Totem - audio and video viewer
*gThum - image viewer
*Evince PDF Viewer. Possible PDF editor, Openoffice has excellent PDF export
*SVG Viewer - Gimp

*For Kids (possible inclusion)
**http://www.linuxforkids.org/
**[http://www.tuxpaint.org/ Tuxpaint]
**[http://gcompris.net/-en- qcompris]
**[http://tuxtype.sourceforge.net Tuxtype]
**[http://www.schooltool.org/ Schooltool]

*A good idea might be to include some promotional information like http://why.openoffice.org/why_nfp.html but also for all the other applications, Why Gimp, Why Inscape, etc.

*note that all these FOSS applications are also available for installation on machines running proprietary operating systems (windows, osx), not just linux machines

==== Creative Commons-licensed content ====
We want to provide examples from each category (audio, video, text, image, education) to showcase on the LiveContent CD. We will develop a system that can automatically pull top content from the sites that we choose (and these sites can change as well).

We'll feature one website/service/cc-content provider from each of the 5 categories for this initial run. We should provide examples of cc-licensed materials from each. don't know how many--we'll see how much room is left on the cd:

*audio - jamendo
**[[Audio#Featured_Audio_Sites|more audio]]
*video - blip.tv
**[[Video#Featured_Video_Sites|more video]]
*image - flickr
**[[Image#Featured_Image_Sites|more image]]
*text - lulu
**[[Text#Featured_Text_sites|more text]]
*education - connexions
**[[Education#Featured_Education_sites|more education]]

*[[Multiple_Formats|even more]]

*what about cc-videos?
*possible inclusion of a CC plugin pre-installed in Openoffice.org
*inclusion of CC plug-in for Firefox?

==== Documentation ====

*http://opendocumentfellowship.org/
*explanation of licenses like from the Free Me DVD - http://questionsplease.org/freeme/free-culture/the-licenses/
*obvious CC explanations - to be displayed in an initial pop-up browser page?
**this should mirror the info we have on the inside of the cd packaging - a redirect to the visual on the website
**http://creativecommons.org/about/licenses/meet-the-licenses
**http://creativecommons.org/about/licenses
* tutorials
**http://www.tutorialsforopenoffice.org/
**http://docs.fedoraproject.org/
**http://www.gimp.org/docs/
**http://www.inkscape.org/doc/index.php

=== Interface and Display Options ===

==== Themeing ====
*Gnome with cc desktop, content icons, share/reuse/remix icons

==== Initial Pop-up Screen ====
This screen will be loaded upon booting the CD to welcome users and give an overview of the LiveCD.

Some things to include:
*what is a LiveCD
*what is on the cd
**pointer to Fedora docs
**pointer to App docs
**pointer to CC docs
*instructions about how to open applications
*how to save
*how to quit?

==== how to access cc content ====
*cc icons on the desktop - utilize icons for the content categories (audio, video, text, image, education)
* digging deeper - how do we provide more examples? - possibly through the inclusion of examples of how users can share/remix/reuse content using cc - users can click on these icons to pull up a webpage that explains more

=== Distribution Options ===

We will investigate options for getting the CDs into the hands of the libraries we wish to target. While we wish to provide a quality LiveContent CD to the most libraries we can, we realize that mass mailing may not be the best way to accomplish this distribution goal, especially since this may be considered a type of spamming. Ideas other than mailing include hosting the contents online and doing outreach to libraries and other interested parties through a widespread press release, listservs, hand out at events, or get an in through professional organizations like the American Library Association.

While we are working towards a deliverable LiveContent CD by August 8, further exploration of a dynamic, automated system should be examined. This type of system could be automated to pull updated content from various sources , current application versions and OS patches and build a CD extremely easily. In this way, users could download the most current build at any time.

During development, we hope to provide preliminary builds and demos that we can send to various organization and libraries so that they can review the LiveContent CD and provide input for further development. Later reviews hopefully will be published in numerous ALA publications. Reviews could be sent with the CD in the mailing so that there is neutral positive influence behind the CD.

==== Resources ====

===== Groups =====

*OCLC
**http://www.oclc.org/default.htm
**http://www.oclc.org/research/staff/default.htm
**http://www.oclc.org/research/software/default.htm
**http://www.oclc.org/research/software/opensource.htm

*American Library Association http://www.ala.org

*Library Information Technology Association (LITA) http://www.lita.org

*Open Source Systems interest group http://www.ala.org/ala/lita/litamembership/litaigs/opensourcesystem/opensourcesystems.cfm

*OpenOffice http://marketing.openoffice.org/ and http://distribution.openoffice.org/

===== People =====

*Jack Aboutboul - Redhat mailto:jaa@redhat.com - Redhat will provide the themeing and customized builds of the CDs containing the OS, open source apps, Worldlabel documentation, CC content

*Jonathan Roberts - Free Me DVD - http://questionsplease.org/freeme/

*Mr. Alex Choong of Innotech Resources Pte Ltd (worldlabel.com.sg) will cover the cost of duplication of master Library CD. 8000 to 10000pcs with jewel box or sleedve. He wants will also implement a program in Singapore and Malaysia to distribute the CD to libraries. He mentioned wanting reference to this in press releases.

*project managers for oo marketing: john mccressh-mailto:jpmcc@openoffice.org, cristin driga-mailto:cdriga@openoffice.org
*Mr. Louis Suarez-Potts (Community Manager): mailto:luispo@gmail.com
*distribution-mailto:cdrom@distribution.openoffice.org

*Simon Spero at Sun in North Carolina, who might be willing to provide server space to maintain a dynamic build system

*John Rutherford of Lita/ALA Chairman of Opensource for Lita - IT division of ALA
**http://www.ala.org/ala/lita/litamembership/litacommittees/roster.cfm?committee=lit-igopens
**mailto:jrutherford @ wayne.edu
**Phone: (313) 577-0367
**will be at ALA conference in Washington DC end of June

*David Bretthauer
**http://www.lita.org/ala/lita/litapublications/ital/2101bretthauer.cfm, can be a big help, especially giving ideas which libraries to target for mailings and other stuff.
**mailto:Dave.Bretthauer@uconn.edu
**Tel: 860-486-6494

*Ms. Carrie Russell mailto:crussell@alawash.org
**Copyright Specialist, ALA, Office for Information Technology Policy

===== Reading =====

*ALA public library funding & technology access study
**http://www.ala.org/ala/ors/publiclibraryfundingtechnologyaccessstudy/pullibfunandtechaccstudy.htm
*public libraries and the internet
**http://www.ii.fsu.edu/plinternet_findings.cfm
*http://www.infomotions.com/musings/ossnlibraries-workshop/ossnlibraries-workshop.html
*http://www.newsforge.com/article.pl?sid=03/12/14/1545216&mode=thread&tid=132&tid=151&tid=82
*http://webjunction.org/do/DisplayContent?id=1216
*Article on Open Source in libaries by Gates Foundation: http://webjunction.org/do/DisplayContent?id=734
*Abstract by Siobhan Stevenson, an assistant professor at the Faculty of Information Studies University of Toronto http://www.firstmonday.org/issues/issue12_5/stevenson/index.html

*information on licensing issues for libraries: - http://www.librarycopyright.net/

===== LiveCD Examples =====

* [http://debian-live.alioth.debian.org/ Debian Live] - Debian LiveCDs
* [http://www.knoppix.org/ KNOPPIX] - Well-known LiveCD
* [http://www.slax.org/ Slax] - Slackware-based LiveCD
* [http://www.ubuntu.com/ Ubuntu] - Popular LiveCD
* [http://questionsplease.org/freeme Free Me] - Live DVD promoting free culture in the same way

===== LiveCD Resources =====

* [http://debian-live.alioth.debian.org/ Debian Live]
* [http://www.frozentech.com/content/livecd.php Live CD List] - Long List of LiveCDs
* [http://www.livedistro.org LiveDistro] - [http://www.livedistro.org/taxonomy/term/378/list Build Tools], [http://www.livedistro.org/taxonomy/term/370/list Howtos], [http://www.livedistro.org/vocabulary/18/list Releases]
* [http://reconstructor.aperantis.com/ Reconstructor] - Remaster Ubuntu LiveCDs
* [http://en.wikipedia.org/wiki/Comparison_of_Linux_LiveDistros Wikipedia Linux LiveDistro Comparison]
* [http://en.wikipedia.org/wiki/LiveCD Wikipedia LiveCD]
* [http://uck.sourceforge.net/ Ubuntu Customization Kit] - Make custom Ubuntu LiveCDs
* [http://revisor.fedoraunity.org/ Revisor] - Graphical tool for creating Fedora Live CDs/DVDs/USBs and installation media

==== future ====

*Researching 3 libraries in Putnam County, N.Y. in upscale districts, the 3 libraries had Openoffice.org, Firefox and Gimp installed. Further research in under privileged areas will be done. Visited private library which relies on Donations in Cold Springs, NY. Had no FOSS installed and where extremely receptive to the CD idea.

*how can we expand the idea to more libraries, and which are the best to target
*school integration? k-12, universities?

LiveContent

2007-07-20T01:46:50Z

LuisVilla: /* interface */

[[Category:Technology]]
[[Category:Developer Challenges]]
[[Category:Developer]]
[[Category:freesoftware]]
[[Category:opensource]]
[[Category:ccLiveCD]]
[[Category:LiveContent]]

LiveContent is an umbrella idea which aims to connect and expand Creative Commons and open source communities. LiveContent works to identify creators and content providers working to share their creations more easily with others. LiveContent works to support developers and others who build better technology to distribute these works. LiveContent is up-to-the-minute creativity, "alive" by being licensed Creative Commons, which allows others to better interact with the content.

LiveContent can be delivered in a variety of ways. The first incarnation of LiveContent will deliver content as a LiveCD. LiveCDs are equivalent to what is called a [http://en.wikipedia.org/wiki/LiveDistro LiveDistro]. LiveCDs have traditionally been a vehicle to test an operating system or applications live. Operating systems and/or applications are directly booted from a CD or other type of media without needing to install the actual software on a machine. LiveContent aims to add value to LiveDistros by providing dynamically-generated content that can be added

== Contribute! ==

Creative Commons encourages others to provide ideas, feedback, comments and connections to other projects on this wiki page. There are many ways to contribute:

#Sign up for an account on this wiki and begin adding to the community - your knowledge, ideas and contributions are welcome
#IRC - Channel #CC at http://irc.freenode.net - general chatter from CC-ers, affiliates, guests - http://wiki.creativecommons.org/IRC
#cc-devel listserv - Creative Commons developers email list - http://wiki.creativecommons.org/Mailing_Lists

==Roadmap==

=== June 11===
* Brainstorming "best-of" CC-licensed content to include with the LiveCD
* Connect with other organizations - ALA, LITA, FOSS
* blog post about the project

===June 18===
* (DONE) talk to scott about helping us with builds with the correct sizing
* trying out different spins (tvol)
* bug jon to get test computer (tvol)

===June 25===
* figure out packaging of physical CD (cardboard insert/cd burns/how many/how long it will take to get manufactured/how much) (tvol + alex))
** (DONE) need to schedule meeting with alex for this week (Monday)
** Explaining CC on the packaging
* make public web page requirements on the wiki (tvol)
** (live.creativecommons.org or creativecommons.org/livecontent or creativecommons.org/live ... maybe for now just redirect to wiki page) (tvol)
** NOTECH: just clean up this wiki page (tvol)
* get the automated fedora build system working! (tannewt)

===July 2===
* Have daily builds running on redhat infrastructure (tannewt)
* planning what docs we need to collect for documentation for Fedora, apps, CC-licenses (tvol)
**pull from documentation on sites--don't reinvent the wheel, utilize wikis, but try to distill important info, especially for new users
**we want the most of these to be present as documentation within the cd, not in print
* conceptualize how to have auto-curated packages (pick one package in each media) (tannewt/tvol) - LiveContent takes off
** what are the top [[Content_Curators|Content Curators]] to have, one each for audio, video, image, and text, education. (tvol)
** develop icons for each of these categories? (alex?)

===July 9===
* have basic liveCD build completed (tannewt)

===July 16===

* Have all top auto-curated packages building on redhat infrastructure (tannewt)
* Test out auto-curated packages and communicate with tannewt (tvol)

===July 23===
* (HIGH PRIORITY) Send off CD for printing early week
*build up steam for the release
*library distribution options
**how many will get sent out?
**which libraries?

===July 30===
*press release about the project -work with worldlabel, redhat

===August 6===
*LiveCD rollout at Linuxworld - San Francisco

===August 8th===
*LiveCD rollout CC Salon - San Francisco

== Formats for distribution of LiveContent==

=== USB ===
The LiveContent could also be made to fit onto a usb stick so that it can be plugged into computers and boot straight into Linux and/or have Creative Commons licensed content on this thumbdrive.

=== DVD ===
The Free Me project has already produced a [http://questionsplease.org/freeme live DVD] with almost exactly the same ideas behind it. More than willing to lend a hand with this :D. Contact me at [mailto:jonathan.roberts.uk@googlemail.com] if you think I could be of use.

=== CD ===
We're currently working on creating an ISO image for a bootable system that would be filled with free open source software (FOSS) and CC-licensed content. Creative Commons will team with [http://fedoraproject.org Fedora] (technical support) and [http://www.worldlabel.com/ Worldlabel.com] (development and distribution support) in order to produce a LiveCD.

==ccLiveContent v1.0 - testing feedback==

*Please help CC make LiveContent the best it can be! Provide feedback under the following categories, or create your own!

===interface===
* desktop icons look like part of the background- they should somehow be raised or otherwise be made to look like an icon, rather than part of the background.
* not clear that using two desktops makes sense; just one more thing for people to click on and be confused by. Make it only one desktop by default, and remove the applet from the panel.
* make CC the default search in FF.
* if there is a global CC ical file, the calendar should be subscribed to it so that it shows up in the calendar in the panel clock.
* I'd remove gnome-terminal, at least from the final build. No need to have it clutter up the iso or the menus.
* folders that are 'bookmarked' show up in the 'Places' menus; would be good to bookmark the various Audio/Video/etc. folders, I think.
* nautilus thumbnails certain media types. The thumbnails should be pre-generated so that there isn't excessive drive access and clock icons when people open the folders for the first time. (They are in .thumbnails, I believe.)
* nautilus can put icons on individual files. I suggest that perhaps nautilus should include icons representing the licenses, and then each media/content file can have the license represented as an icon on the file. (Either as a supplement to, or a replacement for, the ugly license.txt file. The license.txt can be hidden with by placing it in .hidden, as in http://svn.gnome.org/viewcvs/livecd-project/trunk/locales/en_US/home/Desktop/Images%20from%20GNOME%20community%20events/.hidden?view=markup)
* nautilus can reorder and remember the order of files; would be good to order the content directories something like content / web links / license.txt. (That information is stored in ~/.nautilus/metafiles/ if you need to back it up.)
* the pictures should be titled with names/author ('foo by Steve Bar.jpg'), instead of 1.jpg, 2.jpg, etc.
* web icons should have the globe replaced with the sites favico or something like it. I believe the same trick as previously can be used for that.

===content (audio/video/image/text/education)===

* no Free Culture in Texts? :)
* in Education, probably a link to Curriki would be good. Ditto perhaps http://www.introecon.com/ ?
* perhaps the various CC comics, both http://www.law.duke.edu/cspd/comics/ and http://creativecommons.org/about/licenses/comics1/ ? Not sure where those would go.

===proposed additions/deletions to applications===
* would remove DOM Inspector plugin from FF, and add the MozCC plugin.
* why OpenOffice? Abiword and Gnumeric fit onto a liveCD much, much better- could fit another several dozen megs of content, at least, if you made that swap.

===bugs===

*wireless is not supported on all machines
*system time is incorrect
*is there printing support?

===comments/questions===

==ccLiveContent v2.0 - Libraries==

=== Rationale ===

We believe that the LiveContent CD can be a gateway distribution device to test the waters of using free open source software within library settings. It will also help to spread the message about Creative Commons and provide examples of different media that has been licensed under Creative Commons. We wish to promote network effects for open source in general - get more people involved with supporting FOSS, CC.

=== Target ===

Our first LiveContent CD will be created for librarians to test for public terminals at libraries. The object is to get as many libraries to install Free and Open Source Software (FOSS) on their current systems. We will be aiming the implementation at librarians and library administrators.

We strongly believe that libraries are a great way to plant seeds in the community to help the FOSS movement expand. This project will help bring more awareness to open source by providing an example of an operating system and free open source applications that could be implemented on library patron terminals. If the ideas can catch on, the long-range effects might be that libraries would begin to implement free open source software on machines permanently, thus providing a wealth of benefits both to patrons in terms of a more free computing environment and severing the long-standing ties between libraries and proprietary software license fees.

At this time, it seems that CDs provide the best media format that is accessible to most library computer terminals.

=== potential benefits ===

*libraries
**save money on proprietary software licensing - total cost of ownership (tco) is less
**libraries can be seen as cutting edge in adoption of open source
**more control over computing environment
**can test on machines without installing
**can also install directly from a desktop image
**most productivity and creativity applications have a free open source counterpart
**increase services to user by offering more software

=== potential concerns ===

*public libraries vs academic libraries - public libraries have less resources, less staff time to examine new products and test out - at the same time FOSS might most benefit small public libraries, especially rural
*academic libraries are often equipped for more research, and might be better geared towards having the resources for testing and future development
*what kinds of agreements do libraries have with software providers now, if any?
*make the cds very intuitive, well-labeled, good supporting documentation - fedora has a lot of good documentation, +/- of liveCD
*will we only make spins for i386? - probably the architecture of most library terminal machines, unless some use older macs - ppc
*how do we distribute without spamming?
*will libraries trust what we send to them?
*will libraries notice it or have time to look at it?
*less to do with the software and more to do with presentation and documentation
*focus on low income areas, rural?
*will CC put on material that covers all the different licenses? or least restrictive? - attribution only
*different libraries have different budgets which allow for a vast range in hardware and training
*The mailing will have a mail back questionaire asking did they install software and other general questions. - rethink this idea due to spamming/response issues? - think about other ways to gather feedback
*what about adding the CDs to library collections? - might be a good way for people to install or use at home, but doesn't align too well with the applications and content becoming obsolete
*accessibility
**http://ui.openoffice.org/accessibility/disabilities.html
**http://developer.gnome.org/projects/gap/at-types.html

=== What is the current landscape for library computing? ===

*at San Francisco Public Library (SFPL) main branch, there are two types of computer terminals:
**those that are used solely for card catalog lookup - no other features provided
**those where patrons can access the internet (via internet explorer) and use the Microsoft Office 2003 suite (Word, Excel, Powerpoint) - there are no other applications that are accessible through the tailored, limited-view interface

===Proposed LiveCD Contents ===

==== Fedora 7 ====
Fedora 7 is the Linux operating system that will be running live from the CD. Fedora 7 can be customized by creating "spins." Spins are custom builds of the CD with applications and features that meet the users' needs. A specific spin can be documented by including a "build date" on the CD and its packaging. Any user who has installed Fedora on their machine can spin custom LiveCDs.

Documentation at http://fedoraproject.org/wiki/FedoraLiveCD/

There are differnt ways to create LiveCDs with Fedora:
*Graphical User Interface (GUI) - Revisor (comes loaded in Fedora)
*Command Line Interface (CLI) - livecd-creator (creates liveCDs), [https://hosted.fedoraproject.org/projects/pungi Pungi] (creates installation disks)
*users who wish to contribute to Fedora's internal build system need an account - create account @ http://admin.fedoraproject.org/accounts
*Koji is Fedora's server that tracks recent builds - http://koji.fedoraproject.org
*testing notes:
**fedora 7 LiveCD Gnome runs extremely slow on a 256MB test machine
**note - productivity and creativity apps cannot be installed at terminals without first installing Fedora - aka liveCD doesn't support application installs before full OS install

==== FOSS Productivity/creativity/entertainment apps ====

*[http://www.openoffice.org Openoffice] - Complete version
*[http://www.mozilla.com/en-US/firefox/ FireFox] - web browser
*[http://www.gimp.org/ Gimp] - raster graphics editor
*[http://www.inkscape.org/ Inkscape] - vector graphics editor
*[http://www.worldlabel.com Worldlabel.com] Blank Opendocument Format Label Templates and collection of pre-designed label templates: address, shipping, filing, CD - licensed public domain
*Collection of clipart from [http://www.openclipart.org Open Clip Art Library]?
*Totem - audio and video viewer
*gThum - image viewer
*Evince PDF Viewer. Possible PDF editor, Openoffice has excellent PDF export
*SVG Viewer - Gimp

*For Kids (possible inclusion)
**http://www.linuxforkids.org/
**[http://www.tuxpaint.org/ Tuxpaint]
**[http://gcompris.net/-en- qcompris]
**[http://tuxtype.sourceforge.net Tuxtype]
**[http://www.schooltool.org/ Schooltool]

*A good idea might be to include some promotional information like http://why.openoffice.org/why_nfp.html but also for all the other applications, Why Gimp, Why Inscape, etc.

*note that all these FOSS applications are also available for installation on machines running proprietary operating systems (windows, osx), not just linux machines

==== Creative Commons-licensed content ====
We want to provide examples from each category (audio, video, text, image, education) to showcase on the LiveContent CD. We will develop a system that can automatically pull top content from the sites that we choose (and these sites can change as well).

We'll feature one website/service/cc-content provider from each of the 5 categories for this initial run. We should provide examples of cc-licensed materials from each. don't know how many--we'll see how much room is left on the cd:

*audio - jamendo
**[[Audio#Featured_Audio_Sites|more audio]]
*video - blip.tv
**[[Video#Featured_Video_Sites|more video]]
*image - flickr
**[[Image#Featured_Image_Sites|more image]]
*text - lulu
**[[Text#Featured_Text_sites|more text]]
*education - connexions
**[[Education#Featured_Education_sites|more education]]

*[[Multiple_Formats|even more]]

*what about cc-videos?
*possible inclusion of a CC plugin pre-installed in Openoffice.org
*inclusion of CC plug-in for Firefox?

==== Documentation ====

*http://opendocumentfellowship.org/
*explanation of licenses like from the Free Me DVD - http://questionsplease.org/freeme/free-culture/the-licenses/
*obvious CC explanations - to be displayed in an initial pop-up browser page?
**this should mirror the info we have on the inside of the cd packaging - a redirect to the visual on the website
**http://creativecommons.org/about/licenses/meet-the-licenses
**http://creativecommons.org/about/licenses
* tutorials
**http://www.tutorialsforopenoffice.org/
**http://docs.fedoraproject.org/
**http://www.gimp.org/docs/
**http://www.inkscape.org/doc/index.php

=== Interface and Display Options ===

==== Themeing ====
*Gnome with cc desktop, content icons, share/reuse/remix icons

==== Initial Pop-up Screen ====
This screen will be loaded upon booting the CD to welcome users and give an overview of the LiveCD.

Some things to include:
*what is a LiveCD
*what is on the cd
**pointer to Fedora docs
**pointer to App docs
**pointer to CC docs
*instructions about how to open applications
*how to save
*how to quit?

==== how to access cc content ====
*cc icons on the desktop - utilize icons for the content categories (audio, video, text, image, education)
* digging deeper - how do we provide more examples? - possibly through the inclusion of examples of how users can share/remix/reuse content using cc - users can click on these icons to pull up a webpage that explains more

=== Distribution Options ===

We will investigate options for getting the CDs into the hands of the libraries we wish to target. While we wish to provide a quality LiveContent CD to the most libraries we can, we realize that mass mailing may not be the best way to accomplish this distribution goal, especially since this may be considered a type of spamming. Ideas other than mailing include hosting the contents online and doing outreach to libraries and other interested parties through a widespread press release, listservs, hand out at events, or get an in through professional organizations like the American Library Association.

While we are working towards a deliverable LiveContent CD by August 8, further exploration of a dynamic, automated system should be examined. This type of system could be automated to pull updated content from various sources , current application versions and OS patches and build a CD extremely easily. In this way, users could download the most current build at any time.

During development, we hope to provide preliminary builds and demos that we can send to various organization and libraries so that they can review the LiveContent CD and provide input for further development. Later reviews hopefully will be published in numerous ALA publications. Reviews could be sent with the CD in the mailing so that there is neutral positive influence behind the CD.

==== Resources ====

===== Groups =====

*OCLC
**http://www.oclc.org/default.htm
**http://www.oclc.org/research/staff/default.htm
**http://www.oclc.org/research/software/default.htm
**http://www.oclc.org/research/software/opensource.htm

*American Library Association http://www.ala.org

*Library Information Technology Association (LITA) http://www.lita.org

*Open Source Systems interest group http://www.ala.org/ala/lita/litamembership/litaigs/opensourcesystem/opensourcesystems.cfm

*OpenOffice http://marketing.openoffice.org/ and http://distribution.openoffice.org/

===== People =====

*Jack Aboutboul - Redhat mailto:jaa@redhat.com - Redhat will provide the themeing and customized builds of the CDs containing the OS, open source apps, Worldlabel documentation, CC content

*Jonathan Roberts - Free Me DVD - http://questionsplease.org/freeme/

*Mr. Alex Choong of Innotech Resources Pte Ltd (worldlabel.com.sg) will cover the cost of duplication of master Library CD. 8000 to 10000pcs with jewel box or sleedve. He wants will also implement a program in Singapore and Malaysia to distribute the CD to libraries. He mentioned wanting reference to this in press releases.

*project managers for oo marketing: john mccressh-mailto:jpmcc@openoffice.org, cristin driga-mailto:cdriga@openoffice.org
*Mr. Louis Suarez-Potts (Community Manager): mailto:luispo@gmail.com
*distribution-mailto:cdrom@distribution.openoffice.org

*Simon Spero at Sun in North Carolina, who might be willing to provide server space to maintain a dynamic build system

*John Rutherford of Lita/ALA Chairman of Opensource for Lita - IT division of ALA
**http://www.ala.org/ala/lita/litamembership/litacommittees/roster.cfm?committee=lit-igopens
**mailto:jrutherford @ wayne.edu
**Phone: (313) 577-0367
**will be at ALA conference in Washington DC end of June

*David Bretthauer
**http://www.lita.org/ala/lita/litapublications/ital/2101bretthauer.cfm, can be a big help, especially giving ideas which libraries to target for mailings and other stuff.
**mailto:Dave.Bretthauer@uconn.edu
**Tel: 860-486-6494

*Ms. Carrie Russell mailto:crussell@alawash.org
**Copyright Specialist, ALA, Office for Information Technology Policy

===== Reading =====

*ALA public library funding & technology access study
**http://www.ala.org/ala/ors/publiclibraryfundingtechnologyaccessstudy/pullibfunandtechaccstudy.htm
*public libraries and the internet
**http://www.ii.fsu.edu/plinternet_findings.cfm
*http://www.infomotions.com/musings/ossnlibraries-workshop/ossnlibraries-workshop.html
*http://www.newsforge.com/article.pl?sid=03/12/14/1545216&mode=thread&tid=132&tid=151&tid=82
*http://webjunction.org/do/DisplayContent?id=1216
*Article on Open Source in libaries by Gates Foundation: http://webjunction.org/do/DisplayContent?id=734
*Abstract by Siobhan Stevenson, an assistant professor at the Faculty of Information Studies University of Toronto http://www.firstmonday.org/issues/issue12_5/stevenson/index.html

*information on licensing issues for libraries: - http://www.librarycopyright.net/

===== LiveCD Examples =====

* [http://debian-live.alioth.debian.org/ Debian Live] - Debian LiveCDs
* [http://www.knoppix.org/ KNOPPIX] - Well-known LiveCD
* [http://www.slax.org/ Slax] - Slackware-based LiveCD
* [http://www.ubuntu.com/ Ubuntu] - Popular LiveCD
* [http://questionsplease.org/freeme Free Me] - Live DVD promoting free culture in the same way

===== LiveCD Resources =====

* [http://debian-live.alioth.debian.org/ Debian Live]
* [http://www.frozentech.com/content/livecd.php Live CD List] - Long List of LiveCDs
* [http://www.livedistro.org LiveDistro] - [http://www.livedistro.org/taxonomy/term/378/list Build Tools], [http://www.livedistro.org/taxonomy/term/370/list Howtos], [http://www.livedistro.org/vocabulary/18/list Releases]
* [http://reconstructor.aperantis.com/ Reconstructor] - Remaster Ubuntu LiveCDs
* [http://en.wikipedia.org/wiki/Comparison_of_Linux_LiveDistros Wikipedia Linux LiveDistro Comparison]
* [http://en.wikipedia.org/wiki/LiveCD Wikipedia LiveCD]
* [http://uck.sourceforge.net/ Ubuntu Customization Kit] - Make custom Ubuntu LiveCDs
* [http://revisor.fedoraunity.org/ Revisor] - Graphical tool for creating Fedora Live CDs/DVDs/USBs and installation media

==== future ====

*Researching 3 libraries in Putnam County, N.Y. in upscale districts, the 3 libraries had Openoffice.org, Firefox and Gimp installed. Further research in under privileged areas will be done. Visited private library which relies on Donations in Cold Springs, NY. Had no FOSS installed and where extremely receptive to the CD idea.

*how can we expand the idea to more libraries, and which are the best to target
*school integration? k-12, universities?

LiveContent

2007-07-20T01:46:39Z

LuisVilla: /* proposed additions/deletions to content/applications */ (retitled since content is elsewhere)

[[Category:Technology]]
[[Category:Developer Challenges]]
[[Category:Developer]]
[[Category:freesoftware]]
[[Category:opensource]]
[[Category:ccLiveCD]]
[[Category:LiveContent]]

LiveContent is an umbrella idea which aims to connect and expand Creative Commons and open source communities. LiveContent works to identify creators and content providers working to share their creations more easily with others. LiveContent works to support developers and others who build better technology to distribute these works. LiveContent is up-to-the-minute creativity, "alive" by being licensed Creative Commons, which allows others to better interact with the content.

LiveContent can be delivered in a variety of ways. The first incarnation of LiveContent will deliver content as a LiveCD. LiveCDs are equivalent to what is called a [http://en.wikipedia.org/wiki/LiveDistro LiveDistro]. LiveCDs have traditionally been a vehicle to test an operating system or applications live. Operating systems and/or applications are directly booted from a CD or other type of media without needing to install the actual software on a machine. LiveContent aims to add value to LiveDistros by providing dynamically-generated content that can be added

== Contribute! ==

Creative Commons encourages others to provide ideas, feedback, comments and connections to other projects on this wiki page. There are many ways to contribute:

#Sign up for an account on this wiki and begin adding to the community - your knowledge, ideas and contributions are welcome
#IRC - Channel #CC at http://irc.freenode.net - general chatter from CC-ers, affiliates, guests - http://wiki.creativecommons.org/IRC
#cc-devel listserv - Creative Commons developers email list - http://wiki.creativecommons.org/Mailing_Lists

==Roadmap==

=== June 11===
* Brainstorming "best-of" CC-licensed content to include with the LiveCD
* Connect with other organizations - ALA, LITA, FOSS
* blog post about the project

===June 18===
* (DONE) talk to scott about helping us with builds with the correct sizing
* trying out different spins (tvol)
* bug jon to get test computer (tvol)

===June 25===
* figure out packaging of physical CD (cardboard insert/cd burns/how many/how long it will take to get manufactured/how much) (tvol + alex))
** (DONE) need to schedule meeting with alex for this week (Monday)
** Explaining CC on the packaging
* make public web page requirements on the wiki (tvol)
** (live.creativecommons.org or creativecommons.org/livecontent or creativecommons.org/live ... maybe for now just redirect to wiki page) (tvol)
** NOTECH: just clean up this wiki page (tvol)
* get the automated fedora build system working! (tannewt)

===July 2===
* Have daily builds running on redhat infrastructure (tannewt)
* planning what docs we need to collect for documentation for Fedora, apps, CC-licenses (tvol)
**pull from documentation on sites--don't reinvent the wheel, utilize wikis, but try to distill important info, especially for new users
**we want the most of these to be present as documentation within the cd, not in print
* conceptualize how to have auto-curated packages (pick one package in each media) (tannewt/tvol) - LiveContent takes off
** what are the top [[Content_Curators|Content Curators]] to have, one each for audio, video, image, and text, education. (tvol)
** develop icons for each of these categories? (alex?)

===July 9===
* have basic liveCD build completed (tannewt)

===July 16===

* Have all top auto-curated packages building on redhat infrastructure (tannewt)
* Test out auto-curated packages and communicate with tannewt (tvol)

===July 23===
* (HIGH PRIORITY) Send off CD for printing early week
*build up steam for the release
*library distribution options
**how many will get sent out?
**which libraries?

===July 30===
*press release about the project -work with worldlabel, redhat

===August 6===
*LiveCD rollout at Linuxworld - San Francisco

===August 8th===
*LiveCD rollout CC Salon - San Francisco

== Formats for distribution of LiveContent==

=== USB ===
The LiveContent could also be made to fit onto a usb stick so that it can be plugged into computers and boot straight into Linux and/or have Creative Commons licensed content on this thumbdrive.

=== DVD ===
The Free Me project has already produced a [http://questionsplease.org/freeme live DVD] with almost exactly the same ideas behind it. More than willing to lend a hand with this :D. Contact me at [mailto:jonathan.roberts.uk@googlemail.com] if you think I could be of use.

=== CD ===
We're currently working on creating an ISO image for a bootable system that would be filled with free open source software (FOSS) and CC-licensed content. Creative Commons will team with [http://fedoraproject.org Fedora] (technical support) and [http://www.worldlabel.com/ Worldlabel.com] (development and distribution support) in order to produce a LiveCD.

==ccLiveContent v1.0 - testing feedback==

*Please help CC make LiveContent the best it can be! Provide feedback under the following categories, or create your own!

===interface===
* desktop icons look like part of the background- they should somehow be raised or otherwise be made to look like an icon, rather than part of the background.
* not clear that using two desktops makes sense; just one more thing for people to click on and be confused by. Make it only one desktop by default, and remove the applet from the panel.
* make CC the default search in FF.
* would remove DOM Inspector plugin from FF, and add the MozCC plugin.
* why OpenOffice? Abiword and Gnumeric fit onto a liveCD much, much better- could fit another several dozen megs of content, at least, if you made that swap.
* if there is a global CC ical file, the calendar should be subscribed to it so that it shows up in the calendar in the panel clock.
* I'd remove gnome-terminal, at least from the final build. No need to have it clutter up the iso or the menus.
* folders that are 'bookmarked' show up in the 'Places' menus; would be good to bookmark the various Audio/Video/etc. folders, I think.
* nautilus thumbnails certain media types. The thumbnails should be pre-generated so that there isn't excessive drive access and clock icons when people open the folders for the first time. (They are in .thumbnails, I believe.)
* nautilus can put icons on individual files. I suggest that perhaps nautilus should include icons representing the licenses, and then each media/content file can have the license represented as an icon on the file. (Either as a supplement to, or a replacement for, the ugly license.txt file. The license.txt can be hidden with by placing it in .hidden, as in http://svn.gnome.org/viewcvs/livecd-project/trunk/locales/en_US/home/Desktop/Images%20from%20GNOME%20community%20events/.hidden?view=markup)
* nautilus can reorder and remember the order of files; would be good to order the content directories something like content / web links / license.txt. (That information is stored in ~/.nautilus/metafiles/ if you need to back it up.)
* the pictures should be titled with names/author ('foo by Steve Bar.jpg'), instead of 1.jpg, 2.jpg, etc.
* web icons should have the globe replaced with the sites favico or something like it. I believe the same trick as previously can be used for that.

===content (audio/video/image/text/education)===

* no Free Culture in Texts? :)
* in Education, probably a link to Curriki would be good. Ditto perhaps http://www.introecon.com/ ?
* perhaps the various CC comics, both http://www.law.duke.edu/cspd/comics/ and http://creativecommons.org/about/licenses/comics1/ ? Not sure where those would go.

===proposed additions/deletions to applications===
* would remove DOM Inspector plugin from FF, and add the MozCC plugin.
* why OpenOffice? Abiword and Gnumeric fit onto a liveCD much, much better- could fit another several dozen megs of content, at least, if you made that swap.

===bugs===

*wireless is not supported on all machines
*system time is incorrect
*is there printing support?

===comments/questions===

==ccLiveContent v2.0 - Libraries==

=== Rationale ===

We believe that the LiveContent CD can be a gateway distribution device to test the waters of using free open source software within library settings. It will also help to spread the message about Creative Commons and provide examples of different media that has been licensed under Creative Commons. We wish to promote network effects for open source in general - get more people involved with supporting FOSS, CC.

=== Target ===

Our first LiveContent CD will be created for librarians to test for public terminals at libraries. The object is to get as many libraries to install Free and Open Source Software (FOSS) on their current systems. We will be aiming the implementation at librarians and library administrators.

We strongly believe that libraries are a great way to plant seeds in the community to help the FOSS movement expand. This project will help bring more awareness to open source by providing an example of an operating system and free open source applications that could be implemented on library patron terminals. If the ideas can catch on, the long-range effects might be that libraries would begin to implement free open source software on machines permanently, thus providing a wealth of benefits both to patrons in terms of a more free computing environment and severing the long-standing ties between libraries and proprietary software license fees.

At this time, it seems that CDs provide the best media format that is accessible to most library computer terminals.

=== potential benefits ===

*libraries
**save money on proprietary software licensing - total cost of ownership (tco) is less
**libraries can be seen as cutting edge in adoption of open source
**more control over computing environment
**can test on machines without installing
**can also install directly from a desktop image
**most productivity and creativity applications have a free open source counterpart
**increase services to user by offering more software

=== potential concerns ===

*public libraries vs academic libraries - public libraries have less resources, less staff time to examine new products and test out - at the same time FOSS might most benefit small public libraries, especially rural
*academic libraries are often equipped for more research, and might be better geared towards having the resources for testing and future development
*what kinds of agreements do libraries have with software providers now, if any?
*make the cds very intuitive, well-labeled, good supporting documentation - fedora has a lot of good documentation, +/- of liveCD
*will we only make spins for i386? - probably the architecture of most library terminal machines, unless some use older macs - ppc
*how do we distribute without spamming?
*will libraries trust what we send to them?
*will libraries notice it or have time to look at it?
*less to do with the software and more to do with presentation and documentation
*focus on low income areas, rural?
*will CC put on material that covers all the different licenses? or least restrictive? - attribution only
*different libraries have different budgets which allow for a vast range in hardware and training
*The mailing will have a mail back questionaire asking did they install software and other general questions. - rethink this idea due to spamming/response issues? - think about other ways to gather feedback
*what about adding the CDs to library collections? - might be a good way for people to install or use at home, but doesn't align too well with the applications and content becoming obsolete
*accessibility
**http://ui.openoffice.org/accessibility/disabilities.html
**http://developer.gnome.org/projects/gap/at-types.html

=== What is the current landscape for library computing? ===

*at San Francisco Public Library (SFPL) main branch, there are two types of computer terminals:
**those that are used solely for card catalog lookup - no other features provided
**those where patrons can access the internet (via internet explorer) and use the Microsoft Office 2003 suite (Word, Excel, Powerpoint) - there are no other applications that are accessible through the tailored, limited-view interface

===Proposed LiveCD Contents ===

==== Fedora 7 ====
Fedora 7 is the Linux operating system that will be running live from the CD. Fedora 7 can be customized by creating "spins." Spins are custom builds of the CD with applications and features that meet the users' needs. A specific spin can be documented by including a "build date" on the CD and its packaging. Any user who has installed Fedora on their machine can spin custom LiveCDs.

Documentation at http://fedoraproject.org/wiki/FedoraLiveCD/

There are differnt ways to create LiveCDs with Fedora:
*Graphical User Interface (GUI) - Revisor (comes loaded in Fedora)
*Command Line Interface (CLI) - livecd-creator (creates liveCDs), [https://hosted.fedoraproject.org/projects/pungi Pungi] (creates installation disks)
*users who wish to contribute to Fedora's internal build system need an account - create account @ http://admin.fedoraproject.org/accounts
*Koji is Fedora's server that tracks recent builds - http://koji.fedoraproject.org
*testing notes:
**fedora 7 LiveCD Gnome runs extremely slow on a 256MB test machine
**note - productivity and creativity apps cannot be installed at terminals without first installing Fedora - aka liveCD doesn't support application installs before full OS install

==== FOSS Productivity/creativity/entertainment apps ====

*[http://www.openoffice.org Openoffice] - Complete version
*[http://www.mozilla.com/en-US/firefox/ FireFox] - web browser
*[http://www.gimp.org/ Gimp] - raster graphics editor
*[http://www.inkscape.org/ Inkscape] - vector graphics editor
*[http://www.worldlabel.com Worldlabel.com] Blank Opendocument Format Label Templates and collection of pre-designed label templates: address, shipping, filing, CD - licensed public domain
*Collection of clipart from [http://www.openclipart.org Open Clip Art Library]?
*Totem - audio and video viewer
*gThum - image viewer
*Evince PDF Viewer. Possible PDF editor, Openoffice has excellent PDF export
*SVG Viewer - Gimp

*For Kids (possible inclusion)
**http://www.linuxforkids.org/
**[http://www.tuxpaint.org/ Tuxpaint]
**[http://gcompris.net/-en- qcompris]
**[http://tuxtype.sourceforge.net Tuxtype]
**[http://www.schooltool.org/ Schooltool]

*A good idea might be to include some promotional information like http://why.openoffice.org/why_nfp.html but also for all the other applications, Why Gimp, Why Inscape, etc.

*note that all these FOSS applications are also available for installation on machines running proprietary operating systems (windows, osx), not just linux machines

==== Creative Commons-licensed content ====
We want to provide examples from each category (audio, video, text, image, education) to showcase on the LiveContent CD. We will develop a system that can automatically pull top content from the sites that we choose (and these sites can change as well).

We'll feature one website/service/cc-content provider from each of the 5 categories for this initial run. We should provide examples of cc-licensed materials from each. don't know how many--we'll see how much room is left on the cd:

*audio - jamendo
**[[Audio#Featured_Audio_Sites|more audio]]
*video - blip.tv
**[[Video#Featured_Video_Sites|more video]]
*image - flickr
**[[Image#Featured_Image_Sites|more image]]
*text - lulu
**[[Text#Featured_Text_sites|more text]]
*education - connexions
**[[Education#Featured_Education_sites|more education]]

*[[Multiple_Formats|even more]]

*what about cc-videos?
*possible inclusion of a CC plugin pre-installed in Openoffice.org
*inclusion of CC plug-in for Firefox?

==== Documentation ====

*http://opendocumentfellowship.org/
*explanation of licenses like from the Free Me DVD - http://questionsplease.org/freeme/free-culture/the-licenses/
*obvious CC explanations - to be displayed in an initial pop-up browser page?
**this should mirror the info we have on the inside of the cd packaging - a redirect to the visual on the website
**http://creativecommons.org/about/licenses/meet-the-licenses
**http://creativecommons.org/about/licenses
* tutorials
**http://www.tutorialsforopenoffice.org/
**http://docs.fedoraproject.org/
**http://www.gimp.org/docs/
**http://www.inkscape.org/doc/index.php

=== Interface and Display Options ===

==== Themeing ====
*Gnome with cc desktop, content icons, share/reuse/remix icons

==== Initial Pop-up Screen ====
This screen will be loaded upon booting the CD to welcome users and give an overview of the LiveCD.

Some things to include:
*what is a LiveCD
*what is on the cd
**pointer to Fedora docs
**pointer to App docs
**pointer to CC docs
*instructions about how to open applications
*how to save
*how to quit?

==== how to access cc content ====
*cc icons on the desktop - utilize icons for the content categories (audio, video, text, image, education)
* digging deeper - how do we provide more examples? - possibly through the inclusion of examples of how users can share/remix/reuse content using cc - users can click on these icons to pull up a webpage that explains more

=== Distribution Options ===

We will investigate options for getting the CDs into the hands of the libraries we wish to target. While we wish to provide a quality LiveContent CD to the most libraries we can, we realize that mass mailing may not be the best way to accomplish this distribution goal, especially since this may be considered a type of spamming. Ideas other than mailing include hosting the contents online and doing outreach to libraries and other interested parties through a widespread press release, listservs, hand out at events, or get an in through professional organizations like the American Library Association.

While we are working towards a deliverable LiveContent CD by August 8, further exploration of a dynamic, automated system should be examined. This type of system could be automated to pull updated content from various sources , current application versions and OS patches and build a CD extremely easily. In this way, users could download the most current build at any time.

During development, we hope to provide preliminary builds and demos that we can send to various organization and libraries so that they can review the LiveContent CD and provide input for further development. Later reviews hopefully will be published in numerous ALA publications. Reviews could be sent with the CD in the mailing so that there is neutral positive influence behind the CD.

==== Resources ====

===== Groups =====

*OCLC
**http://www.oclc.org/default.htm
**http://www.oclc.org/research/staff/default.htm
**http://www.oclc.org/research/software/default.htm
**http://www.oclc.org/research/software/opensource.htm

*American Library Association http://www.ala.org

*Library Information Technology Association (LITA) http://www.lita.org

*Open Source Systems interest group http://www.ala.org/ala/lita/litamembership/litaigs/opensourcesystem/opensourcesystems.cfm

*OpenOffice http://marketing.openoffice.org/ and http://distribution.openoffice.org/

===== People =====

*Jack Aboutboul - Redhat mailto:jaa@redhat.com - Redhat will provide the themeing and customized builds of the CDs containing the OS, open source apps, Worldlabel documentation, CC content

*Jonathan Roberts - Free Me DVD - http://questionsplease.org/freeme/

*Mr. Alex Choong of Innotech Resources Pte Ltd (worldlabel.com.sg) will cover the cost of duplication of master Library CD. 8000 to 10000pcs with jewel box or sleedve. He wants will also implement a program in Singapore and Malaysia to distribute the CD to libraries. He mentioned wanting reference to this in press releases.

*project managers for oo marketing: john mccressh-mailto:jpmcc@openoffice.org, cristin driga-mailto:cdriga@openoffice.org
*Mr. Louis Suarez-Potts (Community Manager): mailto:luispo@gmail.com
*distribution-mailto:cdrom@distribution.openoffice.org

*Simon Spero at Sun in North Carolina, who might be willing to provide server space to maintain a dynamic build system

*John Rutherford of Lita/ALA Chairman of Opensource for Lita - IT division of ALA
**http://www.ala.org/ala/lita/litamembership/litacommittees/roster.cfm?committee=lit-igopens
**mailto:jrutherford @ wayne.edu
**Phone: (313) 577-0367
**will be at ALA conference in Washington DC end of June

*David Bretthauer
**http://www.lita.org/ala/lita/litapublications/ital/2101bretthauer.cfm, can be a big help, especially giving ideas which libraries to target for mailings and other stuff.
**mailto:Dave.Bretthauer@uconn.edu
**Tel: 860-486-6494

*Ms. Carrie Russell mailto:crussell@alawash.org
**Copyright Specialist, ALA, Office for Information Technology Policy

===== Reading =====

*ALA public library funding & technology access study
**http://www.ala.org/ala/ors/publiclibraryfundingtechnologyaccessstudy/pullibfunandtechaccstudy.htm
*public libraries and the internet
**http://www.ii.fsu.edu/plinternet_findings.cfm
*http://www.infomotions.com/musings/ossnlibraries-workshop/ossnlibraries-workshop.html
*http://www.newsforge.com/article.pl?sid=03/12/14/1545216&mode=thread&tid=132&tid=151&tid=82
*http://webjunction.org/do/DisplayContent?id=1216
*Article on Open Source in libaries by Gates Foundation: http://webjunction.org/do/DisplayContent?id=734
*Abstract by Siobhan Stevenson, an assistant professor at the Faculty of Information Studies University of Toronto http://www.firstmonday.org/issues/issue12_5/stevenson/index.html

*information on licensing issues for libraries: - http://www.librarycopyright.net/

===== LiveCD Examples =====

* [http://debian-live.alioth.debian.org/ Debian Live] - Debian LiveCDs
* [http://www.knoppix.org/ KNOPPIX] - Well-known LiveCD
* [http://www.slax.org/ Slax] - Slackware-based LiveCD
* [http://www.ubuntu.com/ Ubuntu] - Popular LiveCD
* [http://questionsplease.org/freeme Free Me] - Live DVD promoting free culture in the same way

===== LiveCD Resources =====

* [http://debian-live.alioth.debian.org/ Debian Live]
* [http://www.frozentech.com/content/livecd.php Live CD List] - Long List of LiveCDs
* [http://www.livedistro.org LiveDistro] - [http://www.livedistro.org/taxonomy/term/378/list Build Tools], [http://www.livedistro.org/taxonomy/term/370/list Howtos], [http://www.livedistro.org/vocabulary/18/list Releases]
* [http://reconstructor.aperantis.com/ Reconstructor] - Remaster Ubuntu LiveCDs
* [http://en.wikipedia.org/wiki/Comparison_of_Linux_LiveDistros Wikipedia Linux LiveDistro Comparison]
* [http://en.wikipedia.org/wiki/LiveCD Wikipedia LiveCD]
* [http://uck.sourceforge.net/ Ubuntu Customization Kit] - Make custom Ubuntu LiveCDs
* [http://revisor.fedoraunity.org/ Revisor] - Graphical tool for creating Fedora Live CDs/DVDs/USBs and installation media

==== future ====

*Researching 3 libraries in Putnam County, N.Y. in upscale districts, the 3 libraries had Openoffice.org, Firefox and Gimp installed. Further research in under privileged areas will be done. Visited private library which relies on Donations in Cold Springs, NY. Had no FOSS installed and where extremely receptive to the CD idea.

*how can we expand the idea to more libraries, and which are the best to target
*school integration? k-12, universities?

LiveContent

2007-07-20T01:44:58Z

LuisVilla: /* content (audio/video/image/text/education) */

[[Category:Technology]]
[[Category:Developer Challenges]]
[[Category:Developer]]
[[Category:freesoftware]]
[[Category:opensource]]
[[Category:ccLiveCD]]
[[Category:LiveContent]]

LiveContent is an umbrella idea which aims to connect and expand Creative Commons and open source communities. LiveContent works to identify creators and content providers working to share their creations more easily with others. LiveContent works to support developers and others who build better technology to distribute these works. LiveContent is up-to-the-minute creativity, "alive" by being licensed Creative Commons, which allows others to better interact with the content.

LiveContent can be delivered in a variety of ways. The first incarnation of LiveContent will deliver content as a LiveCD. LiveCDs are equivalent to what is called a [http://en.wikipedia.org/wiki/LiveDistro LiveDistro]. LiveCDs have traditionally been a vehicle to test an operating system or applications live. Operating systems and/or applications are directly booted from a CD or other type of media without needing to install the actual software on a machine. LiveContent aims to add value to LiveDistros by providing dynamically-generated content that can be added

== Contribute! ==

Creative Commons encourages others to provide ideas, feedback, comments and connections to other projects on this wiki page. There are many ways to contribute:

#Sign up for an account on this wiki and begin adding to the community - your knowledge, ideas and contributions are welcome
#IRC - Channel #CC at http://irc.freenode.net - general chatter from CC-ers, affiliates, guests - http://wiki.creativecommons.org/IRC
#cc-devel listserv - Creative Commons developers email list - http://wiki.creativecommons.org/Mailing_Lists

==Roadmap==

=== June 11===
* Brainstorming "best-of" CC-licensed content to include with the LiveCD
* Connect with other organizations - ALA, LITA, FOSS
* blog post about the project

===June 18===
* (DONE) talk to scott about helping us with builds with the correct sizing
* trying out different spins (tvol)
* bug jon to get test computer (tvol)

===June 25===
* figure out packaging of physical CD (cardboard insert/cd burns/how many/how long it will take to get manufactured/how much) (tvol + alex))
** (DONE) need to schedule meeting with alex for this week (Monday)
** Explaining CC on the packaging
* make public web page requirements on the wiki (tvol)
** (live.creativecommons.org or creativecommons.org/livecontent or creativecommons.org/live ... maybe for now just redirect to wiki page) (tvol)
** NOTECH: just clean up this wiki page (tvol)
* get the automated fedora build system working! (tannewt)

===July 2===
* Have daily builds running on redhat infrastructure (tannewt)
* planning what docs we need to collect for documentation for Fedora, apps, CC-licenses (tvol)
**pull from documentation on sites--don't reinvent the wheel, utilize wikis, but try to distill important info, especially for new users
**we want the most of these to be present as documentation within the cd, not in print
* conceptualize how to have auto-curated packages (pick one package in each media) (tannewt/tvol) - LiveContent takes off
** what are the top [[Content_Curators|Content Curators]] to have, one each for audio, video, image, and text, education. (tvol)
** develop icons for each of these categories? (alex?)

===July 9===
* have basic liveCD build completed (tannewt)

===July 16===

* Have all top auto-curated packages building on redhat infrastructure (tannewt)
* Test out auto-curated packages and communicate with tannewt (tvol)

===July 23===
* (HIGH PRIORITY) Send off CD for printing early week
*build up steam for the release
*library distribution options
**how many will get sent out?
**which libraries?

===July 30===
*press release about the project -work with worldlabel, redhat

===August 6===
*LiveCD rollout at Linuxworld - San Francisco

===August 8th===
*LiveCD rollout CC Salon - San Francisco

== Formats for distribution of LiveContent==

=== USB ===
The LiveContent could also be made to fit onto a usb stick so that it can be plugged into computers and boot straight into Linux and/or have Creative Commons licensed content on this thumbdrive.

=== DVD ===
The Free Me project has already produced a [http://questionsplease.org/freeme live DVD] with almost exactly the same ideas behind it. More than willing to lend a hand with this :D. Contact me at [mailto:jonathan.roberts.uk@googlemail.com] if you think I could be of use.

=== CD ===
We're currently working on creating an ISO image for a bootable system that would be filled with free open source software (FOSS) and CC-licensed content. Creative Commons will team with [http://fedoraproject.org Fedora] (technical support) and [http://www.worldlabel.com/ Worldlabel.com] (development and distribution support) in order to produce a LiveCD.

==ccLiveContent v1.0 - testing feedback==

*Please help CC make LiveContent the best it can be! Provide feedback under the following categories, or create your own!

===interface===
* desktop icons look like part of the background- they should somehow be raised or otherwise be made to look like an icon, rather than part of the background.
* not clear that using two desktops makes sense; just one more thing for people to click on and be confused by. Make it only one desktop by default, and remove the applet from the panel.
* make CC the default search in FF.
* would remove DOM Inspector plugin from FF, and add the MozCC plugin.
* why OpenOffice? Abiword and Gnumeric fit onto a liveCD much, much better- could fit another several dozen megs of content, at least, if you made that swap.
* if there is a global CC ical file, the calendar should be subscribed to it so that it shows up in the calendar in the panel clock.
* I'd remove gnome-terminal, at least from the final build. No need to have it clutter up the iso or the menus.
* folders that are 'bookmarked' show up in the 'Places' menus; would be good to bookmark the various Audio/Video/etc. folders, I think.
* nautilus thumbnails certain media types. The thumbnails should be pre-generated so that there isn't excessive drive access and clock icons when people open the folders for the first time. (They are in .thumbnails, I believe.)
* nautilus can put icons on individual files. I suggest that perhaps nautilus should include icons representing the licenses, and then each media/content file can have the license represented as an icon on the file. (Either as a supplement to, or a replacement for, the ugly license.txt file. The license.txt can be hidden with by placing it in .hidden, as in http://svn.gnome.org/viewcvs/livecd-project/trunk/locales/en_US/home/Desktop/Images%20from%20GNOME%20community%20events/.hidden?view=markup)
* nautilus can reorder and remember the order of files; would be good to order the content directories something like content / web links / license.txt. (That information is stored in ~/.nautilus/metafiles/ if you need to back it up.)
* the pictures should be titled with names/author ('foo by Steve Bar.jpg'), instead of 1.jpg, 2.jpg, etc.
* web icons should have the globe replaced with the sites favico or something like it. I believe the same trick as previously can be used for that.

===content (audio/video/image/text/education)===

* no Free Culture in Texts? :)
* in Education, probably a link to Curriki would be good. Ditto perhaps http://www.introecon.com/ ?
* perhaps the various CC comics, both http://www.law.duke.edu/cspd/comics/ and http://creativecommons.org/about/licenses/comics1/ ? Not sure where those would go.

===proposed additions/deletions to content/applications===

===bugs===

*wireless is not supported on all machines
*system time is incorrect
*is there printing support?

===comments/questions===

==ccLiveContent v2.0 - Libraries==

=== Rationale ===

We believe that the LiveContent CD can be a gateway distribution device to test the waters of using free open source software within library settings. It will also help to spread the message about Creative Commons and provide examples of different media that has been licensed under Creative Commons. We wish to promote network effects for open source in general - get more people involved with supporting FOSS, CC.

=== Target ===

Our first LiveContent CD will be created for librarians to test for public terminals at libraries. The object is to get as many libraries to install Free and Open Source Software (FOSS) on their current systems. We will be aiming the implementation at librarians and library administrators.

We strongly believe that libraries are a great way to plant seeds in the community to help the FOSS movement expand. This project will help bring more awareness to open source by providing an example of an operating system and free open source applications that could be implemented on library patron terminals. If the ideas can catch on, the long-range effects might be that libraries would begin to implement free open source software on machines permanently, thus providing a wealth of benefits both to patrons in terms of a more free computing environment and severing the long-standing ties between libraries and proprietary software license fees.

At this time, it seems that CDs provide the best media format that is accessible to most library computer terminals.

=== potential benefits ===

*libraries
**save money on proprietary software licensing - total cost of ownership (tco) is less
**libraries can be seen as cutting edge in adoption of open source
**more control over computing environment
**can test on machines without installing
**can also install directly from a desktop image
**most productivity and creativity applications have a free open source counterpart
**increase services to user by offering more software

=== potential concerns ===

*public libraries vs academic libraries - public libraries have less resources, less staff time to examine new products and test out - at the same time FOSS might most benefit small public libraries, especially rural
*academic libraries are often equipped for more research, and might be better geared towards having the resources for testing and future development
*what kinds of agreements do libraries have with software providers now, if any?
*make the cds very intuitive, well-labeled, good supporting documentation - fedora has a lot of good documentation, +/- of liveCD
*will we only make spins for i386? - probably the architecture of most library terminal machines, unless some use older macs - ppc
*how do we distribute without spamming?
*will libraries trust what we send to them?
*will libraries notice it or have time to look at it?
*less to do with the software and more to do with presentation and documentation
*focus on low income areas, rural?
*will CC put on material that covers all the different licenses? or least restrictive? - attribution only
*different libraries have different budgets which allow for a vast range in hardware and training
*The mailing will have a mail back questionaire asking did they install software and other general questions. - rethink this idea due to spamming/response issues? - think about other ways to gather feedback
*what about adding the CDs to library collections? - might be a good way for people to install or use at home, but doesn't align too well with the applications and content becoming obsolete
*accessibility
**http://ui.openoffice.org/accessibility/disabilities.html
**http://developer.gnome.org/projects/gap/at-types.html

=== What is the current landscape for library computing? ===

*at San Francisco Public Library (SFPL) main branch, there are two types of computer terminals:
**those that are used solely for card catalog lookup - no other features provided
**those where patrons can access the internet (via internet explorer) and use the Microsoft Office 2003 suite (Word, Excel, Powerpoint) - there are no other applications that are accessible through the tailored, limited-view interface

===Proposed LiveCD Contents ===

==== Fedora 7 ====
Fedora 7 is the Linux operating system that will be running live from the CD. Fedora 7 can be customized by creating "spins." Spins are custom builds of the CD with applications and features that meet the users' needs. A specific spin can be documented by including a "build date" on the CD and its packaging. Any user who has installed Fedora on their machine can spin custom LiveCDs.

Documentation at http://fedoraproject.org/wiki/FedoraLiveCD/

There are differnt ways to create LiveCDs with Fedora:
*Graphical User Interface (GUI) - Revisor (comes loaded in Fedora)
*Command Line Interface (CLI) - livecd-creator (creates liveCDs), [https://hosted.fedoraproject.org/projects/pungi Pungi] (creates installation disks)
*users who wish to contribute to Fedora's internal build system need an account - create account @ http://admin.fedoraproject.org/accounts
*Koji is Fedora's server that tracks recent builds - http://koji.fedoraproject.org
*testing notes:
**fedora 7 LiveCD Gnome runs extremely slow on a 256MB test machine
**note - productivity and creativity apps cannot be installed at terminals without first installing Fedora - aka liveCD doesn't support application installs before full OS install

==== FOSS Productivity/creativity/entertainment apps ====

*[http://www.openoffice.org Openoffice] - Complete version
*[http://www.mozilla.com/en-US/firefox/ FireFox] - web browser
*[http://www.gimp.org/ Gimp] - raster graphics editor
*[http://www.inkscape.org/ Inkscape] - vector graphics editor
*[http://www.worldlabel.com Worldlabel.com] Blank Opendocument Format Label Templates and collection of pre-designed label templates: address, shipping, filing, CD - licensed public domain
*Collection of clipart from [http://www.openclipart.org Open Clip Art Library]?
*Totem - audio and video viewer
*gThum - image viewer
*Evince PDF Viewer. Possible PDF editor, Openoffice has excellent PDF export
*SVG Viewer - Gimp

*For Kids (possible inclusion)
**http://www.linuxforkids.org/
**[http://www.tuxpaint.org/ Tuxpaint]
**[http://gcompris.net/-en- qcompris]
**[http://tuxtype.sourceforge.net Tuxtype]
**[http://www.schooltool.org/ Schooltool]

*A good idea might be to include some promotional information like http://why.openoffice.org/why_nfp.html but also for all the other applications, Why Gimp, Why Inscape, etc.

*note that all these FOSS applications are also available for installation on machines running proprietary operating systems (windows, osx), not just linux machines

==== Creative Commons-licensed content ====
We want to provide examples from each category (audio, video, text, image, education) to showcase on the LiveContent CD. We will develop a system that can automatically pull top content from the sites that we choose (and these sites can change as well).

We'll feature one website/service/cc-content provider from each of the 5 categories for this initial run. We should provide examples of cc-licensed materials from each. don't know how many--we'll see how much room is left on the cd:

*audio - jamendo
**[[Audio#Featured_Audio_Sites|more audio]]
*video - blip.tv
**[[Video#Featured_Video_Sites|more video]]
*image - flickr
**[[Image#Featured_Image_Sites|more image]]
*text - lulu
**[[Text#Featured_Text_sites|more text]]
*education - connexions
**[[Education#Featured_Education_sites|more education]]

*[[Multiple_Formats|even more]]

*what about cc-videos?
*possible inclusion of a CC plugin pre-installed in Openoffice.org
*inclusion of CC plug-in for Firefox?

==== Documentation ====

*http://opendocumentfellowship.org/
*explanation of licenses like from the Free Me DVD - http://questionsplease.org/freeme/free-culture/the-licenses/
*obvious CC explanations - to be displayed in an initial pop-up browser page?
**this should mirror the info we have on the inside of the cd packaging - a redirect to the visual on the website
**http://creativecommons.org/about/licenses/meet-the-licenses
**http://creativecommons.org/about/licenses
* tutorials
**http://www.tutorialsforopenoffice.org/
**http://docs.fedoraproject.org/
**http://www.gimp.org/docs/
**http://www.inkscape.org/doc/index.php

=== Interface and Display Options ===

==== Themeing ====
*Gnome with cc desktop, content icons, share/reuse/remix icons

==== Initial Pop-up Screen ====
This screen will be loaded upon booting the CD to welcome users and give an overview of the LiveCD.

Some things to include:
*what is a LiveCD
*what is on the cd
**pointer to Fedora docs
**pointer to App docs
**pointer to CC docs
*instructions about how to open applications
*how to save
*how to quit?

==== how to access cc content ====
*cc icons on the desktop - utilize icons for the content categories (audio, video, text, image, education)
* digging deeper - how do we provide more examples? - possibly through the inclusion of examples of how users can share/remix/reuse content using cc - users can click on these icons to pull up a webpage that explains more

=== Distribution Options ===

We will investigate options for getting the CDs into the hands of the libraries we wish to target. While we wish to provide a quality LiveContent CD to the most libraries we can, we realize that mass mailing may not be the best way to accomplish this distribution goal, especially since this may be considered a type of spamming. Ideas other than mailing include hosting the contents online and doing outreach to libraries and other interested parties through a widespread press release, listservs, hand out at events, or get an in through professional organizations like the American Library Association.

While we are working towards a deliverable LiveContent CD by August 8, further exploration of a dynamic, automated system should be examined. This type of system could be automated to pull updated content from various sources , current application versions and OS patches and build a CD extremely easily. In this way, users could download the most current build at any time.

During development, we hope to provide preliminary builds and demos that we can send to various organization and libraries so that they can review the LiveContent CD and provide input for further development. Later reviews hopefully will be published in numerous ALA publications. Reviews could be sent with the CD in the mailing so that there is neutral positive influence behind the CD.

==== Resources ====

===== Groups =====

*OCLC
**http://www.oclc.org/default.htm
**http://www.oclc.org/research/staff/default.htm
**http://www.oclc.org/research/software/default.htm
**http://www.oclc.org/research/software/opensource.htm

*American Library Association http://www.ala.org

*Library Information Technology Association (LITA) http://www.lita.org

*Open Source Systems interest group http://www.ala.org/ala/lita/litamembership/litaigs/opensourcesystem/opensourcesystems.cfm

*OpenOffice http://marketing.openoffice.org/ and http://distribution.openoffice.org/

===== People =====

*Jack Aboutboul - Redhat mailto:jaa@redhat.com - Redhat will provide the themeing and customized builds of the CDs containing the OS, open source apps, Worldlabel documentation, CC content

*Jonathan Roberts - Free Me DVD - http://questionsplease.org/freeme/

*Mr. Alex Choong of Innotech Resources Pte Ltd (worldlabel.com.sg) will cover the cost of duplication of master Library CD. 8000 to 10000pcs with jewel box or sleedve. He wants will also implement a program in Singapore and Malaysia to distribute the CD to libraries. He mentioned wanting reference to this in press releases.

*project managers for oo marketing: john mccressh-mailto:jpmcc@openoffice.org, cristin driga-mailto:cdriga@openoffice.org
*Mr. Louis Suarez-Potts (Community Manager): mailto:luispo@gmail.com
*distribution-mailto:cdrom@distribution.openoffice.org

*Simon Spero at Sun in North Carolina, who might be willing to provide server space to maintain a dynamic build system

*John Rutherford of Lita/ALA Chairman of Opensource for Lita - IT division of ALA
**http://www.ala.org/ala/lita/litamembership/litacommittees/roster.cfm?committee=lit-igopens
**mailto:jrutherford @ wayne.edu
**Phone: (313) 577-0367
**will be at ALA conference in Washington DC end of June

*David Bretthauer
**http://www.lita.org/ala/lita/litapublications/ital/2101bretthauer.cfm, can be a big help, especially giving ideas which libraries to target for mailings and other stuff.
**mailto:Dave.Bretthauer@uconn.edu
**Tel: 860-486-6494

*Ms. Carrie Russell mailto:crussell@alawash.org
**Copyright Specialist, ALA, Office for Information Technology Policy

===== Reading =====

*ALA public library funding & technology access study
**http://www.ala.org/ala/ors/publiclibraryfundingtechnologyaccessstudy/pullibfunandtechaccstudy.htm
*public libraries and the internet
**http://www.ii.fsu.edu/plinternet_findings.cfm
*http://www.infomotions.com/musings/ossnlibraries-workshop/ossnlibraries-workshop.html
*http://www.newsforge.com/article.pl?sid=03/12/14/1545216&mode=thread&tid=132&tid=151&tid=82
*http://webjunction.org/do/DisplayContent?id=1216
*Article on Open Source in libaries by Gates Foundation: http://webjunction.org/do/DisplayContent?id=734
*Abstract by Siobhan Stevenson, an assistant professor at the Faculty of Information Studies University of Toronto http://www.firstmonday.org/issues/issue12_5/stevenson/index.html

*information on licensing issues for libraries: - http://www.librarycopyright.net/

===== LiveCD Examples =====

* [http://debian-live.alioth.debian.org/ Debian Live] - Debian LiveCDs
* [http://www.knoppix.org/ KNOPPIX] - Well-known LiveCD
* [http://www.slax.org/ Slax] - Slackware-based LiveCD
* [http://www.ubuntu.com/ Ubuntu] - Popular LiveCD
* [http://questionsplease.org/freeme Free Me] - Live DVD promoting free culture in the same way

===== LiveCD Resources =====

* [http://debian-live.alioth.debian.org/ Debian Live]
* [http://www.frozentech.com/content/livecd.php Live CD List] - Long List of LiveCDs
* [http://www.livedistro.org LiveDistro] - [http://www.livedistro.org/taxonomy/term/378/list Build Tools], [http://www.livedistro.org/taxonomy/term/370/list Howtos], [http://www.livedistro.org/vocabulary/18/list Releases]
* [http://reconstructor.aperantis.com/ Reconstructor] - Remaster Ubuntu LiveCDs
* [http://en.wikipedia.org/wiki/Comparison_of_Linux_LiveDistros Wikipedia Linux LiveDistro Comparison]
* [http://en.wikipedia.org/wiki/LiveCD Wikipedia LiveCD]
* [http://uck.sourceforge.net/ Ubuntu Customization Kit] - Make custom Ubuntu LiveCDs
* [http://revisor.fedoraunity.org/ Revisor] - Graphical tool for creating Fedora Live CDs/DVDs/USBs and installation media

==== future ====

*Researching 3 libraries in Putnam County, N.Y. in upscale districts, the 3 libraries had Openoffice.org, Firefox and Gimp installed. Further research in under privileged areas will be done. Visited private library which relies on Donations in Cold Springs, NY. Had no FOSS installed and where extremely receptive to the CD idea.

*how can we expand the idea to more libraries, and which are the best to target
*school integration? k-12, universities?

LiveContent

2007-07-20T01:44:50Z

LuisVilla: /* interface */ - remove some content.

[[Category:Technology]]
[[Category:Developer Challenges]]
[[Category:Developer]]
[[Category:freesoftware]]
[[Category:opensource]]
[[Category:ccLiveCD]]
[[Category:LiveContent]]

LiveContent is an umbrella idea which aims to connect and expand Creative Commons and open source communities. LiveContent works to identify creators and content providers working to share their creations more easily with others. LiveContent works to support developers and others who build better technology to distribute these works. LiveContent is up-to-the-minute creativity, "alive" by being licensed Creative Commons, which allows others to better interact with the content.

LiveContent can be delivered in a variety of ways. The first incarnation of LiveContent will deliver content as a LiveCD. LiveCDs are equivalent to what is called a [http://en.wikipedia.org/wiki/LiveDistro LiveDistro]. LiveCDs have traditionally been a vehicle to test an operating system or applications live. Operating systems and/or applications are directly booted from a CD or other type of media without needing to install the actual software on a machine. LiveContent aims to add value to LiveDistros by providing dynamically-generated content that can be added

== Contribute! ==

Creative Commons encourages others to provide ideas, feedback, comments and connections to other projects on this wiki page. There are many ways to contribute:

#Sign up for an account on this wiki and begin adding to the community - your knowledge, ideas and contributions are welcome
#IRC - Channel #CC at http://irc.freenode.net - general chatter from CC-ers, affiliates, guests - http://wiki.creativecommons.org/IRC
#cc-devel listserv - Creative Commons developers email list - http://wiki.creativecommons.org/Mailing_Lists

==Roadmap==

=== June 11===
* Brainstorming "best-of" CC-licensed content to include with the LiveCD
* Connect with other organizations - ALA, LITA, FOSS
* blog post about the project

===June 18===
* (DONE) talk to scott about helping us with builds with the correct sizing
* trying out different spins (tvol)
* bug jon to get test computer (tvol)

===June 25===
* figure out packaging of physical CD (cardboard insert/cd burns/how many/how long it will take to get manufactured/how much) (tvol + alex))
** (DONE) need to schedule meeting with alex for this week (Monday)
** Explaining CC on the packaging
* make public web page requirements on the wiki (tvol)
** (live.creativecommons.org or creativecommons.org/livecontent or creativecommons.org/live ... maybe for now just redirect to wiki page) (tvol)
** NOTECH: just clean up this wiki page (tvol)
* get the automated fedora build system working! (tannewt)

===July 2===
* Have daily builds running on redhat infrastructure (tannewt)
* planning what docs we need to collect for documentation for Fedora, apps, CC-licenses (tvol)
**pull from documentation on sites--don't reinvent the wheel, utilize wikis, but try to distill important info, especially for new users
**we want the most of these to be present as documentation within the cd, not in print
* conceptualize how to have auto-curated packages (pick one package in each media) (tannewt/tvol) - LiveContent takes off
** what are the top [[Content_Curators|Content Curators]] to have, one each for audio, video, image, and text, education. (tvol)
** develop icons for each of these categories? (alex?)

===July 9===
* have basic liveCD build completed (tannewt)

===July 16===

* Have all top auto-curated packages building on redhat infrastructure (tannewt)
* Test out auto-curated packages and communicate with tannewt (tvol)

===July 23===
* (HIGH PRIORITY) Send off CD for printing early week
*build up steam for the release
*library distribution options
**how many will get sent out?
**which libraries?

===July 30===
*press release about the project -work with worldlabel, redhat

===August 6===
*LiveCD rollout at Linuxworld - San Francisco

===August 8th===
*LiveCD rollout CC Salon - San Francisco

== Formats for distribution of LiveContent==

=== USB ===
The LiveContent could also be made to fit onto a usb stick so that it can be plugged into computers and boot straight into Linux and/or have Creative Commons licensed content on this thumbdrive.

=== DVD ===
The Free Me project has already produced a [http://questionsplease.org/freeme live DVD] with almost exactly the same ideas behind it. More than willing to lend a hand with this :D. Contact me at [mailto:jonathan.roberts.uk@googlemail.com] if you think I could be of use.

=== CD ===
We're currently working on creating an ISO image for a bootable system that would be filled with free open source software (FOSS) and CC-licensed content. Creative Commons will team with [http://fedoraproject.org Fedora] (technical support) and [http://www.worldlabel.com/ Worldlabel.com] (development and distribution support) in order to produce a LiveCD.

==ccLiveContent v1.0 - testing feedback==

*Please help CC make LiveContent the best it can be! Provide feedback under the following categories, or create your own!

===interface===
* desktop icons look like part of the background- they should somehow be raised or otherwise be made to look like an icon, rather than part of the background.
* not clear that using two desktops makes sense; just one more thing for people to click on and be confused by. Make it only one desktop by default, and remove the applet from the panel.
* make CC the default search in FF.
* would remove DOM Inspector plugin from FF, and add the MozCC plugin.
* why OpenOffice? Abiword and Gnumeric fit onto a liveCD much, much better- could fit another several dozen megs of content, at least, if you made that swap.
* if there is a global CC ical file, the calendar should be subscribed to it so that it shows up in the calendar in the panel clock.
* I'd remove gnome-terminal, at least from the final build. No need to have it clutter up the iso or the menus.
* folders that are 'bookmarked' show up in the 'Places' menus; would be good to bookmark the various Audio/Video/etc. folders, I think.
* nautilus thumbnails certain media types. The thumbnails should be pre-generated so that there isn't excessive drive access and clock icons when people open the folders for the first time. (They are in .thumbnails, I believe.)
* nautilus can put icons on individual files. I suggest that perhaps nautilus should include icons representing the licenses, and then each media/content file can have the license represented as an icon on the file. (Either as a supplement to, or a replacement for, the ugly license.txt file. The license.txt can be hidden with by placing it in .hidden, as in http://svn.gnome.org/viewcvs/livecd-project/trunk/locales/en_US/home/Desktop/Images%20from%20GNOME%20community%20events/.hidden?view=markup)
* nautilus can reorder and remember the order of files; would be good to order the content directories something like content / web links / license.txt. (That information is stored in ~/.nautilus/metafiles/ if you need to back it up.)
* the pictures should be titled with names/author ('foo by Steve Bar.jpg'), instead of 1.jpg, 2.jpg, etc.
* web icons should have the globe replaced with the sites favico or something like it. I believe the same trick as previously can be used for that.

===content (audio/video/image/text/education)===

===proposed additions/deletions to content/applications===

===bugs===

*wireless is not supported on all machines
*system time is incorrect
*is there printing support?

===comments/questions===

==ccLiveContent v2.0 - Libraries==

=== Rationale ===

We believe that the LiveContent CD can be a gateway distribution device to test the waters of using free open source software within library settings. It will also help to spread the message about Creative Commons and provide examples of different media that has been licensed under Creative Commons. We wish to promote network effects for open source in general - get more people involved with supporting FOSS, CC.

=== Target ===

Our first LiveContent CD will be created for librarians to test for public terminals at libraries. The object is to get as many libraries to install Free and Open Source Software (FOSS) on their current systems. We will be aiming the implementation at librarians and library administrators.

We strongly believe that libraries are a great way to plant seeds in the community to help the FOSS movement expand. This project will help bring more awareness to open source by providing an example of an operating system and free open source applications that could be implemented on library patron terminals. If the ideas can catch on, the long-range effects might be that libraries would begin to implement free open source software on machines permanently, thus providing a wealth of benefits both to patrons in terms of a more free computing environment and severing the long-standing ties between libraries and proprietary software license fees.

At this time, it seems that CDs provide the best media format that is accessible to most library computer terminals.

=== potential benefits ===

*libraries
**save money on proprietary software licensing - total cost of ownership (tco) is less
**libraries can be seen as cutting edge in adoption of open source
**more control over computing environment
**can test on machines without installing
**can also install directly from a desktop image
**most productivity and creativity applications have a free open source counterpart
**increase services to user by offering more software

=== potential concerns ===

*public libraries vs academic libraries - public libraries have less resources, less staff time to examine new products and test out - at the same time FOSS might most benefit small public libraries, especially rural
*academic libraries are often equipped for more research, and might be better geared towards having the resources for testing and future development
*what kinds of agreements do libraries have with software providers now, if any?
*make the cds very intuitive, well-labeled, good supporting documentation - fedora has a lot of good documentation, +/- of liveCD
*will we only make spins for i386? - probably the architecture of most library terminal machines, unless some use older macs - ppc
*how do we distribute without spamming?
*will libraries trust what we send to them?
*will libraries notice it or have time to look at it?
*less to do with the software and more to do with presentation and documentation
*focus on low income areas, rural?
*will CC put on material that covers all the different licenses? or least restrictive? - attribution only
*different libraries have different budgets which allow for a vast range in hardware and training
*The mailing will have a mail back questionaire asking did they install software and other general questions. - rethink this idea due to spamming/response issues? - think about other ways to gather feedback
*what about adding the CDs to library collections? - might be a good way for people to install or use at home, but doesn't align too well with the applications and content becoming obsolete
*accessibility
**http://ui.openoffice.org/accessibility/disabilities.html
**http://developer.gnome.org/projects/gap/at-types.html

=== What is the current landscape for library computing? ===

*at San Francisco Public Library (SFPL) main branch, there are two types of computer terminals:
**those that are used solely for card catalog lookup - no other features provided
**those where patrons can access the internet (via internet explorer) and use the Microsoft Office 2003 suite (Word, Excel, Powerpoint) - there are no other applications that are accessible through the tailored, limited-view interface

===Proposed LiveCD Contents ===

==== Fedora 7 ====
Fedora 7 is the Linux operating system that will be running live from the CD. Fedora 7 can be customized by creating "spins." Spins are custom builds of the CD with applications and features that meet the users' needs. A specific spin can be documented by including a "build date" on the CD and its packaging. Any user who has installed Fedora on their machine can spin custom LiveCDs.

Documentation at http://fedoraproject.org/wiki/FedoraLiveCD/

There are differnt ways to create LiveCDs with Fedora:
*Graphical User Interface (GUI) - Revisor (comes loaded in Fedora)
*Command Line Interface (CLI) - livecd-creator (creates liveCDs), [https://hosted.fedoraproject.org/projects/pungi Pungi] (creates installation disks)
*users who wish to contribute to Fedora's internal build system need an account - create account @ http://admin.fedoraproject.org/accounts
*Koji is Fedora's server that tracks recent builds - http://koji.fedoraproject.org
*testing notes:
**fedora 7 LiveCD Gnome runs extremely slow on a 256MB test machine
**note - productivity and creativity apps cannot be installed at terminals without first installing Fedora - aka liveCD doesn't support application installs before full OS install

==== FOSS Productivity/creativity/entertainment apps ====

*[http://www.openoffice.org Openoffice] - Complete version
*[http://www.mozilla.com/en-US/firefox/ FireFox] - web browser
*[http://www.gimp.org/ Gimp] - raster graphics editor
*[http://www.inkscape.org/ Inkscape] - vector graphics editor
*[http://www.worldlabel.com Worldlabel.com] Blank Opendocument Format Label Templates and collection of pre-designed label templates: address, shipping, filing, CD - licensed public domain
*Collection of clipart from [http://www.openclipart.org Open Clip Art Library]?
*Totem - audio and video viewer
*gThum - image viewer
*Evince PDF Viewer. Possible PDF editor, Openoffice has excellent PDF export
*SVG Viewer - Gimp

*For Kids (possible inclusion)
**http://www.linuxforkids.org/
**[http://www.tuxpaint.org/ Tuxpaint]
**[http://gcompris.net/-en- qcompris]
**[http://tuxtype.sourceforge.net Tuxtype]
**[http://www.schooltool.org/ Schooltool]

*A good idea might be to include some promotional information like http://why.openoffice.org/why_nfp.html but also for all the other applications, Why Gimp, Why Inscape, etc.

*note that all these FOSS applications are also available for installation on machines running proprietary operating systems (windows, osx), not just linux machines

==== Creative Commons-licensed content ====
We want to provide examples from each category (audio, video, text, image, education) to showcase on the LiveContent CD. We will develop a system that can automatically pull top content from the sites that we choose (and these sites can change as well).

We'll feature one website/service/cc-content provider from each of the 5 categories for this initial run. We should provide examples of cc-licensed materials from each. don't know how many--we'll see how much room is left on the cd:

*audio - jamendo
**[[Audio#Featured_Audio_Sites|more audio]]
*video - blip.tv
**[[Video#Featured_Video_Sites|more video]]
*image - flickr
**[[Image#Featured_Image_Sites|more image]]
*text - lulu
**[[Text#Featured_Text_sites|more text]]
*education - connexions
**[[Education#Featured_Education_sites|more education]]

*[[Multiple_Formats|even more]]

*what about cc-videos?
*possible inclusion of a CC plugin pre-installed in Openoffice.org
*inclusion of CC plug-in for Firefox?

==== Documentation ====

*http://opendocumentfellowship.org/
*explanation of licenses like from the Free Me DVD - http://questionsplease.org/freeme/free-culture/the-licenses/
*obvious CC explanations - to be displayed in an initial pop-up browser page?
**this should mirror the info we have on the inside of the cd packaging - a redirect to the visual on the website
**http://creativecommons.org/about/licenses/meet-the-licenses
**http://creativecommons.org/about/licenses
* tutorials
**http://www.tutorialsforopenoffice.org/
**http://docs.fedoraproject.org/
**http://www.gimp.org/docs/
**http://www.inkscape.org/doc/index.php

=== Interface and Display Options ===

==== Themeing ====
*Gnome with cc desktop, content icons, share/reuse/remix icons

==== Initial Pop-up Screen ====
This screen will be loaded upon booting the CD to welcome users and give an overview of the LiveCD.

Some things to include:
*what is a LiveCD
*what is on the cd
**pointer to Fedora docs
**pointer to App docs
**pointer to CC docs
*instructions about how to open applications
*how to save
*how to quit?

==== how to access cc content ====
*cc icons on the desktop - utilize icons for the content categories (audio, video, text, image, education)
* digging deeper - how do we provide more examples? - possibly through the inclusion of examples of how users can share/remix/reuse content using cc - users can click on these icons to pull up a webpage that explains more

=== Distribution Options ===

We will investigate options for getting the CDs into the hands of the libraries we wish to target. While we wish to provide a quality LiveContent CD to the most libraries we can, we realize that mass mailing may not be the best way to accomplish this distribution goal, especially since this may be considered a type of spamming. Ideas other than mailing include hosting the contents online and doing outreach to libraries and other interested parties through a widespread press release, listservs, hand out at events, or get an in through professional organizations like the American Library Association.

While we are working towards a deliverable LiveContent CD by August 8, further exploration of a dynamic, automated system should be examined. This type of system could be automated to pull updated content from various sources , current application versions and OS patches and build a CD extremely easily. In this way, users could download the most current build at any time.

During development, we hope to provide preliminary builds and demos that we can send to various organization and libraries so that they can review the LiveContent CD and provide input for further development. Later reviews hopefully will be published in numerous ALA publications. Reviews could be sent with the CD in the mailing so that there is neutral positive influence behind the CD.

==== Resources ====

===== Groups =====

*OCLC
**http://www.oclc.org/default.htm
**http://www.oclc.org/research/staff/default.htm
**http://www.oclc.org/research/software/default.htm
**http://www.oclc.org/research/software/opensource.htm

*American Library Association http://www.ala.org

*Library Information Technology Association (LITA) http://www.lita.org

*Open Source Systems interest group http://www.ala.org/ala/lita/litamembership/litaigs/opensourcesystem/opensourcesystems.cfm

*OpenOffice http://marketing.openoffice.org/ and http://distribution.openoffice.org/

===== People =====

*Jack Aboutboul - Redhat mailto:jaa@redhat.com - Redhat will provide the themeing and customized builds of the CDs containing the OS, open source apps, Worldlabel documentation, CC content

*Jonathan Roberts - Free Me DVD - http://questionsplease.org/freeme/

*Mr. Alex Choong of Innotech Resources Pte Ltd (worldlabel.com.sg) will cover the cost of duplication of master Library CD. 8000 to 10000pcs with jewel box or sleedve. He wants will also implement a program in Singapore and Malaysia to distribute the CD to libraries. He mentioned wanting reference to this in press releases.

*project managers for oo marketing: john mccressh-mailto:jpmcc@openoffice.org, cristin driga-mailto:cdriga@openoffice.org
*Mr. Louis Suarez-Potts (Community Manager): mailto:luispo@gmail.com
*distribution-mailto:cdrom@distribution.openoffice.org

*Simon Spero at Sun in North Carolina, who might be willing to provide server space to maintain a dynamic build system

*John Rutherford of Lita/ALA Chairman of Opensource for Lita - IT division of ALA
**http://www.ala.org/ala/lita/litamembership/litacommittees/roster.cfm?committee=lit-igopens
**mailto:jrutherford @ wayne.edu
**Phone: (313) 577-0367
**will be at ALA conference in Washington DC end of June

*David Bretthauer
**http://www.lita.org/ala/lita/litapublications/ital/2101bretthauer.cfm, can be a big help, especially giving ideas which libraries to target for mailings and other stuff.
**mailto:Dave.Bretthauer@uconn.edu
**Tel: 860-486-6494

*Ms. Carrie Russell mailto:crussell@alawash.org
**Copyright Specialist, ALA, Office for Information Technology Policy

===== Reading =====

*ALA public library funding & technology access study
**http://www.ala.org/ala/ors/publiclibraryfundingtechnologyaccessstudy/pullibfunandtechaccstudy.htm
*public libraries and the internet
**http://www.ii.fsu.edu/plinternet_findings.cfm
*http://www.infomotions.com/musings/ossnlibraries-workshop/ossnlibraries-workshop.html
*http://www.newsforge.com/article.pl?sid=03/12/14/1545216&mode=thread&tid=132&tid=151&tid=82
*http://webjunction.org/do/DisplayContent?id=1216
*Article on Open Source in libaries by Gates Foundation: http://webjunction.org/do/DisplayContent?id=734
*Abstract by Siobhan Stevenson, an assistant professor at the Faculty of Information Studies University of Toronto http://www.firstmonday.org/issues/issue12_5/stevenson/index.html

*information on licensing issues for libraries: - http://www.librarycopyright.net/

===== LiveCD Examples =====

* [http://debian-live.alioth.debian.org/ Debian Live] - Debian LiveCDs
* [http://www.knoppix.org/ KNOPPIX] - Well-known LiveCD
* [http://www.slax.org/ Slax] - Slackware-based LiveCD
* [http://www.ubuntu.com/ Ubuntu] - Popular LiveCD
* [http://questionsplease.org/freeme Free Me] - Live DVD promoting free culture in the same way

===== LiveCD Resources =====

* [http://debian-live.alioth.debian.org/ Debian Live]
* [http://www.frozentech.com/content/livecd.php Live CD List] - Long List of LiveCDs
* [http://www.livedistro.org LiveDistro] - [http://www.livedistro.org/taxonomy/term/378/list Build Tools], [http://www.livedistro.org/taxonomy/term/370/list Howtos], [http://www.livedistro.org/vocabulary/18/list Releases]
* [http://reconstructor.aperantis.com/ Reconstructor] - Remaster Ubuntu LiveCDs
* [http://en.wikipedia.org/wiki/Comparison_of_Linux_LiveDistros Wikipedia Linux LiveDistro Comparison]
* [http://en.wikipedia.org/wiki/LiveCD Wikipedia LiveCD]
* [http://uck.sourceforge.net/ Ubuntu Customization Kit] - Make custom Ubuntu LiveCDs
* [http://revisor.fedoraunity.org/ Revisor] - Graphical tool for creating Fedora Live CDs/DVDs/USBs and installation media

==== future ====

*Researching 3 libraries in Putnam County, N.Y. in upscale districts, the 3 libraries had Openoffice.org, Firefox and Gimp installed. Further research in under privileged areas will be done. Visited private library which relies on Donations in Cold Springs, NY. Had no FOSS installed and where extremely receptive to the CD idea.

*how can we expand the idea to more libraries, and which are the best to target
*school integration? k-12, universities?

LiveContent

2007-07-20T01:43:57Z

LuisVilla: /* interface */ - a whole bunch of stuff, some of which should be elsewhere.

[[Category:Technology]]
[[Category:Developer Challenges]]
[[Category:Developer]]
[[Category:freesoftware]]
[[Category:opensource]]
[[Category:ccLiveCD]]
[[Category:LiveContent]]

LiveContent is an umbrella idea which aims to connect and expand Creative Commons and open source communities. LiveContent works to identify creators and content providers working to share their creations more easily with others. LiveContent works to support developers and others who build better technology to distribute these works. LiveContent is up-to-the-minute creativity, "alive" by being licensed Creative Commons, which allows others to better interact with the content.

LiveContent can be delivered in a variety of ways. The first incarnation of LiveContent will deliver content as a LiveCD. LiveCDs are equivalent to what is called a [http://en.wikipedia.org/wiki/LiveDistro LiveDistro]. LiveCDs have traditionally been a vehicle to test an operating system or applications live. Operating systems and/or applications are directly booted from a CD or other type of media without needing to install the actual software on a machine. LiveContent aims to add value to LiveDistros by providing dynamically-generated content that can be added

== Contribute! ==

Creative Commons encourages others to provide ideas, feedback, comments and connections to other projects on this wiki page. There are many ways to contribute:

#Sign up for an account on this wiki and begin adding to the community - your knowledge, ideas and contributions are welcome
#IRC - Channel #CC at http://irc.freenode.net - general chatter from CC-ers, affiliates, guests - http://wiki.creativecommons.org/IRC
#cc-devel listserv - Creative Commons developers email list - http://wiki.creativecommons.org/Mailing_Lists

==Roadmap==

=== June 11===
* Brainstorming "best-of" CC-licensed content to include with the LiveCD
* Connect with other organizations - ALA, LITA, FOSS
* blog post about the project

===June 18===
* (DONE) talk to scott about helping us with builds with the correct sizing
* trying out different spins (tvol)
* bug jon to get test computer (tvol)

===June 25===
* figure out packaging of physical CD (cardboard insert/cd burns/how many/how long it will take to get manufactured/how much) (tvol + alex))
** (DONE) need to schedule meeting with alex for this week (Monday)
** Explaining CC on the packaging
* make public web page requirements on the wiki (tvol)
** (live.creativecommons.org or creativecommons.org/livecontent or creativecommons.org/live ... maybe for now just redirect to wiki page) (tvol)
** NOTECH: just clean up this wiki page (tvol)
* get the automated fedora build system working! (tannewt)

===July 2===
* Have daily builds running on redhat infrastructure (tannewt)
* planning what docs we need to collect for documentation for Fedora, apps, CC-licenses (tvol)
**pull from documentation on sites--don't reinvent the wheel, utilize wikis, but try to distill important info, especially for new users
**we want the most of these to be present as documentation within the cd, not in print
* conceptualize how to have auto-curated packages (pick one package in each media) (tannewt/tvol) - LiveContent takes off
** what are the top [[Content_Curators|Content Curators]] to have, one each for audio, video, image, and text, education. (tvol)
** develop icons for each of these categories? (alex?)

===July 9===
* have basic liveCD build completed (tannewt)

===July 16===

* Have all top auto-curated packages building on redhat infrastructure (tannewt)
* Test out auto-curated packages and communicate with tannewt (tvol)

===July 23===
* (HIGH PRIORITY) Send off CD for printing early week
*build up steam for the release
*library distribution options
**how many will get sent out?
**which libraries?

===July 30===
*press release about the project -work with worldlabel, redhat

===August 6===
*LiveCD rollout at Linuxworld - San Francisco

===August 8th===
*LiveCD rollout CC Salon - San Francisco

== Formats for distribution of LiveContent==

=== USB ===
The LiveContent could also be made to fit onto a usb stick so that it can be plugged into computers and boot straight into Linux and/or have Creative Commons licensed content on this thumbdrive.

=== DVD ===
The Free Me project has already produced a [http://questionsplease.org/freeme live DVD] with almost exactly the same ideas behind it. More than willing to lend a hand with this :D. Contact me at [mailto:jonathan.roberts.uk@googlemail.com] if you think I could be of use.

=== CD ===
We're currently working on creating an ISO image for a bootable system that would be filled with free open source software (FOSS) and CC-licensed content. Creative Commons will team with [http://fedoraproject.org Fedora] (technical support) and [http://www.worldlabel.com/ Worldlabel.com] (development and distribution support) in order to produce a LiveCD.

==ccLiveContent v1.0 - testing feedback==

*Please help CC make LiveContent the best it can be! Provide feedback under the following categories, or create your own!

===interface===
* desktop icons look like part of the background- they should somehow be raised or otherwise be made to look like an icon, rather than part of the background.
* not clear that using two desktops makes sense; just one more thing for people to click on and be confused by. Make it only one desktop by default, and remove the applet from the panel.
* make CC the default search in FF.
* would remove DOM Inspector plugin from FF, and add the MozCC plugin.
* why OpenOffice? Abiword and Gnumeric fit onto a liveCD much, much better- could fit another several dozen megs of content, at least, if you made that swap.
* if there is a global CC ical file, the calendar should be subscribed to it so that it shows up in the calendar in the panel clock.
* I'd remove gnome-terminal, at least from the final build. No need to have it clutter up the iso or the menus.
* folders that are 'bookmarked' show up in the 'Places' menus; would be good to bookmark the various Audio/Video/etc. folders, I think.
* nautilus thumbnails certain media types. The thumbnails should be pre-generated so that there isn't excessive drive access and clock icons when people open the folders for the first time. (They are in .thumbnails, I believe.)
* nautilus can put icons on individual files. I suggest that perhaps nautilus should include icons representing the licenses, and then each media/content file can have the license represented as an icon on the file. (Either as a supplement to, or a replacement for, the ugly license.txt file. The license.txt can be hidden with by placing it in .hidden, as in http://svn.gnome.org/viewcvs/livecd-project/trunk/locales/en_US/home/Desktop/Images%20from%20GNOME%20community%20events/.hidden?view=markup)
* nautilus can reorder and remember the order of files; would be good to order the content directories something like content / web links / license.txt. (That information is stored in ~/.nautilus/metafiles/ if you need to back it up.)
* the pictures should be titled with names/author ('foo by Steve Bar.jpg'), instead of 1.jpg, 2.jpg, etc.
* web icons should have the globe replaced with the sites favico or something like it. I believe the same trick as previously can be used for that.
* no Free Culture in Texts?
* in Education, probably a link to Curriki would be good. Ditto perhaps http://www.introecon.com/ ?
* perhaps the various CC comics, both http://www.law.duke.edu/cspd/comics/ and http://creativecommons.org/about/licenses/comics1/ ?

===content (audio/video/image/text/education)===

===proposed additions/deletions to content/applications===

===bugs===

*wireless is not supported on all machines
*system time is incorrect
*is there printing support?

===comments/questions===

==ccLiveContent v2.0 - Libraries==

=== Rationale ===

We believe that the LiveContent CD can be a gateway distribution device to test the waters of using free open source software within library settings. It will also help to spread the message about Creative Commons and provide examples of different media that has been licensed under Creative Commons. We wish to promote network effects for open source in general - get more people involved with supporting FOSS, CC.

=== Target ===

Our first LiveContent CD will be created for librarians to test for public terminals at libraries. The object is to get as many libraries to install Free and Open Source Software (FOSS) on their current systems. We will be aiming the implementation at librarians and library administrators.

We strongly believe that libraries are a great way to plant seeds in the community to help the FOSS movement expand. This project will help bring more awareness to open source by providing an example of an operating system and free open source applications that could be implemented on library patron terminals. If the ideas can catch on, the long-range effects might be that libraries would begin to implement free open source software on machines permanently, thus providing a wealth of benefits both to patrons in terms of a more free computing environment and severing the long-standing ties between libraries and proprietary software license fees.

At this time, it seems that CDs provide the best media format that is accessible to most library computer terminals.

=== potential benefits ===

*libraries
**save money on proprietary software licensing - total cost of ownership (tco) is less
**libraries can be seen as cutting edge in adoption of open source
**more control over computing environment
**can test on machines without installing
**can also install directly from a desktop image
**most productivity and creativity applications have a free open source counterpart
**increase services to user by offering more software

=== potential concerns ===

*public libraries vs academic libraries - public libraries have less resources, less staff time to examine new products and test out - at the same time FOSS might most benefit small public libraries, especially rural
*academic libraries are often equipped for more research, and might be better geared towards having the resources for testing and future development
*what kinds of agreements do libraries have with software providers now, if any?
*make the cds very intuitive, well-labeled, good supporting documentation - fedora has a lot of good documentation, +/- of liveCD
*will we only make spins for i386? - probably the architecture of most library terminal machines, unless some use older macs - ppc
*how do we distribute without spamming?
*will libraries trust what we send to them?
*will libraries notice it or have time to look at it?
*less to do with the software and more to do with presentation and documentation
*focus on low income areas, rural?
*will CC put on material that covers all the different licenses? or least restrictive? - attribution only
*different libraries have different budgets which allow for a vast range in hardware and training
*The mailing will have a mail back questionaire asking did they install software and other general questions. - rethink this idea due to spamming/response issues? - think about other ways to gather feedback
*what about adding the CDs to library collections? - might be a good way for people to install or use at home, but doesn't align too well with the applications and content becoming obsolete
*accessibility
**http://ui.openoffice.org/accessibility/disabilities.html
**http://developer.gnome.org/projects/gap/at-types.html

=== What is the current landscape for library computing? ===

*at San Francisco Public Library (SFPL) main branch, there are two types of computer terminals:
**those that are used solely for card catalog lookup - no other features provided
**those where patrons can access the internet (via internet explorer) and use the Microsoft Office 2003 suite (Word, Excel, Powerpoint) - there are no other applications that are accessible through the tailored, limited-view interface

===Proposed LiveCD Contents ===

==== Fedora 7 ====
Fedora 7 is the Linux operating system that will be running live from the CD. Fedora 7 can be customized by creating "spins." Spins are custom builds of the CD with applications and features that meet the users' needs. A specific spin can be documented by including a "build date" on the CD and its packaging. Any user who has installed Fedora on their machine can spin custom LiveCDs.

Documentation at http://fedoraproject.org/wiki/FedoraLiveCD/

There are differnt ways to create LiveCDs with Fedora:
*Graphical User Interface (GUI) - Revisor (comes loaded in Fedora)
*Command Line Interface (CLI) - livecd-creator (creates liveCDs), [https://hosted.fedoraproject.org/projects/pungi Pungi] (creates installation disks)
*users who wish to contribute to Fedora's internal build system need an account - create account @ http://admin.fedoraproject.org/accounts
*Koji is Fedora's server that tracks recent builds - http://koji.fedoraproject.org
*testing notes:
**fedora 7 LiveCD Gnome runs extremely slow on a 256MB test machine
**note - productivity and creativity apps cannot be installed at terminals without first installing Fedora - aka liveCD doesn't support application installs before full OS install

==== FOSS Productivity/creativity/entertainment apps ====

*[http://www.openoffice.org Openoffice] - Complete version
*[http://www.mozilla.com/en-US/firefox/ FireFox] - web browser
*[http://www.gimp.org/ Gimp] - raster graphics editor
*[http://www.inkscape.org/ Inkscape] - vector graphics editor
*[http://www.worldlabel.com Worldlabel.com] Blank Opendocument Format Label Templates and collection of pre-designed label templates: address, shipping, filing, CD - licensed public domain
*Collection of clipart from [http://www.openclipart.org Open Clip Art Library]?
*Totem - audio and video viewer
*gThum - image viewer
*Evince PDF Viewer. Possible PDF editor, Openoffice has excellent PDF export
*SVG Viewer - Gimp

*For Kids (possible inclusion)
**http://www.linuxforkids.org/
**[http://www.tuxpaint.org/ Tuxpaint]
**[http://gcompris.net/-en- qcompris]
**[http://tuxtype.sourceforge.net Tuxtype]
**[http://www.schooltool.org/ Schooltool]

*A good idea might be to include some promotional information like http://why.openoffice.org/why_nfp.html but also for all the other applications, Why Gimp, Why Inscape, etc.

*note that all these FOSS applications are also available for installation on machines running proprietary operating systems (windows, osx), not just linux machines

==== Creative Commons-licensed content ====
We want to provide examples from each category (audio, video, text, image, education) to showcase on the LiveContent CD. We will develop a system that can automatically pull top content from the sites that we choose (and these sites can change as well).

We'll feature one website/service/cc-content provider from each of the 5 categories for this initial run. We should provide examples of cc-licensed materials from each. don't know how many--we'll see how much room is left on the cd:

*audio - jamendo
**[[Audio#Featured_Audio_Sites|more audio]]
*video - blip.tv
**[[Video#Featured_Video_Sites|more video]]
*image - flickr
**[[Image#Featured_Image_Sites|more image]]
*text - lulu
**[[Text#Featured_Text_sites|more text]]
*education - connexions
**[[Education#Featured_Education_sites|more education]]

*[[Multiple_Formats|even more]]

*what about cc-videos?
*possible inclusion of a CC plugin pre-installed in Openoffice.org
*inclusion of CC plug-in for Firefox?

==== Documentation ====

*http://opendocumentfellowship.org/
*explanation of licenses like from the Free Me DVD - http://questionsplease.org/freeme/free-culture/the-licenses/
*obvious CC explanations - to be displayed in an initial pop-up browser page?
**this should mirror the info we have on the inside of the cd packaging - a redirect to the visual on the website
**http://creativecommons.org/about/licenses/meet-the-licenses
**http://creativecommons.org/about/licenses
* tutorials
**http://www.tutorialsforopenoffice.org/
**http://docs.fedoraproject.org/
**http://www.gimp.org/docs/
**http://www.inkscape.org/doc/index.php

=== Interface and Display Options ===

==== Themeing ====
*Gnome with cc desktop, content icons, share/reuse/remix icons

==== Initial Pop-up Screen ====
This screen will be loaded upon booting the CD to welcome users and give an overview of the LiveCD.

Some things to include:
*what is a LiveCD
*what is on the cd
**pointer to Fedora docs
**pointer to App docs
**pointer to CC docs
*instructions about how to open applications
*how to save
*how to quit?

==== how to access cc content ====
*cc icons on the desktop - utilize icons for the content categories (audio, video, text, image, education)
* digging deeper - how do we provide more examples? - possibly through the inclusion of examples of how users can share/remix/reuse content using cc - users can click on these icons to pull up a webpage that explains more

=== Distribution Options ===

We will investigate options for getting the CDs into the hands of the libraries we wish to target. While we wish to provide a quality LiveContent CD to the most libraries we can, we realize that mass mailing may not be the best way to accomplish this distribution goal, especially since this may be considered a type of spamming. Ideas other than mailing include hosting the contents online and doing outreach to libraries and other interested parties through a widespread press release, listservs, hand out at events, or get an in through professional organizations like the American Library Association.

While we are working towards a deliverable LiveContent CD by August 8, further exploration of a dynamic, automated system should be examined. This type of system could be automated to pull updated content from various sources , current application versions and OS patches and build a CD extremely easily. In this way, users could download the most current build at any time.

During development, we hope to provide preliminary builds and demos that we can send to various organization and libraries so that they can review the LiveContent CD and provide input for further development. Later reviews hopefully will be published in numerous ALA publications. Reviews could be sent with the CD in the mailing so that there is neutral positive influence behind the CD.

==== Resources ====

===== Groups =====

*OCLC
**http://www.oclc.org/default.htm
**http://www.oclc.org/research/staff/default.htm
**http://www.oclc.org/research/software/default.htm
**http://www.oclc.org/research/software/opensource.htm

*American Library Association http://www.ala.org

*Library Information Technology Association (LITA) http://www.lita.org

*Open Source Systems interest group http://www.ala.org/ala/lita/litamembership/litaigs/opensourcesystem/opensourcesystems.cfm

*OpenOffice http://marketing.openoffice.org/ and http://distribution.openoffice.org/

===== People =====

*Jack Aboutboul - Redhat mailto:jaa@redhat.com - Redhat will provide the themeing and customized builds of the CDs containing the OS, open source apps, Worldlabel documentation, CC content

*Jonathan Roberts - Free Me DVD - http://questionsplease.org/freeme/

*Mr. Alex Choong of Innotech Resources Pte Ltd (worldlabel.com.sg) will cover the cost of duplication of master Library CD. 8000 to 10000pcs with jewel box or sleedve. He wants will also implement a program in Singapore and Malaysia to distribute the CD to libraries. He mentioned wanting reference to this in press releases.

*project managers for oo marketing: john mccressh-mailto:jpmcc@openoffice.org, cristin driga-mailto:cdriga@openoffice.org
*Mr. Louis Suarez-Potts (Community Manager): mailto:luispo@gmail.com
*distribution-mailto:cdrom@distribution.openoffice.org

*Simon Spero at Sun in North Carolina, who might be willing to provide server space to maintain a dynamic build system

*John Rutherford of Lita/ALA Chairman of Opensource for Lita - IT division of ALA
**http://www.ala.org/ala/lita/litamembership/litacommittees/roster.cfm?committee=lit-igopens
**mailto:jrutherford @ wayne.edu
**Phone: (313) 577-0367
**will be at ALA conference in Washington DC end of June

*David Bretthauer
**http://www.lita.org/ala/lita/litapublications/ital/2101bretthauer.cfm, can be a big help, especially giving ideas which libraries to target for mailings and other stuff.
**mailto:Dave.Bretthauer@uconn.edu
**Tel: 860-486-6494

*Ms. Carrie Russell mailto:crussell@alawash.org
**Copyright Specialist, ALA, Office for Information Technology Policy

===== Reading =====

*ALA public library funding & technology access study
**http://www.ala.org/ala/ors/publiclibraryfundingtechnologyaccessstudy/pullibfunandtechaccstudy.htm
*public libraries and the internet
**http://www.ii.fsu.edu/plinternet_findings.cfm
*http://www.infomotions.com/musings/ossnlibraries-workshop/ossnlibraries-workshop.html
*http://www.newsforge.com/article.pl?sid=03/12/14/1545216&mode=thread&tid=132&tid=151&tid=82
*http://webjunction.org/do/DisplayContent?id=1216
*Article on Open Source in libaries by Gates Foundation: http://webjunction.org/do/DisplayContent?id=734
*Abstract by Siobhan Stevenson, an assistant professor at the Faculty of Information Studies University of Toronto http://www.firstmonday.org/issues/issue12_5/stevenson/index.html

*information on licensing issues for libraries: - http://www.librarycopyright.net/

===== LiveCD Examples =====

* [http://debian-live.alioth.debian.org/ Debian Live] - Debian LiveCDs
* [http://www.knoppix.org/ KNOPPIX] - Well-known LiveCD
* [http://www.slax.org/ Slax] - Slackware-based LiveCD
* [http://www.ubuntu.com/ Ubuntu] - Popular LiveCD
* [http://questionsplease.org/freeme Free Me] - Live DVD promoting free culture in the same way

===== LiveCD Resources =====

* [http://debian-live.alioth.debian.org/ Debian Live]
* [http://www.frozentech.com/content/livecd.php Live CD List] - Long List of LiveCDs
* [http://www.livedistro.org LiveDistro] - [http://www.livedistro.org/taxonomy/term/378/list Build Tools], [http://www.livedistro.org/taxonomy/term/370/list Howtos], [http://www.livedistro.org/vocabulary/18/list Releases]
* [http://reconstructor.aperantis.com/ Reconstructor] - Remaster Ubuntu LiveCDs
* [http://en.wikipedia.org/wiki/Comparison_of_Linux_LiveDistros Wikipedia Linux LiveDistro Comparison]
* [http://en.wikipedia.org/wiki/LiveCD Wikipedia LiveCD]
* [http://uck.sourceforge.net/ Ubuntu Customization Kit] - Make custom Ubuntu LiveCDs
* [http://revisor.fedoraunity.org/ Revisor] - Graphical tool for creating Fedora Live CDs/DVDs/USBs and installation media

==== future ====

*Researching 3 libraries in Putnam County, N.Y. in upscale districts, the 3 libraries had Openoffice.org, Firefox and Gimp installed. Further research in under privileged areas will be done. Visited private library which relies on Donations in Cold Springs, NY. Had no FOSS installed and where extremely receptive to the CD idea.

*how can we expand the idea to more libraries, and which are the best to target
*school integration? k-12, universities?