DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Fwd: FOSDEM conference - call for participation
Date: Fri, 31 Oct 2014 15:53:19 -0700 (PDT)	[thread overview]
Message-ID: <1721193.Vc6a7NOh5W@xps13> (raw)

Hi,

Talks related to DPDK can be proposed for FOSDEM 2015:
	https://fosdem.org/2015/
This conference will take place in Belgium on 31 January & 1 February.

-- 
Thomas

-------- Forwarded Message --------
Subject: Network devroom call for participation
Date: Fri, 31 Oct 2014 17:33:33 -0400
From: Dave Neary <dneary@redhat.com>
To: Pavel Simerda <psimerda@redhat.com>,
network-devroom@lists.fosdem.org, fosdem@lists.fosdem.org

Hi everyone,

We are pleased to announce the Call for Participation in the FOSDEM
2015 Networking DevRoom!

Important dates:
* Nov 25: Deadline for submissions
* Dec  1: Speakers notified of acceptance
* Dec  5: Schedule published

This is the first time that networking has been included as a
stand-alone DevRoom, and this year the topics will cover two distinct
fields:
* Software Defined Networking (SDN), covering virtual switching, open
source SDN controllers, virtual routing
* Network management, covering host-level networking - NetworkManager,
ConnMan, systemd, wicked, kernel network services, network security, etc


We are now inviting proposals for talks about Free/Libre/Open-source
Software on the topics of SDN and network management. This is an
exciting and growing field, and this is a unique opportunity to show
novel ideas and developments to a very knowledgeable technical audience.

Topics accepted include, but are not limited to:

SDN:
* SDN controllers - OpenDaylight, OpenContrail, OpenStack Neutron
* Dataplane processing: DPDK, OpenDataplane, netdev, netfilter
* Virtual switches: Open vSwitch, Snabb Switch, VDE
* Open network protocols: OpenFlow, NETCONF, OpenLISP

Network management:
* Network management: NetworkManager, ConnMan, systemd-networkd,
interoperability among these projects
* Common code infrastructure: libnl, libmnl, libsystemd, ell, pyroute2
* Network services: DHCP, DNS, DNSSEC, PPP
* Connection management: Wifi, tethering, connection sharing, metric and
source based routing,

Talks should be aimed at a technical audience, but should not assume
that attendees are already familiar with your project or how it solves a
general problem. Talk proposals can be very specific solutions to a
problem, or can be higher level project overviews for lesser known projects.

Please include the following information when submitting a proposal:

    Your name
    The title of your talk (please be descriptive, as titles will be
listed with around 250 from other projects)
    Short abstract of one or two paragraphs
    Short bio (with photo)

The deadline for submissions is November 25th 2014. FOSDEM will be held
on the weekend of January 31st-February 1st 2015 and the Networking
DevRoom will take place on Saturday, January 31st 2015. Please use the
following website to submit your proposals:
https://penta.fosdem.org/submission/FOSDEM15 (you do not need to create
a new Pentabarf account if you already have one from past years).

You can also join the devroom’s mailing list, which is the official
communication channel for the DevRoom: network-devroom@lists.fosdem.org
(subscription page: https://lists.fosdem.org/listinfo/network-devroom)

– The Networking DevRoom 2015 Organization Team

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338

             reply	other threads:[~2014-10-31 22:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 22:53 Thomas Monjalon [this message]
2014-11-01 21:43 ` Stephen Hemminger
2014-11-02 14:33   ` Vincent JARDIN
2014-12-17  3:15 ` Stephen Hemminger
2014-12-17  6:31   ` Vincent JARDIN

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=1721193.Vc6a7NOh5W@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.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).