From: David Lloyd <lloy0076@adam.com.au>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Conference (Mini Conference)
Date: Sat, 15 Feb 2003 19:44:27 +1030 [thread overview]
Message-ID: <20030215194427.1cdcf027.lloy0076@adam.com.au> (raw)
In-Reply-To: <15949.64158.192213.528012@notabene.cse.unsw.edu.au>
Neil,
> That's "Linux Conference, Australia" or the acronym comes out wrong
> :-)
True.
> I don't think it would be out of order at all.
> Are you an Adelaide local? Are you offering to organise?
I am an Adelaide local and I could organise it, however I am also
organising "educationaLinux 2004" (the Australian annual educational
Linux conference thing). I could direct both but I don't want to spread
myself too thinly.
> One must wonder, though, if we take too many topics into special
> mini-conferences, what will be left for the main conference??
That's a point. However there seems to be so much one could talk about,
discuss and learn about the Linux kernel that you could easily spend the
whole _week_ on it alone.
> I understand that Perth LCA had many more submissions than they could
> accept. Possibly a kernel mini-conf could give opportunities to some
> of the kernel-oriented speakers who aren't accepted for the main
> conference...
Or we could carefully pitch the "Mini Conference" to people who were
technical people who understand kernel code [i.e. make it a really,
really technical thing] and the conference at a slightly lesser, but
still technical, level.
DSL
--
I am big, it's the pictures that got small!
(Norma Desmond, Sunset Boulevard)
prev parent reply other threads:[~2003-02-15 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 5:44 David Lloyd
2003-02-15 8:30 ` Neil Brown
2003-02-15 9:14 ` David Lloyd [this message]
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=20030215194427.1cdcf027.lloy0076@adam.com.au \
--to=lloy0076@adam.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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
all inboxes | Powered by JetHome®