This case study examines the San Francisco Performing Arts Library & Museum's (SFPALM) decision to migrate from Windows to open source software. SFPALM needed to license its unlicensed Windows server, outsource some services, and save money. It decided to use Red Hat Linux for its operating system, Samba for file/print sharing, Astaro Security Linux for firewall/VPN, qMail for email, Apache for web hosting, and maintain its legacy database on a Linux server. This saved $2,800 compared to purchasing Windows licenses and keeping outsourced services. The presentation discusses open source strengths like lower costs, security, and stability, as well as challenges like difficulty of deployment and lack

1. An Open Source Case Study Determining if open source is right for you Presented by: Jason Dearborn

2. Overview What is Open Source Case Study of San Francisco Performing Arts Library & Museum Strengths & Weaknesses Decision Making Process Q & A

3. What is Open Source Software (OSS)? Definition : Open Source is a term used to describe software freely distributed with full source code included. Open Source software must comply with the 9 guidelines laid out by the Open Source Initiative (OSI).

4. OSI Guidelines Free Redistribution The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale. Source Code The program must include source code, and must allow distribution in source code as well as compiled form.

5. OSI Guidelines Open Source Initiative www.opensource.org

6. Open Source Licensing General Public License (GPL) Gives you the right to copy, modify, and change the source code. Restriction: Any derivative works must also carry the GPL license Copyleft Berkeley Software Distribution (BSD) Allows licensee to take any modifications to the source code private. Restriction: You must give credit to original copyright holder. Non-Copyleft

7. Open Source Licensing There are many Open Source Licenses. Most are derivatives of either the GPL or BSD. Academic Free License Artistic License Apple Public Source License Common Public License LGPL, etc

8. Open Source Licensing Less restrictive licensing has allowed anyone with a computer to access powerful computing and networking tools. Anyone with the desire and aptitude can gain hands-on experience with technology such as databases, clustering, TCP/IP packet manipulation, and application development.

9. What is Open Source Software (OSS)? It’s almost as though the village blacksmiths of the world can now build axles in their backyards, assemble them together and compete with General Motors. Paul Maritz, Microsoft

10. More information: Berkman Center's Openlaw Report on Open Source Software Licensing http://cyber.law. harvard . edu / openlaw / gpl . pdf Open Source License Law Resource Center http://www. denniskennedy .com/ opensourcelaw . htm .

11. Case Study

12. Case Study: SFPALM Mission SFPALM is a non-profit library and museum whose mission is to preserve and make available to the public materials documenting the performing arts in the San Francisco Bay Area.

13. Case Study: Needs Provide basic network infrastructure to employees. File & Print sharing Remote Access Email Host SFPALM.ORG website. Host Cuadra STAR library database.

14. Case Study: Situation Windows 2000 Small Business Server Inter-office email File & Print VPN Firewall Windows NT 4 Server Cuadra STAR database Website and internet email hosted by InternetConnect. (now Covad)

15. Case Study: Issues Windows 2000 SBS server is unlicensed. Firewall installed on file & print server. Unnecessary outsourcing of web and email hosting.

16. Case Study: Plan of Action Get SFPALM legal. (Businesses can be fined up to $150,000 per copy of unlicensed software) Firewall should be standalone device. Save money by bring web and mail hosting in-house.

17. Case Study: Options Unlicensed Server Purchase Software License SFPALM did not have the funding necessary. They were also unable to secure a technology grant. Migrate server to Linux

18. Case Study: Internal Services Operating System: RedHat Linux 8.0 Commercially supported Well documented Most Popular Distribution

19. Case Study: Internal Services File & Print: SAMBA Provides seamless file and print services to Windows clients. Faster file serving then Windows 2000/2003 Samba 3 (still in beta) will support Active Directory

20. Case Study: Firewall Solution VPN / Firewall: Astaro Security Linux Easy to configure and manage Commercial support and documentation Enterprise class firewall and remote access solution at non-profit prices. Runs on low-end hardware 400 MHz CPU, 128 MB RAM, 8 GB HDD

21. Case Study: External Services RedHat Linux 8.0 Email: qMail Secure Reliable Simple

22. Case Study: External Services Web Hosting: Apache most popular web server on the Internet since April of 1996 Fast Secure Stable

23. Case Study: Other Solutions Cuadra STAR: Maintain legacy Windows NT4 server. Once funds are available, SFPALM plans to upgrade to the latest version of STAR which runs on RedHat Linux.

24. Case Study: Results Total Savings: $2800

25. Strengths & Weaknesses of Open Source Software (and Linux)

26. Strengths Less Expensive Security Open source means more eyes to catch the bugs Linux is the industry leader in defensive design Linux is less vulnerable to MS-centric worms and viruses. Stability Linux is famous for not crashing Thousands of potential contributing developers allow software to mature faster.

27. Strengths Less administration required Companies with a Linux (or Unix) infrastructure report better administrator:server ratios then those with proprietary solutions. Open Formats and Standards No vendor lock-in

28. Strengths Minimal hardware requirements RedHat 9 (Text Mode) Pentium-class CPU 500mb HDD 64 MB RAM Favored in developing nations or poor communities Helping to bridge the digital divide

29. Weaknesses Can be difficult to deploy. Users / Technical staff may be more familiar with proprietary solutions. Lock-out from certain popular proprietary apps.

30. Determining if OSS is right for you. Perform a technology needs assessment. What do you wish to accomplish? Identify your resources Capacity to acquire funds Hardware Knowledge assets Resource: Technology Planning Tools http://www.npowerseattle.org/tools/techplanning.htm

31. Determining if OSS is right for you. How does OSS fit into your long range technology plan? Heterogeneous network environments are more difficult to administer.

32. Determining if OSS is right for you. Research which OSS tools are necessary to meet your need. Research comparable proprietary tools. Compare TCO of OSS vs. proprietary solution for your project.

33. Determining if OSS is right for you TCO includes: Procurement Hardware or network infrastructure upgrades Deployment/Migration Time and Labor Technical support costs Administrative costs Training costs

34. Determining if OSS is right for you.

35. Determining if OSS is right for you Reconciling all of these elements to identify either operating system as the one that offers lower TCO for all situations is impossible. Linux offers a lower TCO in some situations -- a lot lower, according to Aberdeen Group analyst Bill Claybrook. Yet, in other scenarios, Microsoft is a more cost-effective option, he noted. The final answer "depends on what you want to do with it," Claybrook told NewsFactor. Windows vs. Linux: TCO Feud Rages On www.newsfactor.com

36. Q & A For more information or a copy of this presentation, visit the Eris IT Website. www.erisit.com [email_address]