Thursday, March 5, 2015

LitReview: OSI Business Models and GPL Guide Ch. 12 Section 1

Who?


  • Bradley M. Kuhn
  • Anthony K. Sebro, Jr.
  • Denver Gingerich
  • Folks at the OSI and SFLC

What?


GPL Compliance Guide(Chapter 12.1) and Open Source Case for Business

Where?




When?


2014 updates on both

Le Gist


GPL Guide section on basically how the GPL deals specifically with copying, distributing, and modifying, but does not really cover usage at all, which can be helpful to businesses.  OSI article is all about the benefits of Open Source Projects to businesses, and the "4 Ways to Win" which are 4 effective business models that make money with Open Source Software.

The Good


  1. Great transition into the business side of this class.  Also interesting to acknowledge the benefits of the freedom of using open source software in house.
  2. 4 Ways to Win was extremely helpful information.  Great to learn the major types of business models for profiting off FOSS.
  3. I really like the point that FOSS allows businesses to directly interact with customers.  I hadn't thought of this before, but I think it is extremely powerful given how many companies constantly talk about wanting to be close to the customer, and how much companies stress their relationship and trust with customers.

The Bad


  1. Some reiteration on reasons why FOSS is great.  I have heard the bulk of the reasoning behind these benefits over and over again.  I would have saved myself some time by just reading the business model specific stuff.
  2. Only gives 4 business models, although does offer a link for further investigation.  Would have liked some lists of examples, especially considering fellow students complaints at some of the dated examples(*cough*Netscape*cough*)
  3. GPL guide section 12.1 talks about how the GPL does not restrict, but promotes free usage of software under the license, but does not explain how one would control that usage.

Questions


  1. What business model currently is the safest for developers like myself?  Would I fall under that startup category?
  2. Is there a way to regulate usage of software, but still keep it open source?  Is it possible to put source code up for people to see, but not let them use it?  Is this still Open Source Software?
  3. I've heard time and time again the benefits of making software Open Source, to the point that I feel like I can only argue towards everything being open source.  What are some examples of when closed source would be the way to go?

Review


This was a great quick read.  I'm happy to start transitioning from the legal side to the business side of Business/Legal Aspects of FOSS class, and think this was a great jumping off point.  Having said that, I would have liked a less biased, more informative, more up to date version.

7/10

No comments:

Post a Comment