Difference between revisions of "LiveContent 2 0"

From Creative Commons
Jump to: navigation, search
(→‎Vision)
Line 15: Line 15:
  
 
==Technical Considerations==
 
==Technical Considerations==
−
* [http://sourceforge.net/tracker/?group_id=80503&atid=559966 bugs]
+
* [http://sourceforge.net/tracker/?group_id=80503&atid=559966 Sourceforge bug tracker for LiveContent]
 
* [[Autocurated_Packages|autocurated packaging of content]]
 
* [[Autocurated_Packages|autocurated packaging of content]]
−
* [http://pipes.yahoo.com Yahoo! Pipes]
+
* [http://spins.fedoraproject.org/ spins.fedoraproject.org hosting space]
−
* [http://spins.fedoraproject.org/ testing space over at Red Hat]
 
 
* [[LiveContent_1_0#v1.0_testing_feedback|1.0 testing feedback]]
 
* [[LiveContent_1_0#v1.0_testing_feedback|1.0 testing feedback]]
 
* branding concerns - will run by Red Hat before next release
 
* branding concerns - will run by Red Hat before next release
Line 24: Line 23:
 
==Contents==
 
==Contents==
  
−
Applications and Content running on Fedora 7
+
===Fedora 8 is the base architecture===
−
 
 
−
===Applications===
 
 
*keep most from v1.0 as base
 
*keep most from v1.0 as base
 
**OpenOffice
 
**OpenOffice
Line 116: Line 113:
 
* put content icons on the front of packaging?
 
* put content icons on the front of packaging?
  
−
==Library-specific concerns==
 
−
===LiveContent project within library settings===
 
−
* public libraries vs academic libraries vs other 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 - need to target
 
−
* 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?
 
−
**many locked into proprietary software, but not by choice - more a function of ease, what patrons expect, technical experience of staff
 
−
* make the cds very intuitive, well-labeled, good supporting documentation - fedora has a lot of good documentation
 
−
* 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 LiveContent without spamming?
 
−
* originally we had the idea that we needed to keep the distribution of LiveContent to CDs, since they are the media that is most able to be used across the board, especially at places like libraries, which have vastly different landscape of computing power - but are DVDs possible? - can fit so much more content on a DVD
 
−
* less to do with the software and more to do with presentation and documentation and usefulness
 
−
* different libraries have different budgets which allow for a vast range in hardware and training
 
−
* what about adding the CDs to library collections - ISSN numbers? - might be a good way for people or use at home, but doesn't align too well with the applications and content becoming dated
 
−
* accessibility concerns at libraries
 
−
**http://ui.openoffice.org/accessibility/disabilities.html
 
−
**http://developer.gnome.org/projects/gap/at-types.html
 
  
−
===computing environments===
+
==Distribution Options==
−
====San Francisco Public Library====
 
−
*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
 
−
 
 
−
====Ann Arbor District Library (notes from meeting with technology director)====
 
−
*thin-client public computing setup throughout the entire public district
 
−
*no disc drives at all
 
−
*still supporting floppy drives
 
−
*support plug-in USB drives
 
−
*$400 base machine running on MS terminal server (most stable environment)
 
−
*nodes are non-writable
 
−
*"commodity" computing - basic internet access, no high end applications, audio works but technically not supported
 
−
*ann arbor is one of the few libraries that are doing it this way--requires lots of up front investment
 
−
*all applications available to patrons are located on the desktop and locked down (acrobat reader, calculator, internet explorer, firefox, excel, powerpoint, word, paint, telnet ssh, wordpad)
 
−
*public terminals are used mostly for internet access, some word processing. the other apps are infrequently used
 
−
*70% of the people in Ann Arbor have computers at home
 
−
*libraries that have money can set up things like thin clients, so delivery of content through disc drives is not an option
 
−
*libraries that have less resources like smaller rural libraries have standard machines, but less tech help
 
−
*patrons might be confused about how to use the LiveCD/LiveDVD, especially since they are so used to working on windows machines
 
−
*LiveDVD might be good to add to the collection so people can check out and take to home computers
 
−
*suggestion of putting out the LiveDVD as a kit with an instructional/informational booklet
 
−
 
 
−
===Resources===
 
−
*Webjunction
 
−
*TechSoup
 
−
*MaintainIT project
 
−
*LITA
 
−
*oss4lib
 
−
*alatechsource
 
−
* "Public Libraries and the Internet 2006: Study Results and findings" report available for download [http://www.ii.fsu.edu/projectFiles/plinternet/2006/2006_plinternet.pdf here] - may provide some insight to landscape of public library terminal workstation metrics
 
−
 
 
−
==Library Testing==
 
−
We'd like to identify approximately 4 libraries in various areas of the country that would like to come on board to becomes testers for LiveContent 2.0. We'd like to do quick iterative versions of 2.0, starting at "Phase 0" to be built ASAP, with revisions being made at a distinct interval afterwards, with the final 2.0 release coming at Phase 3. Geographically, we're looking to involve a library from each of the following areas:
 
−
 
 
−
===Northeast===
 
−
*New York?
 
  
−
===Southeast===
 
−
*possibly Florida?
 
−
 
−
===Midwest===
 
−
*possbily Michigan, Wisconsin, Chicago?
 
−
 
−
===West Coast===
 
−
*San Francisco?
 
−
 
−
==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 disc 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.
 
  
 
==Future Ideas for LiveContent==
 
==Future Ideas for LiveContent==

Revision as of 16:44, 15 January 2008


Vision

LiveContent 2.0 works to address several technical aspects surrounding "Live Content." First, the project aims to develop, using the Fedora architecture, a daily build structure of the LiveContent LiveDVD. Related, 2.0 aims to generate "autocurated content." Autocurated content uses APIs and content feeds from open content providers and hosting organizations that can be used to pull down the most current, "live" open content.

We believe that the LiveContent distro can provide a useful platform that allows users to test explore free and open content and test out free, open source software. The LiveContent distro provides information and documentation about Creative Commons, the FOSS movement, and demos to how users can take advantage of the media included to re-create, re-mix and re-share content.

Technical Considerations

Contents

Fedora 8 is the base architecture

  • keep most from v1.0 as base
    • OpenOffice
    • Inkscape
    • The Gimp
    • Firefox
    • Totem
    • Evince
    • gThumb
    • Tuxpaint

CC Content

CC is working on developing a system to "autocurate" content from CC-friendly sites such as Flickr. CC tech team will take API infrastructures to be able to pull down CC-licensed content from these sites for inclusion on LiveContent 2.0 DVD. Categories may include, but not limited to:

  • Audio
  • Video
  • Text
  • Image
  • Educational resources
  • Important - how will we be able to mark these works with the appropriate CC license?
    • we'll get a README file generated with the autocurated content
  • How can we bring in other content curators such as Internet Archive, Open Content Alliance, OpenLibrary?
  • How can we work with ccLearn, OER engine?

Other Open Content

Documentation

Proper documentation about LiveContent is vital to include within the DVD. How to deliver documentation that is informative, draws people in, is not boring or too much to digest?

Start page

  • Quick soundbytes

Welcome to LiveContent 2.0

Creative Commons LiveContent is a project to spread the word about open content--multimedia materials that you can freely use, copy, and build upon.

What is Creative Commons?

Blurb: Creative Commons provides free tools that allow creators like authors, artists, scientists and educators share their work with the world. Creative Commons let you legally share, remix and reuse creativity!

What is free, open source software (FOSS)?

Blurb: Free, open source software (FOSS) puts users in the driver's seat, providing free and open access to copy, modify and share software with others. It's an important community that empowers innovation and creativity without the lock-in of proprietary software.

Exploring and Creating with Open Content

Blurb: Check out free, open creative content like photos, music, and videos from places like Flickr, Jamendo, and Blip.tv--all free, all at your fingertips, all ready to share, remix, and reuse. Click on the desktop icons to explore content within that category. Because all the content here is CC-licensed, you can take the material, rip it, use it, improve it.

Access the applications by clicking "Applications" in the menu at the lower left corner of the screen. Create your own flyer using the Gimp and CC-licensed photos on the desktop. Draw a picture, cut up audio, view videos using free, open media players. Plug in an thumb drive to save open content to it. When you create, you can share it again with Creative Commons.

Where is open content going? There are lots of exciting projects that are working on opening up information to everyone. Help support projects to minimaize barriers to sharing and reusing educational materials, build the open content base by adding your favorite CC-licensed-powered project to the Content Directories on the CC wiki, jump in with supporting access to a huge library of free, open books.

Participate

Join us! Help the growing movement that is working to minimize barriers to the sharing and reuse of creativity and culture. There's lots of way to get involved. Build the open content base by adding your favorite CC-licensed-powered project to the Content Directories on the CC wiki. Check out some sweet projects like ccLearn, the educational arm of CC, and OpenLibrary, an ambitious project to collect and unite catalog data for all books in the world.

Quitting out of LiveContent

Quit out of LiveContent by clicking "System" from the menubar at the bottom of the screen. Next, click "Shut Down" and choose whether to restart the computer into the default operating system or shut down.

Thank You

Worldlabel.com has provided generous support for the development and distribution of this project. Technical infrastructure provided by Fedora.

Share how you use LiveContent

Design

  • icons that match apps, renaming of things like openoffice
  • GNOME accessibility for disabled?
  • sticker or revised packaging documentation for libraries
  • develop LiveContent logo
  • put content icons on the front of packaging?


Distribution Options

Future Ideas for LiveContent

Freedom Toaster

  • Freedom Toasters are conveniently located, self-contained, computer-based, 'Bring 'n Burn' facilities.
  • Like vending machines, preloaded to dispense confectionery, Freedom Toasters are preloaded to dispense free digital products, including software, photography, music and literature.
  • The Freedom Toaster project began as a means of overcoming the difficulty in obtaining Linux and Open Source software due to the restrictive telecommunications environment in South Africa, where the easy downloading of large pieces of software is just not possible for everyone.

CC proselytizing and swag

  • have on hand to give out at conferences, meetings
  • ccLearn
  • distribute with other swag like buttons, stickers
Retrieved from "https://wiki.creativecommons.org/index.php?title=LiveContent_2_0&oldid=10554"