From: Ray Bryant <raybry@engr.sgi.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Call for [More] Papers -- OT
Date: Wed, 20 Nov 2002 10:30:45 -0600 [thread overview]
Message-ID: <3DDBB8B5.6D0F1CC8@engr.sgi.com> (raw)
I know this is off topic for this list, but the Freenix track of the
2003 Usenix Conference is looking for additional papers. The submission
deadline was Monday, Nov 18th, but this has been extended to Monday,
Nov 25th.
Freenix is a special track within the Usenix Annual Technical
Conference. The Freenix Program Committee is looking for papers about
projects with a solid emphasis on nurturing the open source and
freely-available software communities. Freenix papers should advance
the state of the art of freely-redistributable software or otherwise
provide useful information to those faced with deploying, selling, or
using free software in the field.
Freenix is also designed to assist an free or open source developer who
has an interesting project but does not have experience in writing a
conference paper and who would like to write such a paper. A member of
the program committee will be assigned as a shepherd to assist in
getting the paper ready for final publication.
Submission is easy. While you can submit a full paper, you can also
submit just an extended abstract. Freenix is thus well suited to
projects that are currently underway but are not necessarily complete at
the present time. Freenix is also a useful forum for you to increase
the exposure of your free or open source project in order to obtain more
users or collaborators.
Further details are given at:
http://www.usenix.org/events/usenix03/cfp/freenix.html
--
Best Regards,
Ray
-----------------------------------------------
Ray Bryant SGI
512-453-9679 (work) 512-507-7807 (cell)
raybry@sgi.com raybry@austin.rr.com
-----------------------------------------------
reply other threads:[~2002-11-20 16:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DDBB8B5.6D0F1CC8@engr.sgi.com \
--to=raybry@engr.sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).