141 lines
5.9 KiB
HTML
141 lines
5.9 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
|
<HTML>
|
|
<HEAD> <title> Linux Advocacy Guidelines </title> </HEAD>
|
|
<BODY>
|
|
<center><H2>MINI-HOWTO </H2></center>
|
|
<P><HR> <P>
|
|
<center><H3> Linux Advocacy Guidelines </H3> </center>
|
|
<ol>
|
|
<li>Share your personal experiences (good and bad) with Linux.
|
|
Everyone knows that software has bugs and limitations and if we
|
|
only have glowing comments about Linux, we aren't being honest. I
|
|
love to tell people about having to reboot four times (three
|
|
scheduled) in three years.
|
|
|
|
<li>If someone has a problem that Linux may be able to solve, offer to
|
|
provide pointers to appropriate information (Web pages, magazine
|
|
articles, books, consultants, ...). If you haven't actually used
|
|
the proposed solution, say so.
|
|
<li>Offer to help someone start using Linux.
|
|
|
|
<li>Try to respond to one ``newbee'' posting each week. Seek out the
|
|
tough questions, you may be the only one to respond and you may
|
|
learn something in the process. However, if you aren't confident
|
|
that you can respond with the correct answer, find someone that
|
|
can.
|
|
|
|
<li>Seek out small software development firms and offer to make a
|
|
presentation about Linux.
|
|
|
|
<li>If the opportunity arises, make a presentation to your employer's
|
|
Information Technology group.
|
|
|
|
<li>If you need an application that is not supported on Linux, contact
|
|
the vendor and request a native Linux version.
|
|
|
|
<li>Participate in community events such as NetDay96
|
|
<A HREF="http://www.netday96.com">http://www.netday96.com</A>.
|
|
While your first priority must be to
|
|
contribute to the success of the event, use the opportunity to let
|
|
others know what Linux can do for them.
|
|
|
|
<li>Always consider the viewpoints of the person to which you are
|
|
``selling'' Linux. Support, reliability, interoperability and cost
|
|
are all factors that a decision-maker must consider. Of the above,
|
|
cost is often the least important portion of the equation.
|
|
|
|
<li>Point out that the production of freely available software takes
|
|
place in an environment of open collaboration between system
|
|
architects, programmers, writers, alpha/beta testers and end users
|
|
which often results in well documented, robust products such as
|
|
Emacs, Perl and the Linux kernel.
|
|
|
|
<li>Report successful efforts of promoting Linux to Linux International
|
|
(<A HREF="mailto:li@li.org">li@li.org</A>) and similar organizations.
|
|
|
|
<li>Find a new home for Linux CD-ROMs and books that you no longer
|
|
need. Give them to someone interested in Linux, a public library
|
|
or a school computer club. A book and its CD-ROM would be most
|
|
appropriate for a library. However, please be sure that making the
|
|
CD-ROM publicly available does not violate a licensing agreement or
|
|
copyright. Also, inform the library staff that the material on the
|
|
CD-ROM is freely distributable. Follow up to make sure it is
|
|
available on the shelves.
|
|
</ol>
|
|
<P> <HR> <P>
|
|
<center><H3> Canons of Conduct </H3> </center>
|
|
<ol>
|
|
<li>As a representative of the Linux community, participate in mailing
|
|
list and newsgroup discussions in a professional manner. Refrain
|
|
from name-calling and use of vulgar language. Consider yourself a
|
|
member of a virtual corporation with Mr. Torvalds as your CEO.
|
|
Your words will either enhance or degrade the image the reader has
|
|
of the Linux community.
|
|
|
|
<li>Avoid hyperbole and unsubstantiated claims at all costs. It's
|
|
unprofessional and will result in unproductive discussions.
|
|
|
|
<li>A thoughtful, well-reasoned response to a posting will not only
|
|
provide insight for your readers, but will also increase their
|
|
respect for your knowledge and abilities.
|
|
|
|
<li>Don't bite if offered flame-bait. Too many threads degenerate into
|
|
a ``My O/S is better than your O/S'' argument. Let's accurately
|
|
describe the capabilities of Linux and leave it at that.
|
|
|
|
<li>Always remember that if you insult or are disrespectful to someone,
|
|
their negative experience may be shared with many others. If you
|
|
do offend someone, please try to make amends.
|
|
|
|
<li>Focus on what Linux has to offer. There is no need to bash the
|
|
competition. We have a good, solid product that stands on its own.
|
|
|
|
<li>Respect the use of other operating systems. While Linux is a
|
|
wonderful platform, it does not meet everyone's needs.
|
|
|
|
<li>Refer to another product by its proper name. There's nothing to be
|
|
gained by attempting to ridicule a company or its products by using
|
|
``creative spelling''. If we expect respect for Linux, we must
|
|
respect other products.
|
|
|
|
<li>Give credit where credit is due. Linux is just the kernel.
|
|
Without the efforts of people involved with the GNU project, MIT,
|
|
Berkeley and others too numerous to mention, the Linux kernel would
|
|
not be very useful to most people.
|
|
|
|
<li>Don't insist that Linux is the only answer for a particular
|
|
application. Just as the Linux community cherishes the freedom that
|
|
Linux provides them, Linux only solutions would deprive others of
|
|
their freedom.
|
|
|
|
<li>There will be cases where Linux is not the answer. Be the first to
|
|
recognize this and offer another solution.
|
|
</ol>
|
|
<P> <HR> <P>
|
|
<center><H3> User Groups </H3></center>
|
|
<ol>
|
|
<li>Participate in a local user's group. If one does not exist in your
|
|
area, start one.
|
|
|
|
<li>Make speakers available to organizations interested in Linux.
|
|
|
|
<li>Issue press releases about your activities to your local media.
|
|
|
|
<li>Discus the Linux Advocacy HOWTO at a meeting. Brainstorm and
|
|
submit new ideas.
|
|
</ol>
|
|
<P> <HR> <P>
|
|
<center><H3>Acknowledgments </H3></center>
|
|
<P>
|
|
Grateful acknowledgment is made to all contributors, including:
|
|
<P>
|
|
Jon "maddog" Hall, <A HREF="mailto:maddog@zk3.digital.com">
|
|
maddog@zk3.digital.com </A> <BR>
|
|
Greg Hankins, <A HREF="mailto:gregh@cc.gatech.edu">gregh@cc.gatech.edu</A><BR>
|
|
Eric Ladner, <A HREF="mailto:eladner@goldinc.com">eladner@goldinc.com</A><BR>
|
|
Martin Michlmayr, <A HREF="mailto:tbm@sypher.com">tbm@sypher.com</A><BR>
|
|
C. J. Suire, <A HREF="mailto:suire@datasync.com">suire@datasync.com</A><BR>
|
|
Lars Wirzenius, <A HREF="mailto:liw@iki.fi">liw@iki.fi</A><BR>
|
|
</BODY>
|
|
</HTML>
|