An "open source software primer" for those that are new to OSS or how it works. Covers some of the basics (who can contribute to the code?) in a (hopefully) easy to read and understand manner.
The Who, What, When, Why, Where and How Photo credit: http://www.flickr.com/photos/auroramixer/2622264212 This is an open source mixer, meaning you can find the instructions and all the parts you need to build this yourself (for free, minus cost of your parts) online. The website is http:// auroramixer.com if you feel so inclined!
If someone tries to present them - throw spoiled vegetables at them. If you want a presentable version, contact the RMIC. Photo credits are listed in the “Presenter Notes”. These slides are better off read, not presented. Why? Because it’s hard for your audience to read the slides AND listen to you at the same time. Better off giving them 100% of the information, not 50%.
the Wild, Wild West A place where anything goes A place where anyone can do what they want with software Photo credit: http://flickr.com/photos/arcticpuppy/2740392172
a trademark of the scientific community i.e. Knowledge transfer via academic papers and studies It has existed in the software world for 40+ years Photo credit: http://flickr.com/photos/epitti/2370873167 From engineering to medicine, from art to music, there are many examples of an “open source” environment or mindset. Essentially, “open source” just means “I’ll share my knowledge or experience so someone else can benefit. Or improve it.”
computer software that is available in source code form for which the source code and certain other rights normally reserved for copyright holders are provided under a software license that permits users to study, change and improve the software. In non-Wikipedia speak, it is software that allows users rights they don’t have with many proprietary software packages. Users and developers can view the source code, build it on their machine, customize it (if needed), etc. The following slides will dive into more details about OSS.
programmer named Eric S. Raymond wrote an essay entitled The Cathedral and the Bazaar. The essay is a look at how open source software is developed. It focused on Raymond’s experiences in developing open source software on a project named fetchmail and included his observations on the then-quickly-growing Linux operating system. Eric Raymond has a series of blog posts and other writings on OSS that are well worth reading. You can find them at http://www.catb.org/~esr/
process that was “top down” Ideas came from the top and only certain developers could make changes to the code It was open source, but limited in terms of participation In many cases, this also describes proprietary software Photo credit: http://flickr.com/photos/dannyford/5211972994
openly viewed and maintained over the Internet Code contributions could come from many sources A major benefit: “Given enough eyeballs, all bugs are shallow” Photo credit: http://flickr.com/photos/dynamosquito/2589857274 Most open source projects embrace the “Bazaar” style over the “Cathedral” style.
of one or two people and a few big ideas They often come about because a programmer needed something that was missing and built it themselves Linus Torvalds (pictured) is the creator of the Linux kernel, one of the most widely used OSS projects Photo credit: http://flickr.com/photos/randal-schwartz/3996403365
project committers (or maintainers) have the ability to make changes to the software. Additions and bug fixes may come from anywhere, but only the proper people allow them to take effect. The rules and etiquette for how this happens largely depends on the project, but in most cases it is an open process. For most OSS projects, you can see the list of committers on the project web page, or version control system.
Key Committers Source Code Repository The Community The community submits patches, bug fixes and suggestions to the owners and key committers These must be vetted and approved before they can be introduced to the source code
Key Committers Source Code Repository The Community Users often submit requests for improvements or other ideas about the software These may be vetted and completed by either the community, or the project owner/key committers The Users
Source Code Repository The Community Some users or community members go on to become committers, or even project owners They are often heavy users or proponents of the software Typically, their ideas and code contributions are tested to ensure they have value A User Yay! Yay!
Source Code Repository Some users have radical ideas about how the software should work If the idea or change is rejected, the user can choose to copy the code and create a branch The community may or may not embrace a branch Branches become new projects and are the only way to add changes without permission The Community A User NO! Hi, I’m new here! ???
well as effort, there are a set of ground rules for how this is done Licenses define how the code may be used, modified and shared (or distributed) Certain licenses, such as the GNU Public License (GPL), are used to enforce the free (as in speech and as in beer) aspects of the software Other licenses, such as the Apache license, allow companies to reuse modified versions of the software without releasing those changes to the public
resources (paid developers) to many open source projects Microsoft uses and contributes to open source projects, such as jQuery Many startup companies contribute to and use OSS
Department of Defense A 2009 memo from the DoD CIO emphasizes that “OSS can provide advantages” when updating software capabilities Also in 2009, the official home page of the White House, whitehouse.gov, began using Drupal, an open source content management system
of open source software and services, was purchased by VMWare for $360+ million in 2009 10gen, creator of MongoDB, recently received $6.5mil in VC funding