ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <boaz@plexistor.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Draft Kernel Summit track agenda
Date: Thu, 8 Nov 2018 19:31:01 +0200	[thread overview]
Message-ID: <6d3fa1f2-43a6-cd34-208d-c02c68ec9dea@plexistor.com> (raw)
In-Reply-To: <20181108160507.GA1080@thunk.org>

On 08/11/18 18:05, Theodore Y. Ts'o wrote:
> On Thu, Nov 08, 2018 at 02:28:35PM +0200, Boaz Harrosh wrote:
>>
>> I would like to please ask again for a slot to talk about ZUFS, at one of the TBD
>> slots above?
>>
>> It is a very big project, that I would love to discuss with the Linux community
>> and developers. I believe it is a very important project in the up coming years.
> 
> So for anyone who wants to schedule one the TBD / Unconference slots,
> please send a note to the ksummit-discuss list with a [TOPIC] subject
> prefix.  That note should include a description of what will be
> discussed, and what the goals / success criteria for that session.
> Also please include scheduling conflicts and/or a suggested time slot
> that you would prefer.
> 
> Scheduling will be based by people responding to the mail thread ---
> especially people who will actually *be* at the Plumber's Conference
> in vancouver.  If there's general interest and a set of issues where
> face to face discussion would be constructive, those topics will be
> given priority over people who just want to publicize their project or
> just give a status update.  Status updates can always be very
> effectively given via e-mail.  :-)
> 
> I and other members of the program committee will be monitoring the
> mailing list during the conference, so the same procedure should be
> used next week.  For now though, I'd like to keep the remaining
> sessions unscheduled to give everyone a fair shot at the remaining
> slots.  So for people who want to propose topics, please submit
> [TOPIC] suggestions to the ksummit mailing list.  We'll do another
> review and scheduling pass next week on Monday, right before the
> conference starts.
> 

Cool thanks I will resend my [TOPIC]

> Cheers,
> 
> 						- Ted

Boaz

  reply	other threads:[~2018-11-08 17:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 17:47 Theodore Y. Ts'o
2018-11-07 21:05 ` Thomas Gleixner
2018-11-07 21:53 ` Theodore Y. Ts'o
2018-11-08 10:06 ` Greg KH
2018-11-08 12:28 ` Boaz Harrosh
2018-11-08 15:40   ` Greg KH
2018-11-08 16:05   ` Theodore Y. Ts'o
2018-11-08 17:31     ` Boaz Harrosh [this message]
2018-11-08 18:05       ` Matthew Wilcox

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=6d3fa1f2-43a6-cd34-208d-c02c68ec9dea@plexistor.com \
    --to=boaz@plexistor.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tytso@mit.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