[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Linux Expo call for papers (fwd)
Hi Blinuxers,
despite this event seems not to be related directly to
Linux blind support, there is no reason why it could not
be used to promote this theme.
Take a look at the the progam comittee, which sounds really promising.
Enjoy!
hans
---------- Forwarded message ----------
Date: Mon, 26 Oct 1998 12:59:19 -0800
From: Larry McVoy <lm@bitmover.com>
Reply-To: redhat-list@redhat.com
To: redhat-announce-list@redhat.com
Subject: Linux Expo call for papers
Resent-Date: 26 Oct 1998 22:05:21 -0000
Resent-From: redhat-announce-list@redhat.com
Resent-cc: recipient list not shown: ;
-------------------------------------------------------------------------------
Linux Expo 1998 Call for Papers
-------------------------------------------------------------------------------
May 18 - 22, 1999
Raleigh, North Carolina
DATES FOR REFEREED PAPER SUBMISSIONS
* Extended abstracts and/or full papers due: December 1, 1998
* Notification to authors: January 15, 1999
* Full papers due for final review: February 15, 1999
* Camera-ready full papers due: March 1, 1999
PROGRAM COMMITTEE
Marc Ewing, Red Hat Advanced Laboratories
Richard Henderson, Cygnus Solutions
Dirk Hohndel, S.u.S.E. GmbH
Larry McVoy, BitMover (Chair)
Carl Staelin, Hewlett-Packard Labs
Theodore Ts'o, MIT
Stephen Tweedie, Red Hat Software
Victor Yodaiken, New Mexico Institute of Technology
OVERVIEW
The goal of the technical track of Linux Expo is to bring
together engineers and researchers doing innovative work
associated with Linux. This will be a 4 day conference:
Tuesday 18th Pre-registration for tutorial attendees 6-9pm
Wednesday 19th Tutorials and conference registration 9-6pm
Welcome Reception 6-7pm (outdoors in mall weather
permitting)
Exhibitor set-up 3-9pm
Thursday 20th Conference 9-5pm (registrations from 8am)
Exhibits 10.30am-5pm
Free night
Friday 21st Conference (as Thursday)
Exhibits ditto
Reception in exhibit hall area 5-6.30pm
Saturday 22nd Conference 10am-4pm
Exhibits 10am-2pm
TUTORIALS
May 19th, 1999
Tutorials for both technical staff and managers will provide
immediately useful, practical information on topics such as
programming, system administration, and security. If you
are interested in proposing a tutorial, contact the tutorial
coordinator, Marc Ewing <marc@redhat.com>.
TECHNICAL SESSIONS
May 20th-22nd, 1999
The explosion of interest in Linux as a viable alternative
to both existing Unix systems and Microsoft operating
systems has led to the development of new features as well
as refinements of existing features.
We are interested in papers covering any area of Linux related
software, but we encourage authors to submit papers in the areas
of
. Linux kernel enhancements, status, future plans
. Databases on Linux
. Linux clustering
. High availability on Linux
. Performance of Linux and/or applications on Linux
. Innovations in user interface on Linux
. Linux applications, both Open Source (tm) and commercial
Besides mature work, we encourage submissions describing
exceptionally promising prototypes, or enlightening negative
results.
Where appropriate, authors will be able to demonstrate
their applications during their presentation using computers
linked to the audio-visual system and the Internet. Also,
space will be available to authors in the vendor display
room to demonstrate their work outside of their presentation
in a more relaxed and interactive environment.
WHAT TO SUBMIT
Authors must submit an extended abstract (or a full paper,
if available) by December 1, 1998. This should be 5-7 pages
long or about 2500-3500 words, not counting references and
figures. The full papers resulting from accepted abstracts
will go through an editorial review cycle with a member of
the program committee, and should end up about 8-10 pages
long. Very similar papers must not have been published or
submitted for publication elsewhere.
The object of an extended abstract is to convince the
reviewers that a good paper and a 25-minute presentation
will result. It is important to identify what has been
accomplished, to explain why it is significant, and to
compare with prior work in the field, demonstrating knowledge
of the relevant literature. The extended abstract should
represent the paper in "short form." It must include the
abstract as it will appear in the final paper. The body
of the extended abstract should be complete paragraphs,
not just an outline of the paper. (Sections present in the
full paper but omitted from the abstract may be summarized
in terse form.) Authors should include full references,
figures when available, and as is usually appropriate,
performance data. Such data also help indicate the status
of the implementation, often a crucial issue. The abstract
will be judged on significance, originality, clarity,
relevance, and correctness. (All submissions will be held
in the highest confidence prior to publication. Papers
accompanied by so called "non-disclosure agreement" forms
are not acceptable and will be returned unread.)
SUBMISSION FORMAT
In the interests of having a uniform look and feel, we are
requesting that submissions be in "groff -mgs" source format.
This will allow us to format all of the papers together, adding
a table of contents, page numbers and headers to the proceedings.
Example papers demonstrating and explaining the format, how to
do graphs, how to include postscript figures, etc., will be made
available. If you've never heard of groff, fear not, both the
program chair and the keynote speaker are old time roff hackers
and will be available for assistance.
If you would like to receive detailed guidelines for
submission and examples of extended abstracts, you may send
email to: linuxexpo@bitmover.com.
EDITORIAL, FORMATTING HELP
The program committee will provide help to authors if needed.
The committee has extensive experience in programming and in
publishing, so if you have a good idea but don't know how to
write it up, contact us.
For the formatting, an example paper with formatting instructions
will be published on the web at http://www.bitmover.com/linuxexpo/
WHERE TO SUBMIT
Please send one copy of an extended abstract to the program
chair via email. All submissions will be acknowledged.
REVIEW PROCESS
Linux Expo is adopting a policy of blind review to
ensure fairness in the review process. Author names and
affiliations will be removed from the papers. To facilitate
this, email the groff source to papers only to
linuxpapers@bitmover.com .
WORK-IN-PROGRESS REPORTS
Do you have interesting work you would like to share, or a cool
idea that is not ready to be published? Work-in-progress reports are
for you! Work-in-progress reports, scheduled during the technical
sessions, introduce new or ongoing work. The Linux Expo audience
provides valuable discussion and feedback. We are particularly
interested in presentations of student work. To schedule your
report, please contact the Works-in-progress coordinator Marc
Ewing, <marc@redhat.com>.
VENDOR DISPLAY AND DEMONSTRATIONS
Linux Expo will feature both vendor displays and
demonstrations of technologies and systems presented
in some of the refereed presentations. Authors will
be able to demonstrate their work in a more relaxed and
interactive environment. Vendors will demonstrate the
technical innovations which distinguish their products,
and attendees can "kick the tires" and play with the systems.
We invite you to take part in the Vendor Display.
Authors of papers interested in offering a demonstration,
please contact:
Yvonne Hart
yvonne@linuxexpo.org
(919) 942-3318
Fax: (919) 933-9233
REGISTRATION MATERIALS
Materials containing all details of the technical and tutorial
programs, registration fees and forms, and hotel information
will be mailed as soon as possible. If you wish to receive the
registration materials, please contact Linux Expo at:
Yvonne Hart
yvonne@linuxexpo.org
(919) 942-3318
Fax: (919) 933-9233
Thanks and see you at LinuxExpo '99!
--
To unsubscribe:
mail -s unsubscribe redhat-announce-list-request@redhat.com < /dev/null
--
To unsubscribe: mail blinux-announce-request@redhat.com with
"unsubscribe" as the Subject.