Difference between revisions of "LiveContent 2 0"
(→Technical Considerations) |
(→Other) |
||
Line 48: | Line 48: | ||
====Other==== | ====Other==== | ||
− | *openclipart | + | * [http://www.openclipart.org/ openclipart] |
− | * | + | * [http://openfontlibrary.org/ openfontlibrary] |
− | * | + | * [http://www.openlibrary.org/ openlibrary] |
+ | * [http://www.worldlabel.com/Pages/openoffice-template.htm opendocumenttemplates] | ||
===Documentation=== | ===Documentation=== |
Revision as of 20:40, 27 September 2007
Contents
Rationale
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.
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.
Technical Considerations
- bugs
- autocurated packaging of content
- daily build tech specs
- 1.0 testing feedback
Contents
Applications and Content running on Fedora 7
Applications
- keep most from v1.0
- OpenOffice
- Inkscape
- The Gimp
- Firefox
- Totem
- Evince
- gThumb
- additions?
- math app from openoffice - http://www.openoffice.org/product/math.html
- kids programs like tuxpaint
- audio/video manipulation?
CC Content
Content categories may include:
- Audio
- Video
- Text
- Image
- Educational resources
Other
Documentation
Proper documentation about LiveContent is vital to include within the CD/DVD. Videos and illustrations are great ways to communicate information. A 3-pronged documentation outline would be great. Possibly get testimonials or short sound bytes?
How to deliver documentation that is informative, draws people in, is not boring or too much to digest?
- First Window/icon/video/comic = What is open content and Creative Commons?
- Second Window/icon/video/comic = What is open source software?
- Third Window/icon/video/comic = How do I use the LiveContent DVD?
What is open content and Creative Commons?
- Creative Commons text, but make sure we're speaking to target library audiences.
- info from cc.o site
- include the "review conditions" and "select license mockups"
What is free, open source software (FOSS)?
- add stuff here
How do I use LiveContent DVD?
- livecontent is dynamic content
- what does it mean for users to interact with living content?
- how can cc allow users to reuse content, remix content, share the content again to the community?
- livecontent is a “window on CC,” because cc is not a content repository in itself
Demos
Share, Remix, Reuse
- How do I use this take this content and make something new with the apps?
- How do I then share this stuff with others?
- What is the cycle?
-
- searching for content
- manipulating content for new creation
- putting your creation back into the stew
-
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?
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?
- 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 LiveContent without spamming?
- 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 to install or use at home, but doesn't align too well with the applications and content becoming obsolete
- accessibility concerns at libraries
computing environment
- 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
- "Public Libraries and the Internet 2006: Study Results and findings" report available for download here - may provide some insight to landscape of public library terminal workstation metrics
dvds?
- 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
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 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.