Linux Advocacy mini-HOWTO
Paul.L.Rogers@li.orgv0.5c, 3 May 2000
This document provides suggestions for how the Linux community can effectively advocate the use of Linux.
This is the Linux Advocacy mini-HOWTO and is intended to provide guidelines and ideas to assist with your Linux advocacy efforts.
This mini-HOWTO was inspired by Jon ``maddog'' Hall when he responded to a request for feedback on guidelines for advocating Linux during
guidelines and observed that they were the basis of a list of ``canons of conduct'' that would benefit the Linux community.
This document is available in HTML form at
http://www.datasync.com/rogerspl/Advocacy-HOWTO.html.
Nat Makarevitch <nat@nataa.fr.eu.org> has translated this document into French.
Chie Nakatani <jeanne@mbox.kyoto-inet.or.jp> has translated this document into Japanese.
Janusz Batko <janus@krakow.linux.org.pl> has translated this document into Polish.
Bruno H. Collovini <buick@microlink.com.br> has translated this document into Portuguese.
Mauricio Rivera Pineda <rmrivera@hotmail.com> has translated this document into Spanish.
The author and maintainer of the Linux Advocacy mini-HOWTO is Paul L. Rogers <Paul.L.Rogers@li.org>.
Comments and proposed additions are welcome.
If you need to know more about the Linux Documentation Project or about Linux HOWTO's, feel free to contact the supervisor Tim Bynum <linux-howto@sunsite.unc.edu>. Tim Bynum will post this document to several national and international newsgroups on a monthly basis.
A personal note: Due to various circumstances, I have not been able to dedicate as much time to maintaining this mini-HOWTO and interacting with the Linux community as I would have desired. I apologize for this and if you have attempted to contact me and I was slow in responding, please forgive me being so inconsiderate. While I still have many other commitments, I am anticipating that they will start requiring less time to meet and allow me to catch up on other parts of my life. I appreciate your patience and would like to extend a special thanks to all who have taken the time to suggest additions and corrections.
This mini-HOWTO is Copyright (c) 1996-2000 by Paul L. Rogers. All rights reserved.
A verbatim copy may be reproduced or distributed in any medium physical or electronic without permission of the author. Translations are similarly permitted without express permission if it includes a notice on who translated it.
Short quotes may be used without prior consent by the author. Derivative work and partial distributions of the Advocacy mini-HOWTO must be accompanied with either a verbatim copy of this file or a pointer to the verbatim copy.
Commercial redistribution is allowed and encouraged; however, the author would like to be notified of any such distributions.
In short, we wish to promote dissemination of this information through as many channels as possible. However, we do wish to retain copyright on the HOWTO documents, and would like to be notified of any plans to redistribute the HOWTOs.
We further want that all information provided in the HOWTOs is disseminated. If you have questions, please contact Tim Bynum, the Linux HOWTO coordinator, at linux-howto@sunsite.unc.edu.
The Linux community has known for some time that for many applications, Linux is a stable, reliable, robust (although not perfect) product. Unfortunately, there are still many people, including key decision-makers, that are not aware of the existence of Linux and its capabilities.
If Linux and the many other components that make up a Linux distribution are to reach their full potential, it is critical that we reach out to prospective ``customers'' and advocate (being careful not to promise too much) the use of Linux for appropriate applications. The reason that many a company's products have done well in the marketplace is not so much due to the product's technical superiority but the company's marketing abilities.
If you enjoy using Linux and would like to contribute something to the Linux community, please consider acting on one or more of the ideas in this mini-HOWTO and help others learn more about Linux.
Lars Wirzenius, former comp.os.linux.announce moderator and long-time Linux activist, also has some thoughts about Linux advocacy.
Eric S. Raymond provides an analysis of why the development model used by the Linux community has been so successful.
The free software community has recognized that the terms "free software" and "freely available software" are not appropriate in all contexts. For more information about using the term "open-source software" when marketing "free software", please visit the Open Source site.
If you need to brush up on your Linux sales techniques, take a look at the Linuxmanship essay by Donald B. Marti, Jr.
The Linux PR site discusses the importance of press releases to the Linux community. Another way to gain valuable experience in this area is to organize a !NetDay? at a local school using the guidelines presented in the
Linux International's goal is to promote the development and use of Linux.
The Linux Documentation Project is an invaluable resource for Linux advocates.
The Linux Center Project provides a thematical index of resources about Linux and free software.
The Linux Business Applications site provides a forum for organizations that depend on Linux for day-to-day business operations to share their experiences.
Linux Enterprise Computing and Freely Redistributable Software in Business cover resources and topics of interest to those deploying Linux in a business/commercial/enterprise setting.
The Linux Advocacy Project's goal is to encourage commercial application developers to provide native Linux versions of their software.
The Linux CD and Support Giveaway program is helping make Linux more widely available by encouraging the reuse of Linux CD-ROMs.
Specialized Systems Consultants, Inc. (SSC) hosts the Linux Resources site and publishes the Linux Journal.
The linux-biz mailing list is a forum created to discuss the use of Linux in a business environment.
The Linux Mission Critical Systems survey documents successful existing systems which have a large load and are up 24 hours per day.
A number of online publications are now devoted to covering Linux. These include:
*
Linuxove noviny''
*
Linux Gazette''
*
PLUTO Journal''. *
Additional links to online publications can be found at the Linux Documentation Project and the Linux Center Project.
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.
*
offer to provide pointers to appropriate information (Web pages, magazine articles, books, consultants, ...). If you haven't actually used the proposed solution, say so.
*
register with the Linux Speakers Bureau.
*
sure that they are able to use their system effectively.
*
operate only in text-mode. Make sure that they are aware of the availability of graphical applications, such as the Gimp.
*
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.
*
a presentation about Linux.
*
employer's Information Technology group.
*
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.
*
``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.
*
considering the adoption of Linux. Companies such as Caldera, Cygnus Solutions, Red Hat, and S.u.S.E. offer support for some or all components of a typical Linux distribution. In addition, the Linux Consultants HOWTO provides a listing of companies providing commercial Linux related support. Of course, some of the best support is found in the comp.os.linux and linux newsgroup hierarchies.
*
open-source 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 Apache, GNU Emacs, Perl and the Linux kernel.
*
Linux Counter.
*
Linux International ( li@li.org) and similar organizations.
*
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.
*
give preference to books written by the author of the software. The royalties that authors receive from book sales may be the only monetary compensation received for their efforts. <-- Need to fix or change the Powered by Linux text -->
*
Powered by Linux page and suggest that banners promoting Linux, Apache, GNU, Perl ... be displayed on their site.
*
open-source software, please consider assisting the free software community by:
*
*
*
*
*
*
*
*
*
The Linux Documentation Project provides a list of Linux and Linux-related projects.
*
issues to deal with than the selection of a computing environment. *
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 Chief Executive Officer. Your words will either enhance or degrade the image the reader has of the Linux community.
*
unprofessional and will result in unproductive discussions.
*
only provide insight for your readers, but will also increase their respect for your knowledge and abilities.
*
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.
*
to someone, their negative experience may be shared with many others. If you do offend someone, please try to make amends.
*
the competition. Linux is a good, solid product that stands on its own.
*
a wonderful platform, it does not meet everyone's needs.
*
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.
*
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.
*
application. Just as the Linux community cherishes the freedom that Linux provides them, Linux only solutions would deprive others of their freedom.
*
answer. Be the first to recognize this and offer another solution. *
index of Linux User Group registries is part of the Linux Documentation Project. If a user group does not exist in your area, start one.
*
Linux User Group HOWTO covers many of the issues involved with starting an user group and discusses the importance of Linux advocacy as one of the goals of a user group.
*
*
press releases about your activities to your local media.
*
local community organizations. Of course, the installation process must include training the user community to use the system and adequate documentation for ongoing maintenance.
*
and submit new ideas. *
Linux support and other user's experiences with the product in a Linux environment.
*
services. Encourage them to have their product listed in the Linux Commercial HOWTO.
*
organizations such as the Free Software Foundation, the Linux Development Grant Fund, the XFree86 Project or Software in the Public Interest. If possible, make a personal donation to these or other organizations that support open-source software. Don't forget that some employers offer a matching gift program program.
*
Linux, contact the vendor and request a native Linux version. *
press clippings that mention Linux, GNU and other freely redistributable software. When you see such an article, please send the following information to clippings@li.org:
*
*
*
*
*
*
*
*
*
an article, review or news story, send the details, including the above information, to li@li.org so that an appropriate response can be sent to the publisher. If you contact the publisher directly, be professional and sure of your facts.
*
press releases to appropriate news services on a regular basis. *
Grateful acknowledgement is made to all contributors, including:
Kendall G. Clark <kclark@cmpu.net> Wendell Cochran <atrypa@eskimo.com> Bruno H. Collovini <buick@microlink.com.br> Allan "Norm" Crain <allanc@idea-inc.com> Jon "maddog" Hall <maddog@zk3.digital.com> Greg Hankins <gregh@cc.gatech.edu> Eric Ladner <eladner@goldinc.com> Chie Nakatani <jeanne@mbox.kyoto-inet.or.jp> Daniel P. Kionka <dkionka@worldtalk.com> Nat Makarevitch <nat@nataa.fr.eu.org> Martin Michlmayr <tbm@cyrius.com> Rafael Caetano dos Santos <rcaetano@dijkstra.ime.usp.br> Idan Shoham <idan@m-tech.ab.ca> Adam Spiers <adam.spiers@new.ox.ac.uk> C. J. Suire <suire@datasync.com> Juhapekka Tolvanen <juhtolv@silmu.cc.jyu.fi> Lars Wirzenius <liw@iki.fi> Sean Woolcock <sbwoolco@eos.ncsu.edu>
No other page links to HowToAdvocacy yet.
