mirror of https://github.com/tLDP/LDP
476 lines
16 KiB
Plaintext
476 lines
16 KiB
Plaintext
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V3.1//EN">
|
|
|
|
<article id="index">
|
|
|
|
<!-- Header -->
|
|
|
|
<artheader>
|
|
<title>Event HOWTO</title>
|
|
|
|
<author>
|
|
<firstname>Mark</firstname>
|
|
<othername>F.</othername>
|
|
<surname>Komarinski</surname>
|
|
<affiliation>
|
|
<orgname>VA Linux Systems</orgname>
|
|
<address>
|
|
<email>mkomarinski@valinux.com</email>
|
|
</address>
|
|
</affiliation>
|
|
</author>
|
|
|
|
<revhistory>
|
|
<revision>
|
|
<revnumber>v0.1</revnumber>
|
|
<date>Dec 4, 2000</date>
|
|
<authorinitials>mfk</authorinitials>
|
|
<revremark>
|
|
Comments from John Shipman, added some more notes
|
|
</revremark>
|
|
</revision>
|
|
<revision>
|
|
<revnumber>v0.05</revnumber>
|
|
<date>8 Nov 2000</date>
|
|
<authorinitials>mfk</authorinitials>
|
|
<revremark>
|
|
First revision. Comments from readers is appreciated.
|
|
</revremark>
|
|
</revision>
|
|
|
|
</revhistory>
|
|
|
|
<abstract>
|
|
<indexterm>
|
|
<primary>abstract</primary>
|
|
</indexterm>
|
|
|
|
<para>
|
|
The purpose of this document is to show you how to create good
|
|
presentations for almost any sort of Linux event.
|
|
</para>
|
|
|
|
</abstract>
|
|
|
|
</artheader>
|
|
|
|
|
|
<!-- Section1: intro -->
|
|
|
|
<sect1 id="intro">
|
|
<title>Introduction</title>
|
|
|
|
<indexterm>
|
|
<primary>!introduction</primary>
|
|
</indexterm>
|
|
|
|
<para>
|
|
While many Linux users will give presentations at Linux User
|
|
Group (LUG) meetings, Expos, and other conferences, not everyone
|
|
is effective at giving presentations. Much like public speaking,
|
|
a presenter needs to know how to communicate with their audience
|
|
so that their topic is clear and understood by all. Topics
|
|
that may interest users can easily be lost with ineffective
|
|
presentations. Hopefully this document will spell out how you can
|
|
do this properly.
|
|
</para>
|
|
|
|
<!-- Section2: copyright -->
|
|
|
|
<sect2 id="copyright">
|
|
<title>Copyright Information</title>
|
|
|
|
<para>
|
|
This document is copyrighted (c) 2000 Mark F. Komarinski and is
|
|
distributed under the terms of the Linux Documentation Project
|
|
(LDP) license, stated below.
|
|
</para>
|
|
|
|
<para>
|
|
Unless otherwise stated, Linux HOWTO documents are
|
|
copyrighted by their respective authors. Linux HOWTO documents may
|
|
be reproduced and distributed in whole or in part, in any medium
|
|
physical or electronic, as long as this copyright notice is
|
|
retained on all copies. Commercial redistribution is allowed and
|
|
encouraged; however, the author would like to be notified of any
|
|
such distributions.
|
|
</para>
|
|
|
|
<para>
|
|
All translations, derivative works, or aggregate works
|
|
incorporating any Linux HOWTO documents must be covered under this
|
|
copyright notice. That is, you may not produce a derivative work
|
|
from a HOWTO and impose additional restrictions on its
|
|
distribution. Exceptions to these rules may be granted under
|
|
certain conditions; please contact the Linux HOWTO coordinator at
|
|
the address given below.
|
|
</para>
|
|
|
|
<para>
|
|
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.
|
|
</para>
|
|
|
|
<para>
|
|
If you have any questions, please contact
|
|
<email>linux-howto@metalab.unc.edu</email>
|
|
</para>
|
|
</sect2>
|
|
|
|
<!-- Section2: disclaimer -->
|
|
|
|
<sect2 id="disclaimer">
|
|
<title>Disclaimer</title>
|
|
|
|
<para>
|
|
No liability for the contents of this documents can be accepted.
|
|
Use the concepts, examples and other content at your own risk.
|
|
As this is a new edition of this document, there may be errors
|
|
and inaccuracies, that may of course be damaging to your system.
|
|
Proceed with caution, and although this is highly unlikely,
|
|
the author do not take any responsibility for that.
|
|
</para>
|
|
|
|
<para>
|
|
All copyrights are held by their by their respective owners, unless
|
|
specifically noted otherwise. Use of a term in this document
|
|
should not be regarded as affecting the validity of any trademark
|
|
or service mark.
|
|
</para>
|
|
|
|
<para>
|
|
Naming of particular products or brands should not be seen
|
|
as endorsements.
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
<!-- Section2: newversions-->
|
|
|
|
<sect2 id="newversions">
|
|
<title>New Versions</title>
|
|
|
|
<para>
|
|
New versions can be found at the LDP web site <ulink url="http://www.linuxdoc.org">http://www.linuxdoc.org/</ulink>
|
|
</para>
|
|
</sect2>
|
|
|
|
<!-- Section2: credits -->
|
|
|
|
<sect2 id="credits">
|
|
<title>Credits</title>
|
|
|
|
<para>
|
|
I'd like to thank Prof. Brad Broughton, Technical Communication
|
|
Department, Clarkson University. He taught a number of courses
|
|
on effective presentations and public speaking. I don't always
|
|
follow his rules, but I know what they are.
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
<!-- Section2: feedback -->
|
|
|
|
<sect2 id="feedback">
|
|
<title>Feedback</title>
|
|
|
|
<para>
|
|
Feedback is most certainly welcome for this document. Without
|
|
your submissions and input, this document wouldn't exist. Please
|
|
send your additions, comments and criticisms to the following
|
|
email address : <email>markk@linuxdoc.org</email>.
|
|
</para>
|
|
</sect2>
|
|
|
|
</sect1>
|
|
|
|
<!-- Section1: intro: END -->
|
|
|
|
|
|
<!-- Section1: samples -->
|
|
|
|
<sect1 id="gettingstarted">
|
|
<title>Getting Started</title>
|
|
|
|
<para>
|
|
Before you even give a presentation, there are a few things
|
|
you have to do:
|
|
</para>
|
|
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para>
|
|
Choose a topic.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
Submit your topic to a show or LUG. (and get it accepted!)
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
Create a presentation from the topic.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
Give the presentation.
|
|
</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
<para>
|
|
Contrary to poular belief, each of these may be as hard as all the
|
|
others. Choosing a topic for some may be easy, based on their
|
|
expertise, whereas a Linux jack-of-all-trades may be stuck choosing
|
|
a topic. Those comfortable with public speaking may have trouble
|
|
designing the slides, and so on.
|
|
</para>
|
|
<para>
|
|
So let's jump right in and hit all the topics and get you started!
|
|
</para>
|
|
</sect1>
|
|
|
|
<sect1 id="topic">
|
|
<title>Choosing a topic</title>
|
|
<para>
|
|
In many cases, you can choose your topic based on the area of expertise
|
|
you have. If you're a known (or unknown?) expert on RAID, you can give
|
|
a presentation on RAID. But what do you talk about on RAID? Do you
|
|
talk about the design of the controller drivers under Linux 2.4? Do
|
|
you talk about installing Linux on a RAID device? Case study?
|
|
</para>
|
|
<para>
|
|
Unfortunately, these are things you'll have to think about and decide
|
|
on your own. Your best bet is to think of a generic enough subject,
|
|
and change it based on your audience (we'll get into this
|
|
later on). If you're talking to a more advanced LUG/USENIX crowd,
|
|
you can give a more advanced presentation, whereas newbie groups can
|
|
get a presentation of what RAID is and how it works. The basic idea
|
|
is to keep the intended audience in mind at all times.
|
|
</para>
|
|
</sect1>
|
|
<sect1 id="submit">
|
|
<title>Submitting your topic</title>
|
|
<para>
|
|
Once you have the basic idea of what you want to present, you have
|
|
to get it accepted by groups and get the opportunity to show it.
|
|
Your best line of strategy is to start off giving your intended
|
|
presentation to a local LUG and let them critique it. Audience
|
|
feedback is cruicial, especially if you have not done a presentation
|
|
before.
|
|
</para>
|
|
<para>
|
|
So what's the secret for talking to a LUG? In many cases, just offer.
|
|
LUGs like to have speakers for each meeting to give a reason
|
|
to get together other than go for a beer after the meeting.
|
|
</para>
|
|
<para>
|
|
In terms of conferences that you would like to attend, check the major
|
|
conferences and expos out there. Many are listed at Linux web sites,
|
|
some send out a call for papers (CFP) to approprate discussion lists,
|
|
like <email>discuss@linuxdoc.org</email>. Many will have
|
|
either an e-mail CFP, or have you fill out a web form.
|
|
</para>
|
|
<para>
|
|
I cannot comment on what papers are accepted or declined, mostly
|
|
because I don't know how it works. The best I can say is to see what
|
|
topics have been selected in the past and tailor your abstract that way.
|
|
</para>
|
|
<para>
|
|
Assuming your presentation has been selected, try and get some information
|
|
about the location, dates, time, and so on. This will have a lot of bearing
|
|
on how your presentation is laid out. A presentaton using printed slides
|
|
will appear different on screen than one with an LCD projector that
|
|
connects to your laptop. In some cases, you will need to bring your
|
|
own laptop to the presentation.
|
|
</para>
|
|
</sect1>
|
|
|
|
<sect1 id="creating">
|
|
<title>Creating your Presentation</title>
|
|
<para>
|
|
There are a number of programs for creating presentations. What you
|
|
use should really be a personal preference. However, there are a few
|
|
choices for you to use.
|
|
</para>
|
|
<table frame="all">
|
|
<title>Presentation applications</title>
|
|
<tgroup cols="3">
|
|
<thead>
|
|
<row>
|
|
<entry>Application Name</entry>
|
|
<entry>URL</entry>
|
|
<entry>Notes</entry>
|
|
</row>
|
|
</thead>
|
|
<tbody>
|
|
<row>
|
|
<entry>MagicPoint</entry>
|
|
<entry><ulink url="http://www.Mew.org/mgp/">http://www.Mew.org/mgp/</ulink></entry>
|
|
<entry>Presentation-only. Reads text files for creating presentation. Exports to PS and HTML</entry>
|
|
</row>
|
|
<row>
|
|
<entry>StarOffice</entry>
|
|
<entry><ulink url="http://www.staroffice.com/">http://www.staroffice.com</ulink></entry>
|
|
<entry>Good conversion to and from Microsoft PowerPoint. Not really good for laptops, as it consumes a lot of memory and CPU cycles.</entry>
|
|
</row>
|
|
<row>
|
|
<entry>Applixware Office</entry>
|
|
<entry><ulink url="http://www.vistasource.com/">http://www.vistasource.com</ulink></entry>
|
|
<entry>Commercial application, but smaller requirements than Star Office.</entry>
|
|
</row>
|
|
</tbody>
|
|
</tgroup>
|
|
</table>
|
|
<para>
|
|
So how do you create the your content? First, you'll want to have
|
|
some introductory information. Your first slide should contain the
|
|
title of the presentation, your name, and who you're representing
|
|
(if anyone). Remember that it's good form to include the name of
|
|
the organization that is paying for your trip, even if they're not
|
|
who you're representing.
|
|
</para>
|
|
<para>
|
|
Your second slide should contain the agenda for the remainder
|
|
of the presentation. This serves two purposes - it not only
|
|
tells the audience what to expect, but serves as an outline
|
|
for you as you create the slides.
|
|
</para>
|
|
<para>
|
|
Your third (or fourth, depending on how big the agenda is) should
|
|
contain some information about you. This gives you credibility
|
|
with the audience as to your expertise with the subject matter.
|
|
</para>
|
|
<para>
|
|
After that, it is up to you to start creating your slides. However,
|
|
here's a few hints to keep in mind as you go along:
|
|
</para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>
|
|
Make the text of the slides big, and the amount of text
|
|
small. You want everyone to be able to read what is on
|
|
the slide. A rule of thumb is that characters should
|
|
be 1 inch high for every 10 feet that an audience member
|
|
will be away from the screen.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
There is no real need to write in full sentences. You
|
|
will want to make short points, since your talking will
|
|
fill in the details.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
If you use backgrounds in your slides, make them of light
|
|
colors. Dark colors will contrast the text when they
|
|
are printed out as handouts for attendees.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
Stick to one topic per slide. You can have multiple slides
|
|
per topic, just title them "Topic", "Topic (cont'd)", or number
|
|
them.
|
|
</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</sect1>
|
|
<sect1 id="presenting">
|
|
<title>Giving your presentation</title>
|
|
<para>
|
|
Before you give your presentation to a group of people, give it
|
|
a test run to a friend or SO. This lets you know how well
|
|
the flow of the presentation is, plus may give ideas for improvement.
|
|
You may also just want to give it in front of a mirror.
|
|
</para>
|
|
<para>
|
|
If you have never taken a public speaking class, or given presentations
|
|
to large groups, the first few times you do this it may seem unnerving.
|
|
As I mentioned earlier, it may be easier to start with your local LUG
|
|
and get used to talking to groups of people - the local LUG will be
|
|
filled with a friendly audience and you will be more at ease.
|
|
</para>
|
|
<para>
|
|
When talking to a large audience, keep the following in mind:
|
|
</para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>
|
|
Don't just read the text on the slides. Anyone can put slides up
|
|
and read the text on it. You are an expert! Make like one.
|
|
Anecdotes (humorous or not) can increase the audience's interest
|
|
in the subject, and increase your credibility. Expand on topics
|
|
that you think should be expanded.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
SPEAK SLOWLY. Many people when talking with friends or in stresful
|
|
situations will talk rapidly. Not only does this make your
|
|
presentation much slower than it needs to be, but makes it hard
|
|
for your audience to understand you. Also remember that not
|
|
all of your audience speaks your language as their first language.
|
|
On the same note, don't speak in a monotone.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
Keep eye contact with the audience. Every now and then, look up
|
|
from your screen and scan the audience. If this makes you
|
|
nervous, look across the tops of the heads. From the perspective
|
|
of the audience, you are looking at them. Look up, and scan from
|
|
one side of the room to the other, then look back at your screen.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
Feedback from microphones can cause headaches for all around.
|
|
Test your microphone setup before talking. Ask before you
|
|
start your presentation if everyone can hear you clearly.
|
|
If not, adjust your microphone. Smaller rooms may not
|
|
have microphones, so you will need to speak loudly.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
If you do not have a microphone, try and face your audience as
|
|
much as possible. Your voice will carry better.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
Do not let yourself get sidetracked. Stay on the topic. If
|
|
a member of the audience tries to get you off topic too far,
|
|
offer to discuss it after the presentation. Others
|
|
who are interested can take part then.
|
|
</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</sect1>
|
|
<!-- Section1: examples: END -->
|
|
|
|
</article>
|
|
|
|
<!-- Keep this comment at the end of the file
|
|
Local variables:
|
|
mode: sgml
|
|
sgml-omittag:t
|
|
sgml-shorttag:t
|
|
sgml-namecase-general:t
|
|
sgml-general-insert-case:lower
|
|
sgml-minimize-attributes:nil
|
|
sgml-always-quote-attributes:t
|
|
sgml-indent-step:1
|
|
sgml-indent-data:nil
|
|
sgml-parent-document:nil
|
|
sgml-exposed-tags:nil
|
|
sgml-local-catalogs:nil
|
|
sgml-local-ecat-files:nil
|
|
End:
|
|
-->
|