To add to Paul's list, I add the maintenance flexibility. The below
is from the sample document I had at the LBS:
1.1 Maintenance Options
One of the best benefits of the Open Source model is the ability to
choose your source of maintenance. Some people have argued that the
lack of a single entity to hold responsible for problems is a
drawback. However, the real question when something breaks is not
"who is responsible?" Just because you can identify someone to hold
responsible, and can sue, does not mean the problem will be fixed.
The real questions are:
2 What is wrong? And
3 How do I fix it?
Because all parties have access to the source code, many eyes can
immediately be looking for the problem, and how to fix it. This
contrasts with the traditional model, where the only source of
maintenance is the originator of the software, and you would have to
wait until they found and repaired the problem to get a fix. Note
that, even if the source is interested in fixing the problem, they
only have limited resources to fix your problem and any others that
may also be in the pipeline. If they have no interest in fixing the
problem, your only options are to threaten court action, and to try
and negotiate for the fix. Both of these actions eat time, while the
problem is not fixed. However, with Open Source, you can use all four
of the below options simultaneously, increasing the odds that the fix
will be done quickly, which is the real goal.
3.1.1 Do Yourself
One option is to do the work yourself, with the advantage that you
have immediate ability to start fixes. With Linux, any work you do
is only for the cost of your employees.
3.1.2 Contact the originator
Virtually all of the packages include the name and contact of the
author of the software. You have the option of submitting the bug
report directly to the author, requesting help. Many of the authors
are very willing to fix problems as they are found, as is evidenced by
the speed of fixes occurring within Linux.
3.1.3 Use on-line support
Another option is to use the support that is available on-line,
through Usenet newsgroups and online resources like www.redhat.com,
www.linxuxcare.com, and www.linux.com to find and maintain the
software. You would do the actual patching, but would post problems
and obtain support via the WWW. Note that the Linux on-line support
community earned Infoworld's "Support of the Year" for 1997.
3.1.4 Contract out
The final option is to contract out support. Numerous contractors
as well as local people, provide support for Linux.
This support is either on a monthly or a per-incident charge
structure. One advantage of Linux is the range of support possible.
If you find you don't like a particular support vendor, you can change
at a whim. You can even have multiple contracts simultaneously, to
increase the number of eyes looking at the problems. This contrasts
to most software, which is only supported by the original vendor,
leaving you no option if you are dissatisfied.
jeff
------------------------------------------------------------------------
Jeffry Smith Technical Sales Consultant Mission Critical Linux
[EMAIL PROTECTED] phone:603.930.9379 fax:978.446.9470
------------------------------------------------------------------------
Thought for today: Never let someone who says it cannot be done interrupt the person
who is
doing it.
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
