BobBreedlove.com HomePage     Open Source
The computer is only a fast idiot, it has no imagination; it cannot originate action. It is, and will remain, only a tool to man.
-- On Univac computer exhibited at the 1964 NY World’s Fair
Links

Some links that I have found on the web.

Open Source Initiative
Open Source Initiative (OSI) is a non-profit corporation dedicated to managing and promoting the Open Source Definition for the good of the community, specifically through the OSI Certified Open Source Software certification mark and program.
I'm not so sure that the certification is worth it, but the definition could prove interesting.
Open Source Development Network
Publisher of a lot of open source related sites.
Open Source Application Foundation
Our mission is to create and gain wide adoption for software applications of uncompromising quality ussing open-source methods.
DeveloperWorks Open Source Projects
developerWorks hosts a variety of open source projects, all under open source licenses approved by the Open Source Initiative.
java.net
Lots more open source than there used to be!
Reducing Dependence on Proprietary Systems
A page which gives an opinion on reducing your dependency. Has some interesting thoughts.
The Free Software Definition
``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.''
SourceForge
The world's largest open source software development web site.
O'Reilly Network LAMP
A site supporting open source development on Linux.
Jabber
An open source XML based IM server worth investigating.
tigres.org
mid-sized open source community focused on building better tools for collaborative software development
Open Source Solaris
Sun will make much of its Solaris 10 and future operating systems open
Open Source Training
A resource to find training courses.

Inclusion of these links on this page does not constitute endorsement of these views by Bob Breedlove. The views expressed on these web pages are soley those of the authors.

Introduction

This is a place to discuss open source. It is becoming part of my real job more and more and my interest in this topic continues.

Not Necesarily Free

One interesting point about open source software is that it isn't necessarily free. You may pay for support, for administration or for enhancement. The thing about open source software is that it is open (see the definition below).

My Tools

Tools can mean the difference between a successful, profitable project and one which fails. Here's a look at the tools that I use.

Read more . . .

Open Source Definition

The Open Source Initiative promotes a definition for open source. It includes the following elements:

  1. Free Redistribution
  2. Source Code
  3. Derived Works
  4. Integrity of The Author's Source Code
  5. No Discrimination Against Persons or Groups
  6. No Discrimination Against Fields of Endeavor
  7. Distribution of License
  8. License Must Not Be Specific to a Product
  9. The License Must Not Restrict Other Software
  10. The License must be technology-neutral

I won't duplicate there rationale here. After all, that's what the Web is for, visit their page to read their explanation. I am thinking about each of these elements as I work through my thoughts on open source, however.

Updated: 24-Jun-2004

Reducing Depedence on Proprietary Systems

Take a look at this site. The author raises some very good points about open source software. I believe that they follow my own thinking quite well. I believe that open source and proprietary software must co-exist and needs to be evaluated on an equal footing.

Here are some thoughts in no particular order:

  • Create accurate and complete business and technical requirements, then evaluate all software against those requirements.

    I find that many projects amount to technology looking for a requirement rather than answers to business requirements.
  • Do not be surprised when requirements cannot all be collected before development starts.

    Often business users really don't know what they want in an automated system before that system is developed. In short, expect iterative requirements gathering.

  • When you collect requirements remember that they will change, plan for enhancements, growth and complete changes in direction.

    Future enhancements, changes in business direction, expansion--e.g. the normal course of business--is one of the strongest arguments for standards-based systems.

  • A "standard" is not necessarily all that standard.

    Before jumping on the next "standard" to come along, remember that, in a competitive environment, standards are developed by groups of entities with vested interest in something. If they weren't we wouldn't have competing standards bodies, disagreements and multiple platforms. Hopefully, that interest is in interconnections, interoperability, and a logical upgrade path. But, be careful make sure that the "standard" aligns with your business direction.

Updated: 24-Jun-2004

Development Strategy

I believe that Open Source involvement can actually benefit a corporation, even if the heart of their strategy is proprietary. The real trick is to evaluate both open source and proprietary solutions on a level playing field. Each should be able to stand on their own in this evaluation against your goals.

Read more . . .

An Open Source
Support Strategy

Support is one of the major reasons stressed for not selecting open source products in a corporate environment. Given the development strategy espoused above, it is clear that a new paradigm for support needs to be developed at most companies.

Read more . . .

Proprietary Products
at the Base

At the base of Open Source systems are commercial products. You can't get away from it--and you probably don't want to. For example, you can run an open source

  • operating system,
  • applications,
  • utilities,

but all of it sits on propietary

  • motherboards,
  • processors,
  • memory,
  • video cards,
  • hard drives.

The key to successful implementation of open source products in a commercial environment is to evaluate all products on the same footing. This includes considering overall cost of operation, integration into your envirnment, support, and interoperability with your existing systems.

If you make an honest and equitable evaluation of all products. If this is done correctly, it is difficult for anyone to argue with the choice of an open source product.

Updated: 24-Jun-2004

United Nations Agency

The United Nations is moving to embrace open source with a new agency.

It's called the International Open Source Network (IOSN), which is an initiative of the United Nations Development Programme (UNDP) with a primary goal to promote Free and Open Source (FOSS) software usage.

The IOSN is principally focused in the Asia-Pacific Region as it began as an initiative of the UN's Asia-Pacific Information Development Programme (APDIP).

(source)

This is very interesting. It appears that event the U.N. has recognized the possibilities of open source software.

 

 Related Pages: Web Design  Tech Stuff
  © Bob Breedlove all rights reserved 2003