|
|
| Line 1: |
Line 1: |
| − | [[Category:Technology]] | + | #REDIRECT [[LiveContent_2_0]] |
| − | [[Category:Developer Challenges]]
| |
| − | [[Category:Developer]]
| |
| − | [[Category:freesoftware]]
| |
| − | [[Category:opensource]]
| |
| − | [[Category:ccLiveCD]]
| |
| − | [[Category:LiveContent]]
| |
| − | | |
| − | | |
| − | ==ccLiveContent v2.0 - Libraries==
| |
| − | | |
| − | === ideas to add for v2.0 release ===
| |
| − | | |
| − | *kids programs like tuxpaint
| |
| − | *math app from openoffice - http://www.openoffice.org/product/math.html
| |
| − | *icons that match apps, renaming of things like openoffice
| |
| − | *GNOME accessibility for disabled
| |
| − | *openclipart
| |
| − | *sticker or revised packaging documentation for libraries
| |
| − | *develop LiveContent logo
| |
| − | *put content icons on the front of packaging?
| |
| − | *ISSN numbers
| |
| − | | |
| − | === 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
| |
| − | | |
| − | === 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.
| |
