1 Strategies for Developing and Deploying Free/Open Source Software Walt Scacchi Institute for Software Research School of Information and Computer Science University of California, Irvine Irvine, CA 92697-3425 USA [email protected]http://www.ics.uci.edu/~wscacchi http://www. ics . uci .edu/~wscacchi/Presentations/OSS-Strategies/
36
Embed
Strategies for Developing and Deploying Free/Open Source ...
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1
Strategies for Developing andDeploying Free/Open Source
Software
Walt ScacchiInstitute for Software Research
School of Information and Computer ScienceUniversity of California, IrvineIrvine, CA 92697-3425 USA
NetBeans and Mozilladevelopers collaborate onspell-checking module,
NetBeans adopts Mozillasuper review process
Apache releases newversion of Tomcat
23
Project management and careerdevelopment (Scacchi 2004)
• F/OSSD projects self-organize as a layeredmeritocracy via virtual project management– Meritocracies embrace incremental mutations over
radical innovations– VPM requires people to act in leadership roles based
on skill, availability, and belief in project community
• F/OSS developers use what they build, want tohave fun, exercise their technical skill, try outnew kinds of systems to develop, and/orinterconnect multiple F/OSSD projects (freedomof choice and expression).
• E-Laboratory– encourages adoption of E-Commerce or E-Business
capabilities in Laboratory operations, administration,research, education
• F/OSSD + E-Lab = Open Laboratory– embraces and facilitates open source and E-Laboratory
systems, processes, practices, and communities
26
Why Open Laboratory?
• Help make Laboratory work faster, better,cheaper.
• Empower interested Laboratory employees,contractors, faculty, students and interestedcitizens to offer help and capture theircontributions.
• Enable creation of public test-beds whereexisting/new Laboratory processes can bedemonstrated, manipulated, and refined.– This may facilitate “participatory science” projects
and science learning/game grids.
27
Open source processes
• Free/open source software does not embody theprocesses for how to develop, deploy, use orsustain them– Deploying F/OSS is low-cost, but often inefficient and
sub-optimal
• Closed source software development,deployment, use, and support is also inefficientand sub-optimal– Explicit open source processes could also help closed
source systems.
28
Motivation for open sourceprocesses
• Closed source processes:– Typically opaque or tacit, difficult to improve, subject
to inappropriate automation or patent by vendors.
• Open source processes:– Enable continuous process improvement and
organizational learning through open access to the“source code” of enterprise processes.
29
Strategies for Developing andDeploying F/OSS
• Requirements and design artifact sharing– Emergent, continuously evolving– Structured vs. semi-structured vs. ad hoc
• Community and career development– Join/form F/OSSD consortia– Enhance local skill base– Encourage community ownership over individual
contribution/fault– Leverage private-collective action, when possible
30
Strategies for Developing andDeploying F/OSS
• Capture and codify laboratory process domainexpertise as open source processes:– F/OSS systems analysis and design– Deployment and support of F/OSS systems– Usability capture and feedback– Organizational transformation
• Stimulate/facilitate UC-based research intoF/OSSD through partnerships– UC Institute for Software Research (ISR)– UC Computer Game Culture and Technology Lab
• Game Grids for Science Learning (Science Learning Grids)
31
Strategies for Developing andDeploying F/OSS
• Establish Open Lab F/OSS portals andclearinghouse– Create/share process toolkits, libraries, repositories
• “Co-source” development of OL processes– amortize and share OL development costs across
laboratories• Construct operational OL system and process
demo’s– OL prototypes and public test-beds– Exportable processes for laboratory operations,
administration, research, and education
32
Another game M&Senvironment
33
Open sourcesoftware research
Web site atUCI
34
Acknowledgements
• Project collaborators:– Mark Ackerman, UMichigan, Ann Arbor– Les Gasser, UIllinois, Urbana-Champaign– John Noll, Santa Clara University– Margaret Ellliot, Chris Jensen, Justin Erenkrantz,
Richard Taylor, Jason Robbins, UCI-ISR– Julia Watson, The Ohio State University
• Funding support:– National Science Foundation ITR#-0083075, ITR#-
#0205679, ITR#-0205724, and ITR#-0350754.– No endorsement implied.
35
References
• A. Hars and S. Ou, Working for free? Motivations forparticipating in open source projects, InternationalJournal of Electronic Commerce, 6(3), Spring 2002.
• E.von Hippel and G. von Krogh, Open Source Softwareand the “Private-Collective” Innovation Model: Issues forOrganization Science, Organization Science, 14(2), 209-223, 2003
• G. Madey, V. Freeh, and R. Tynan, Modeling the F/OSSCommunity: A Quantitative Investigation, in Free/OpenSource Software Development, ed., Stephan Koch, IdeaPublishing, forthcoming.
• D.M. Nichols & M.B. Twidale, The Usability of OpenSource Software, First Monday, 8(1), January 2003.
• C. Jensen and W. Scacchi, Discovering, Modeling, and Re-enacting Open Source Software Processes: A Case Study,Working Paper, Institute for Software Research, March 2004.
• W. Scacchi, Free/Open Source Software Development Practicesin the Computer Game Community, IEEE Software, Special Issueon Open Source Software, 21(1), 59-67, January-February 2004.
• W. Scacchi, When is Free/Open Source Software DevelopmentFaster, Better, and Cheaper than Software Engineering? WorkingPaper, Institute for Software Research, UC Irvine, April 2003.
• W. Scacchi, Understanding the Requirements for DevelopingOpen Source Software, IEE Proceedings--Software, 149(1), 24-39, 2002.
• W. Scacchi, Redesigning Contracted Service Procurement forInternet-based Electronic Commerce: A Case Study, J.Information Technology and Management, 2(3), 313-334, 2001.
• This presentation can be found at:http://www.ics.uci.edu/~wscacchi/Presentations/OSS-Strategies/