All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Guy Briggs <rgb@tricolour.ca>
To: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	lwn@lwn.net, netdev01@lists.netfilter.org, lartc@vger.kernel.org,
	netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: NetDev 0.1 Attendee clarification [was: Netdev 0.1 Call for Proposals]
Date: Fri, 12 Dec 2014 10:09:42 -0500	[thread overview]
Message-ID: <20141212150942.GV392@toccata2.tricolour.ca> (raw)
In-Reply-To: <20141203022815.GM4612@toccata2.tricolour.ca>

On 14/12/02, Richard Guy Briggs wrote:
> Netdev 0.1 Call for Proposals
> -----------------------------
> 
> Netdev 0.1 (year 0, conference 1) is a community-driven conference
> geared towards Linux netheads. Linux kernel networking and user 
> space utilization of the interfaces to the Linux kernel networking
> subsystem are the focus.

Hello fellow Linux NetHeads, sorry for the noise:

There seems to have been some questions about the intended audience for this
conference.

The 50/50 by-invitation/submission slots are for the *presenters* of the talks
and not for the audience of attendees.  *Anyone* with an interest in Linux
networking is welcome to attend this conference.

We're very sorry for the confusion and welcome you to join us.

Cheers.

> There are 4 phases/formats to Netdev 0.1
> 
> 1) Workshops (day 1)
> 
> The workshop format is inspired by Netconf and the wireless
> mini-summits, with workshops being centered around existing
> networking subsystems. workshops are intended to be an extension of
> the mailing list in the sense that many times previous
> discussions from the mailing list (or that could otherwise have
> happened there) are taken to the round-table to simplify the
> decision-making process.
> 
> The networking subsystem maintainer(s) should at least prepare a
> list of agenda items well before the workshop takes place to allow 
> participants to come prepared; this makes the discussions most productive.
> Sometimes brain-storming sessions will also be appropriate where
> being prepared is less important, for example for discussions
> around new user requirements this can be very valuable.
> 
> At the workshop meeting itself discussions prevail and notes are
> later sent back to the mailing list; presentations are typically
> - at the discretion of the chairs - only used where needed to
> clarify a problem statement for discussion.
> 
> The sitting format is round-table.
> 
> 2) BOFs (day 1)
> 
> BOFs are sessions with a potential to become a workshop in a future
> Netdev conference. The lifetime of a BOF may be only one or two 
> Netdev conference gatherings. We discourage perpetual BOFs.
> BoFs don't need to have an existing networking subsystem or mailing list.
> BOFs also don't need to strive to be upgraded to be a Workshop
> in the future. Their longevity could only be one conference.
> The sitting format could vary and be either lecture or round table format
> depending on the proposal.
> 
> 3) Tutorials (day 2)
> 
> Tutorials are generally about 2 hours long (or more at the discretion
> of the proposal).
> Tutorials are educational in nature and are presented in a classroom 
> format with a specific educational outcome for the attendees.
> 
> 4) Paper proposals (days 3 and 4)
> 
> These are classical conference paper + presentations.
> Presentations are 30 minutes long with an additional 15 minutes for Q&A
> presented in a lecture format.
> We will require paper submissions for these sessions. The committee 
> believes that a paper submission raises the quality of the presentations
> and makes it easier to build on presented ideas in the future.
> 
> The Netdev conference this year is structured to be 50% by-invitation 
> and 50% submission. We are making sure that we reach out to speakers 
> who have interesting relevant topics because we recognize most of 
> these folks would typically not be submitting papers to a conference.
> The invitation will be made by the technical committee to the individual
> speakers for workshop, paper and tutorial sessions.

Clarification is that the presenters will be split 50/50 invitation/submission
and that regular attendance is open to anyone and we will welcome anyone to
join the conference audience.

> This call for papers is for the 50% submission portion of the 
> conference for paper submissions, tutorials and workshops.
> We *highly discourage* submission of recycled talks.
> 
> Current technical focus topics include:
> - wireless
> - performance analysis, debugging and improvement
> - networking hardware and offload
> - netfilter
> - traffic control
> - different networking layers (L2/3, etc)
> - Internet of things
> - security
> - additional topics can be suggested
> 
> Unlike other conferences, we are going to try and accommodate as many
> submissions as possible - but please stay within the relevant topic focus 
> and tie to Linux networking to make it easier for the technical committee
> to provide quick feedback. In order to give a talk you must be 
> registered. If your proposal is accepted you will not be charged 
> a conference fee or your conference fee will be refunded to you 
> when your talk gets accepted.
> 
> We expect minimum of 2 parallel tracks but likely more depending on the
> (quantity of submissions) in all phases i.e during tutorials,
> workshops and main talks. 
> 
> Why you should submit a proposal
> ---------------------------------
> If you yearn for the old community tech driven conferences where 
> you mingle with fellow geeks (only these would be Linux networking
> geeks) then this would be it. There will be no marketing flashy 
> openings. There will just be a pure feed of Linux networking.
> Netdev 0.1 will be held back to back with Netconf 2015, the 
> by-invite Linux kernel networking workshop 
> (http://vger.kernel.org/netconf2015.html). 
> So gurus of all sorts will be there mingling and giving talks.
> While there will be heavy Linux kernel influence we expect a lot
> of user space presence as well. 
> 
> How to submit a proposal
> ------------------------
> Send email to  netdev01@lists.netfilter.org with a paragraph or
> two of your proposal.
> For paper proposals, if your submission is accepted we will provide
> you a template to use.
> A minimum of two pages is needed so as to to allow people to skip the 
> burden of writing a large paper. The maximum page limit is 10 pages.
> 
> Location:
> ---------
> Downtown Ottawa, Canada
> www.netdev01.org
> 
> Important Dates:
> ----------------
> December 02, 2014	 	Call for Papers opens
> December 10, 2014	 	Registration opens
> January 10, 2015	 	Call for sessions deadline
> January 20, 2015	 	Conference schedule announced
> February 14-17, 2015            Conference days
> 
> Please register as soon as registration opens up on December 10.
> Registering helps us plan properly for numbers of attendees,
> ensuring venue sizes and supplies are appropriate without
> wasting resources.
> 
> 
> 
> 	slainte mhath, RGB

	slainte mhath, RGB

--
Richard Guy Briggs               --  ~\    -- ~\             <hpv.tricolour.ca>
<www.TriColour.ca>                 --  \___   o \@      @        Ride yer bike!
Ottawa, ON, CANADA                  --  Lo_>__M__\\/\%__\\/\%
Vote! -- <greenparty.ca>_____GTVS6#790__(*)__(*)________(*)(*)_________________

WARNING: multiple messages have this Message-ID (diff)
From: Richard Guy Briggs <rgb@tricolour.ca>
To: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	lwn@lwn.net, netdev01@lists.netfilter.org, lartc@vger.kernel.org,
	netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: NetDev 0.1 Attendee clarification [was: Netdev 0.1 Call for Proposals]
Date: Fri, 12 Dec 2014 15:09:42 +0000	[thread overview]
Message-ID: <20141212150942.GV392@toccata2.tricolour.ca> (raw)
In-Reply-To: <20141203022815.GM4612@toccata2.tricolour.ca>

On 14/12/02, Richard Guy Briggs wrote:
> Netdev 0.1 Call for Proposals
> -----------------------------
> 
> Netdev 0.1 (year 0, conference 1) is a community-driven conference
> geared towards Linux netheads. Linux kernel networking and user 
> space utilization of the interfaces to the Linux kernel networking
> subsystem are the focus.

Hello fellow Linux NetHeads, sorry for the noise:

There seems to have been some questions about the intended audience for this
conference.

The 50/50 by-invitation/submission slots are for the *presenters* of the talks
and not for the audience of attendees.  *Anyone* with an interest in Linux
networking is welcome to attend this conference.

We're very sorry for the confusion and welcome you to join us.

Cheers.

> There are 4 phases/formats to Netdev 0.1
> 
> 1) Workshops (day 1)
> 
> The workshop format is inspired by Netconf and the wireless
> mini-summits, with workshops being centered around existing
> networking subsystems. workshops are intended to be an extension of
> the mailing list in the sense that many times previous
> discussions from the mailing list (or that could otherwise have
> happened there) are taken to the round-table to simplify the
> decision-making process.
> 
> The networking subsystem maintainer(s) should at least prepare a
> list of agenda items well before the workshop takes place to allow 
> participants to come prepared; this makes the discussions most productive.
> Sometimes brain-storming sessions will also be appropriate where
> being prepared is less important, for example for discussions
> around new user requirements this can be very valuable.
> 
> At the workshop meeting itself discussions prevail and notes are
> later sent back to the mailing list; presentations are typically
> - at the discretion of the chairs - only used where needed to
> clarify a problem statement for discussion.
> 
> The sitting format is round-table.
> 
> 2) BOFs (day 1)
> 
> BOFs are sessions with a potential to become a workshop in a future
> Netdev conference. The lifetime of a BOF may be only one or two 
> Netdev conference gatherings. We discourage perpetual BOFs.
> BoFs don't need to have an existing networking subsystem or mailing list.
> BOFs also don't need to strive to be upgraded to be a Workshop
> in the future. Their longevity could only be one conference.
> The sitting format could vary and be either lecture or round table format
> depending on the proposal.
> 
> 3) Tutorials (day 2)
> 
> Tutorials are generally about 2 hours long (or more at the discretion
> of the proposal).
> Tutorials are educational in nature and are presented in a classroom 
> format with a specific educational outcome for the attendees.
> 
> 4) Paper proposals (days 3 and 4)
> 
> These are classical conference paper + presentations.
> Presentations are 30 minutes long with an additional 15 minutes for Q&A
> presented in a lecture format.
> We will require paper submissions for these sessions. The committee 
> believes that a paper submission raises the quality of the presentations
> and makes it easier to build on presented ideas in the future.
> 
> The Netdev conference this year is structured to be 50% by-invitation 
> and 50% submission. We are making sure that we reach out to speakers 
> who have interesting relevant topics because we recognize most of 
> these folks would typically not be submitting papers to a conference.
> The invitation will be made by the technical committee to the individual
> speakers for workshop, paper and tutorial sessions.

Clarification is that the presenters will be split 50/50 invitation/submission
and that regular attendance is open to anyone and we will welcome anyone to
join the conference audience.

> This call for papers is for the 50% submission portion of the 
> conference for paper submissions, tutorials and workshops.
> We *highly discourage* submission of recycled talks.
> 
> Current technical focus topics include:
> - wireless
> - performance analysis, debugging and improvement
> - networking hardware and offload
> - netfilter
> - traffic control
> - different networking layers (L2/3, etc)
> - Internet of things
> - security
> - additional topics can be suggested
> 
> Unlike other conferences, we are going to try and accommodate as many
> submissions as possible - but please stay within the relevant topic focus 
> and tie to Linux networking to make it easier for the technical committee
> to provide quick feedback. In order to give a talk you must be 
> registered. If your proposal is accepted you will not be charged 
> a conference fee or your conference fee will be refunded to you 
> when your talk gets accepted.
> 
> We expect minimum of 2 parallel tracks but likely more depending on the
> (quantity of submissions) in all phases i.e during tutorials,
> workshops and main talks. 
> 
> Why you should submit a proposal
> ---------------------------------
> If you yearn for the old community tech driven conferences where 
> you mingle with fellow geeks (only these would be Linux networking
> geeks) then this would be it. There will be no marketing flashy 
> openings. There will just be a pure feed of Linux networking.
> Netdev 0.1 will be held back to back with Netconf 2015, the 
> by-invite Linux kernel networking workshop 
> (http://vger.kernel.org/netconf2015.html). 
> So gurus of all sorts will be there mingling and giving talks.
> While there will be heavy Linux kernel influence we expect a lot
> of user space presence as well. 
> 
> How to submit a proposal
> ------------------------
> Send email to  netdev01@lists.netfilter.org with a paragraph or
> two of your proposal.
> For paper proposals, if your submission is accepted we will provide
> you a template to use.
> A minimum of two pages is needed so as to to allow people to skip the 
> burden of writing a large paper. The maximum page limit is 10 pages.
> 
> Location:
> ---------
> Downtown Ottawa, Canada
> www.netdev01.org
> 
> Important Dates:
> ----------------
> December 02, 2014	 	Call for Papers opens
> December 10, 2014	 	Registration opens
> January 10, 2015	 	Call for sessions deadline
> January 20, 2015	 	Conference schedule announced
> February 14-17, 2015            Conference days
> 
> Please register as soon as registration opens up on December 10.
> Registering helps us plan properly for numbers of attendees,
> ensuring venue sizes and supplies are appropriate without
> wasting resources.
> 
> 
> 
> 	slainte mhath, RGB

	slainte mhath, RGB

--
Richard Guy Briggs               --  ~\    -- ~\             <hpv.tricolour.ca>
<www.TriColour.ca>                 --  \___   o \@      @        Ride yer bike!
Ottawa, ON, CANADA                  --  Lo_>__M__\\/\%__\\/\%
Vote! -- <greenparty.ca>_____GTVS6#790__(*)__(*)________(*)(*)_________________

  parent reply	other threads:[~2014-12-12 15:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03  2:28 Netdev 0.1 Call for Proposals Richard Guy Briggs
2014-12-03  2:28 ` Richard Guy Briggs
2014-12-03  8:24 ` wireless workshop - was: " Johannes Berg
2014-12-11 19:12   ` Johannes Berg
2014-12-12 15:09 ` Richard Guy Briggs [this message]
2014-12-12 15:09   ` NetDev 0.1 Attendee clarification [was: Netdev 0.1 Call for Proposals] Richard Guy Briggs

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=20141212150942.GV392@toccata2.tricolour.ca \
    --to=rgb@tricolour.ca \
    --cc=lartc@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=netdev01@lists.netfilter.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.