For your information, a note from Dave Humphrey on LUX, a new graduate program on Linux and Open Source System Administration at Seneca College, Toronto, ON.
I wanted to let you know about a new graduate program we’re launching in September on Linux and open source system administration. LUX is designed for industry people who want to move into an open source Linux community—we’re partnering with Red Hat and Fedora—and is structured so people can still work while they study.
Professor and Co-Founder
Centre for Development of Open Technology
Seneca College, Toronto
For your information, a research workshop on open source and business.
CALL FOR PAPERS
OSS 2.0 : Leveraging the Open Source community for business
Workshop at OSS 2008 Conference, co-located with IFIP WCC 2008 Milan (Italy)
Deadline for submission: 21st June 2008
Notification of acceptance: 11th July 2008
Final submission due: 25th July 2008
Workshop: 10th September 2008
Continue reading “OSS 2.0: Leveraging The Open Source Community For Business”
Following up on related discussions, another common confusion in my opinion is to think that “open source” is a business model. It is not. Open source is a business strategy, in support of a business model. You still need to know how to make money, and it doesn’t happen by giving software away for free. That is to say, you need a business model like selling subscription or implementation services.
The most common commercial open source business strategy is the “dual-license strategy” as demonstrated by MySQL, Alfresco, etc. This particular business strategy is mostly a go-to-market strategy, a way by which the commercial open source company penetrates customers and fosters the sale. I’ve blogged about this before here and here.
There is more to say, obviously, and I’m working on it. Any thoughts would be appreciated!a
JUnit is a widely-adopted unit testing framework for Java, developed by Kent Beck and Erich Gamma. In their discussion of JUnit 3.8’s design, the authors state:
Notice how TestCase, the central abstraction in the framework, is involved in four patterns. Pictures of mature object designs show this same ‘pattern density’. The star of the design has a rich set of relationships with the supporting players.
The notion of design pattern density has been around forever, but with little serious work being done to refine the idea. I’m calling on all experts (reading this blog…) to tell me whether they agree or disagree with the following statement:
Continue reading “Design Pattern Density and Design Maturity”
Bertrand Meyer, at the 40 Years of Software Engineering panel at ICSE 2008, on May 16, 2008, 11:56am: “Electrical engineering is to computer science what making a bed is to making love.” I’m not entirely sure this is true, but it certainly makes for a memorable quote.
UPDATE: I had mentioned my enjoyment of this quote to Prof. Meyer at the conference. A few days later I received an email from him in which he generously (and gracefully) corrects me with the exact statement, which first appeared in his inaugural lecture at ETH Zurich:
We appreciate our debt to electrical engineering, without which there would be no computers. Indeed, computer science is to electrical engineering as the art of making love is to the art of making beds.
Much better, and certainly less crude than my in-the-moment snapshot.
Commercial open source has a peculiar sales process. Frequently, when a firm decides to buy (license) a specific type of software like a content management system or a wiki engine, they’ll find that their company already employs multiple solutions, downloaded for free from the Internet. By some measures, this is dangerous to IT governance, as it bypasses corporate purchasing and operating regulations. On the other hand, open source empowers IT users to make their own decisions early on without having to go through lengthy approval processes, keeping them nimble and speedy. So, is commercial open source good or bad for IT operations and the CIO?
Read more on FOSSBazaar…
Archived copy of article.
Software researchers need case studies to validate new tools and methods of object-oriented software design. A good thing to do is to standardize on a set of open source frameworks and libraries that are known and available to everyone. Basically, a benchmark set for new tools and methods in object-oriented software design. JUnit and JHotDraw come to mind.
Most open source frameworks and libraries that are being used in research studies have little original documentation associated with them. However, I as well as others have written up such documentation. Here are those frameworks that I see increasingly being used in scientific studies, as well as any design documentation documentation that I may have provided.
Continue reading “Object-Oriented Software Design Documentation”
Commercial open source firms go to market trying to create an “unfair” competitive advantage that lets them win customers more easily than their competitors. So do most other companies. Commercial open source firms do this by bypassing the traditional purchasing process by getting their software into customer companies for free, before the customers even know they will need the software. But is an employee’s decision to install a piece of open source software a good decision for the company? After all, every software locks in its users, whether open source or not.
Continue reading “SDN: Is Open Source Competing Unfairly?”
Markus Völter of the Software Engineering Radio podcast show interviewed me about open source business models. Why not listen to the Open Source Business Model podcast while running rather than reading it as papers on my website?
Continue reading “SE Radio Interview on Open Source Business Models”
As a researcher, imprecise naming bothers me. The general confusion around the terms commercial open source, professional open source, and community open source warrants closer analysis.
First my proposal, then some litmus tests, followed by a bit of history.
- Commercial open source is software provided as open source where a single legal entity owns the rights to the software (SugarCRM, Alfresco, etc.)
- Professional open source is software provided as open source where a dominant firm provides services around the software without actually owning it (JBoss, Spring, etc.)
- Community open source is software provided as open source where multiple stakeholders hold the rights and no player dominates the software (Linux, Apache, etc.)
Continue reading “Commercial, Professional, and Community Open Source: Resolving the Naming Confusion”