9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] WIP session at IWP9
Date: Tue, 27 Nov 2007 07:49:31 -0600	[thread overview]
Message-ID: <a4e6962a0711270549kfd6075dm18798a566890a37b@mail.gmail.com> (raw)
In-Reply-To: <509071940711262322m4c8c54bfmc07b453c0d3dbb8b@mail.gmail.com>

On Nov 27, 2007 1:22 AM, Anthony Sorace <anothy@gmail.com> wrote:
> I saw that the program draft has been posted
> (http://plan9.bell-labs.com/iwp9/programme.pdf) - neat! Looks like an
> interesting lineup. Can someone talk briefly about what the
> Work-in-Progress session at the end is about? That is, is this content
> provided by the organizers, or is it more free-form time for
> attendees?
>

The initial idea was for folks attending to talk about what they were
working on without having to prepare a formal
paper/30-minute-presentation.  I'm not sure what the final format is,
but one suggestion was 3-slides/roughly-5-minutes per topic with a
short discussion time afterwards -- probably maxing out at 10 minutes.
 The idea is to be short and pithy, not get into extended design
discussions.  Perhaps if there is slack time, topics that folks are
interested in can be revisited -- either in front of the group or over
coffee/beer.  (mmm...delicious coffee beer)  Individuals can present
more than one topic, but we may have to revisit that if there is too
much of a time crunch.  For example, I've got a few different things I
want to touch in on -- v9fs, multi-dimension-file-systems, warren, a
Plan 9/Inferno port to RAMP, and maybe some discussion of what's
happening with libOS these days (we'll already be covering the blue
gene update in our talk).  Of course, given that that's almost 30
minutes worth of topics, I may have to selectively trim a bit ;)

Ideally, folks will have their slides prepped ahead of time and in PDF
so we can just dump them all on a laptop so we don't have to deal with
5 minutes of setup time per person.

               -eric


      parent reply	other threads:[~2007-11-27 13:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27  7:22 Anthony Sorace
2007-11-27 10:19 ` Gorka Guardiola
2007-11-27 17:25   ` Anthony Sorace
2007-11-27 19:51     ` Pietro Gagliardi
2007-11-27 22:05       ` andrey mirtchovski
2007-11-27 23:35         ` Eric Van Hensbergen
2007-11-28 19:30         ` Anant Narayanan
2007-11-28 19:41           ` ron minnich
2007-11-28 20:26             ` ron minnich
2007-11-28 20:39             ` Sape Mullender
2007-11-28 20:47               ` Pietro Gagliardi
2007-11-28 22:45                 ` Axel Belinfante
2007-11-28 20:52               ` ron minnich
2007-11-28 22:37                 ` lejatorn
2007-11-29  1:38                 ` Aki Nyrhinen
2007-11-28 21:47             ` Francisco J Ballesteros
2007-11-28 22:59             ` Wes Kussmaul
2007-11-28 23:05               ` Wes Kussmaul
2007-11-27 13:49 ` Eric Van Hensbergen [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=a4e6962a0711270549kfd6075dm18798a566890a37b@mail.gmail.com \
    --to=ericvh@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).