floss - cored.cs.tut.ficored.cs.tut.fi/best/slides/floss.pdf · floss terhi kilamo, teaching...
TRANSCRIPT
FLOSS?
● F ● L● O● S● S● ?
Pic: xkcd07.08.13 2
Free Software
• "Free software is a matter of liberty, not price. To understand the concept, you should think of free as in free speech, not as in free beer.” - Richard Stallman
• Free software movement: political and social, 1983
• Free Software Foundation
07.08.13 3
Open Source Software
• "Shut up and show them the code." -Eric S. Raymond
• A business model• Development methodology• Open Source Initiative, 1998
Four Freedoms
0. The freedom to run the program, for any purpose
1. The freedom to study how the program works, and change it so it does your computing as you wish
2. The freedom to redistribute copies so you can help your neighbor
3. The freedom to distribute copies of your modified versions to others
Open Source Software
• Not just simply access to source code– Free distribution– Source code included– Integrity of the author's source code– No discrimination– Licence must not be specific to a product and
must it be technology neutral– License must not restrict other software
opensource.org
FLOSS: pieces of the puzzle
• Development method for software• Licence• Community• Business
model
Kuva: http://news.cnet.com/8301-30685_3-10422338-264.html
”Release early, release often. And listen to your customers”
- E.S. Raymond
The Cathedral and The Bazaar
Development method• “the power of distributed
peer review and transparency of process.”
• ”better quality, higher reliability, more flexibility, lower cost, and an end to predatory vendor lock-in.”
• Ideally, participation in the community needs no restrictions
• Adequate tools neededopensource.org, bugzilla.org
Example: github
• Build software better, together.
”Given enough eyeballs, all bugs are shallow”
- Linus' law
Licence● Who writes the code owns the
copyright, and can decide the license
● A way to publish software with the right
● to copy and distribute software
● to access to the source code
● to improve software ● A method to give rights to
people besides the author
● Copyleft● Permissive● Virality● Dual licensing
Pic: Wikipedia
Licence
Licence Compatibility
”Every good work of software starts by scratching a developer's personal itch”
E.S. Raymond
Developer Community
● Community base● Volunteer● Company● Mixed
● Motivation● Internal: hacker identity, fun, ideology● External: fame, learning, money
Developer Community
Community Structure● 98% male, unlike to have over 5-7%
female participation● 60% aged 16-25● Majority has a partner, many have
child(ren)●
Business model● Internal usage + competition
strategy● Software As A Service (SAAS)● Consulting (technical, legal,
strategic,...)● Integration, aggregation, and
customization ● Retailing and distribution ● Product and software know-how ● Process and methodology know-
how● Services and product support ● Training and recruiting
● Certification and quality assurance● Substitution/migration● Dual licensing● Documentation (books, user manuals,
etc)● Other process-related issues (testing,
deployment...)● Hardware + other related software
(extra features, protocols, configurations) + media content
● Commercial software on top of OSS● Platform specialization/adaptation,
localization● IT infrastructure ● ...
Business model
Code over everything● Poor documentation● Focus on running the code● Developer and code centric● Community developed● Meritocracy
Challenges
● Stability in different contexts● Versioning● Testing● Project management and trust● Legal issues
Conclusion● Free/Libre Open Source Software is
● Method and tools – known distribution channel● Licence – common and known to people● Community – support for collaboration
● Code and people● Clear and well understood rules● Community desides its practices. Companies have no
absolute power● Open vs. Closed: architectural level issue● No silver bullet!
References
Eric S. Raymond: The Cathedral & the Bazaar. O’Reilly, 2001.
Heather J. Meeker. The Open Source Alternative: Understanding Risks and Leveraging Opportunities. Wiley, 2008.
Bernard Golden. Succeeding with Open Source. Addison-Wesley, 2004.
Karl Fogel. Producing Open Source Software: How to Run a Successful Free Software Project, O’Reilly, 2005,
Dan Woods and Gautam Guliani. Open Source for the Enterprise: Managing Risks, Reaping Rewards. O’Reilly 2005.
Van Lindberg. Intellectual Property and Open Source. A Practical Guide to Protecting Code. O’Reilly, 2008.
Mikko Välimäki. The Rise of Open Source Licensing. A Challenge to the Use of Intellectual Property in the Software Industry. Turre Publishing, 2005. ( http://pub.turre.com/openbook_valimaki.pdf )
Open Source Wikipedia Entry ( http://en.wikipedia.org/wiki/Open_source )
Open Source 101: An Executive Guide to Open Source. ( http://www.cio.com.au/article/268176/open_source_101_an_executive_guide_open_source?pp=1 )
Open Source Initiative ( http://www.opensource.org/ )
The Linux Licencing Labyrinth ( http://www.linuxinsider.com/story/65185.html )
FLOSSTerhi Kilamo, teaching [email protected]
FLOSS?●F ●L●O●S●S●?Pic: xkcd07.08.132
Free Software
• "Free software is a matter of liberty, not price. To understand the concept, you should think of free as in free speech, not as in free beer.” - Richard Stallman
• Free software movement: political and social, 1983
• Free Software Foundation
07.08.13 3
Open Source Software •"Shut up and show them the code." -Eric S. Raymond•A business model•Development methodology•Open Source Initiative, 1998
Four Freedoms 0. The freedom to run the program, for any purpose1. The freedom to study how the program works, and change it so it does your computing as you wish2. The freedom to redistribute copies so you can help your neighbor3. The freedom to distribute copies of your modified versions to others
Open Source Software•Not just simply access to source code–Free distribution–Source code included–Integrity of the author's source code–No discrimination–Licence must not be specific to a product and must it be technology neutral–License must not restrict other software opensource.org
FLOSS: pieces of the puzzle•Development method for software•Licence•Community•Businessmodel Kuva: http://news.cnet.com/8301-30685_3-10422338-264.html
”Release early, release often. And listen to your customers” - E.S. Raymond The Cathedral and The Bazaar
Development method•“the power of distributed peer review and transparency of process.”•”better quality, higher reliability, more flexibility, lower cost, and an end to predatory vendor lock-in.”•Ideally, participation in the community needs no restrictions•Adequate tools neededopensource.org, bugzilla.org
Example: github •Build software better, together.
”Given enough eyeballs, all bugs are shallow” - Linus' law
Licence● Who writes the code owns the copyright, and can decide the license● A way to publish software with the right● to copy and distribute software● to access to the source code ●to improve software ● A method to give rights to people besides the author● Copyleft● Permissive● Virality● Dual licensingPic: Wikipedia
Licence
Licence Compatibility
”Every good work of software starts by scratching a developer's personal itch”E.S. Raymond
Developer Community● Community base●Volunteer●Company●Mixed● Motivation●Internal: hacker identity, fun, ideology●External: fame, learning, money
Developer Community
Community Structure● 98% male, unlike to have over 5-7% female participation● 60% aged 16-25● Majority has a partner, many have child(ren)●
Business model● Internal usage + competition strategy● Software As A Service (SAAS)● Consulting (technical, legal, strategic,...)● Integration, aggregation, and customization ● Retailing and distribution ● Product and software know-how ● Process and methodology know-how● Services and product support ● Training and recruiting● Certification and quality assurance● Substitution/migration● Dual licensing● Documentation (books, user manuals, etc)● Other process-related issues (testing, deployment...)● Hardware + other related software (extra features, protocols, configurations) + media content● Commercial software on top of OSS● Platform specialization/adaptation, localization● IT infrastructure ● ...
Business model
Code over everything● Poor documentation● Focus on running the code● Developer and code centric● Community developed● Meritocracy
Challenges● Stability in different contexts● Versioning● Testing● Project management and trust● Legal issues
Conclusion● Free/Libre Open Source Software is●Method and tools – known distribution channel●Licence – common and known to people●Community – support for collaboration● Code and people●Clear and well understood rules●Community desides its practices. Companies have no absolute power● Open vs. Closed: architectural level issue● No silver bullet!
ReferencesEric S. Raymond: The Cathedral & the Bazaar. O’Reilly, 2001.Heather J. Meeker. The Open Source Alternative: Understanding Risks and Leveraging Opportunities. Wiley, 2008.Bernard Golden. Succeeding with Open Source. Addison-Wesley, 2004.Karl Fogel. Producing Open Source Software: How to Run a Successful Free Software Project, O’Reilly, 2005,Dan Woods and Gautam Guliani. Open Source for the Enterprise: Managing Risks, Reaping Rewards. O’Reilly 2005.Van Lindberg. Intellectual Property and Open Source. A Practical Guide to Protecting Code. O’Reilly, 2008.Mikko Välimäki. The Rise of Open Source Licensing. A Challenge to the Use of Intellectual Property in the Software Industry. Turre Publishing, 2005. ( http://pub.turre.com/openbook_valimaki.pdf )Open Source Wikipedia Entry ( http://en.wikipedia.org/wiki/Open_source )Open Source 101: An Executive Guide to Open Source. ( http://www.cio.com.au/article/268176/open_source_101_an_executive_guide_open_source?pp=1 )Open Source Initiative ( http://www.opensource.org/ )The Linux Licencing Labyrinth ( http://www.linuxinsider.com/story/65185.html )