From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: qian.q.xu@intel.com, tdelanerolle@linuxfoundation.org
Subject: [dpdk-web] [PATCH] add China summit 2018
Date: Mon, 9 Apr 2018 19:11:30 +0200 [thread overview]
Message-ID: <20180409171130.10456-1-thomas@monjalon.net> (raw)
Suggested-by: Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
events.html | 37 +++++++++++++++++++------------------
1 file changed, 19 insertions(+), 18 deletions(-)
diff --git a/events.html b/events.html
index f004049..89cda8b 100644
--- a/events.html
+++ b/events.html
@@ -39,34 +39,35 @@
</nav>
</header>
<section id="events">
- <h2 id="indiasummit2018">› DPDK <em>Summit</em>, Bangalore - March 9, 2018</h2>
- <p>The first DPDK Summit of 2018 will take place in the
- <a href="https://theleela.com/en_us/hotels-in-bengaluru/the-leela-palace-hotel-bengaluru/">Leela Palace hotel</a>
- in Bangalore on Friday March 9th.</p>
- <p>The event will cover the latest developments to the DPDK framework,
- and their application to a variety of industry segments
- including telecom, cloud, enterprise and security.
- The event enables the DPDK open source community to share information
- on DPDK usage and implementation;
- to hear from DPDK developers, contributors, and users;
- and to build the DPDK community.</p>
+ <h2 id="chinasummit2018">› DPDK <em>Summit</em>, Beijing - June 28, 2018</h2>
+ <p>2018 DPDK PRC Summit will take place in the China National Convention Center,
+ Beijing on June 28th.</p>
+ <p>The agenda will cover the latest developments to the DPDK and other related projects
+ such as FD.io, Lagopus, OVS, DPVS, Tungsten Fabric and SPDK,
+ including plans for future releases,
+ and will provide an opportunity to hear from DPDK users
+ who have used it in their applications.</p>
<p style="text-align: center;">
- <a href="https://www.regonline.com/DPDKBangalore2018" class="button">
+ <a href="#" class="button">
<i class="material-icons">event_note</i>
- Register
+ Registration<br>not open yet
</a>
- <a href="https://dpdkbangalore2018.sched.com" class="button">
- <i class="material-icons">schedule</i>
- Schedule
+ <a href="https://www.surveymonkey.com/r/DZGCXTC" class="button">
+ <i class="material-icons">create</i>
+ Call for Proposal
</a>
</p>
<hr>
<ul class="logos" style="text-align: right;">
- <li>Sponsors (in addition to <a href="/about#members">member support</a>):
- <li><img src="/logos/f5.png" alt="F5">
+ <li>Sponsor (in addition to <a href="/about#members">members support</a>):
<li><img src="/logos/intel.png" alt="Intel">
</ul>
<hr>
+ <h2 id="indiasummit2018">› DPDK <em>Summit</em>, Bangalore - March 9, 2018</h2>
+ <p>
+ No archive yet |
+ <a href="https://dpdkbangalore2018.sched.com">Schedule</a>
+ </p>
<h3 id="usasummit2017">› DPDK <em>Summit</em>, San Jose - November 14-15, 2017</h3>
<p>
<a href="/events/summit-2017-usa.html">Archive</a> |
--
2.16.2
next reply other threads:[~2018-04-09 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 17:11 Thomas Monjalon [this message]
2018-04-09 17:17 ` Trishan de Lanerolle
2018-04-09 17:26 ` Thomas Monjalon
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=20180409171130.10456-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=qian.q.xu@intel.com \
--cc=tdelanerolle@linuxfoundation.org \
--cc=web@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).