From: Kelly Choi <kelly.choi@cloud.com>
To: xen-devel <xen-devel@lists.xenproject.org>,
xen-users@lists.xenproject.org,
xen-announce@lists.xenproject.org
Subject: Fwd: [ANNOUNCE] Xen Project Summit 2024 Design Sessions
Date: Fri, 10 May 2024 11:28:43 +0100 [thread overview]
Message-ID: <CAO-mL=wsbpmeyz7ZoD29TBPRpbxR_ZqKQPkQsO6FNduuzFQKcA@mail.gmail.com> (raw)
In-Reply-To: <CAO-mL=wM8siytp7hQezY8mm1AyL0tJc0Y-Za8wt1ebhAjbiOyQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2542 bytes --]
*Our design sessions are now open for Xen Summit! *
If you've attended Xen Summit before, you might be familiar with the
process.
For anyone who hasn't done so before, please follow the instructions below,
using the link to create an account
<https://design-sessions.xenproject.org/>.
Once you've created your account, you'll be asked to verify using the code
below. That's it, you're in!
We aim to have design sessions with a virtual element (using Jitsi/Zoom).
This is free for the community to join in and listen, and will be hosted by
an attendee in the session.
If you're going to be an *in-person attendee*, you can propose a session
and vote on sessions you would like to see discussed.
If you're going to be a *virtual attendee*, you can vote on sessions you
would like to see discussed. You can still propose a session, but please
note there will be no professional audio or visual equipment in person for
these sessions.
The final schedule will be allocated and arranged by the highest-voted
sessions.
Virtual links for the community to join Xen Summit design sessions will be
shared closer to the event.
If you have any questions, please let me know.
For in-person tickets, click here
<https://events.linuxfoundation.org/xen-project-summit/register/>.
------------------------------
We look forward to holding the Design Sessions at the upcoming Xen Project
Summit. The design sessions will be on Wednesday, 5 June, and Thursday, 6
June 2024.
We encourage everyone to submit a Design Session, the verification code is:
“*LFXEN24*”.
*SUBMIT A DESIGN SESSION* <https://design-sessions.xenproject.org/>
The process involves the following steps:
- Anyone interested can propose
<https://design-sessions.xenproject.org/discussion/new> a topic.
- All participants review the list of sessions
<https://design-sessions.xenproject.org/list/discussion>, indicating
their interest in attending each one.
- The session scheduler optimizes the schedule
<https://design-sessions.xenproject.org/schedule> to accommodate as many
preferences as possible.
Participants can also propose long-form talks by adding [TALK] to the
session title.
For suggested topics, sample Design Session submissions, and more tips
check out the Xen Design Session page
<https://events.linuxfoundation.org/xen-project-summit/program/design-sessions/>
for more information.
Best Regards,
Xen Project Events Team
------------------------------
[-- Attachment #2: Type: text/html, Size: 13963 bytes --]
prev parent reply other threads:[~2024-05-10 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <p2-q466qgwwlqfn4m-qx47948p-a01-2x6n-0011N000017qoUMQAY@cvent-planner.com>
[not found] ` <LV8PR84MB3654E4FE6C656979B4A47A78A6172@LV8PR84MB3654.NAMPRD84.PROD.OUTLOOK.COM>
2024-04-26 11:03 ` [ANNOUNCE] Xen Project Summit 2024 Design Sessions Kelly Choi
2024-05-10 10:28 ` Kelly Choi [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='CAO-mL=wsbpmeyz7ZoD29TBPRpbxR_ZqKQPkQsO6FNduuzFQKcA@mail.gmail.com' \
--to=kelly.choi@cloud.com \
--cc=xen-announce@lists.xenproject.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xen-users@lists.xenproject.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 read-only IMAP folder(s) and NNTP newsgroup(s).