qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kashyap Chamarthy <kchamart@redhat.com>
To: qemu-devel@nongnu.org, libvir-list@redhat.com, kvm@vger.kernel.org
Subject: Call for Volunteers: Summaries of a few KVMForum-2020 talks for an LWN article
Date: Thu, 29 Oct 2020 15:27:07 +0100	[thread overview]
Message-ID: <20201029142707.eyjimaffcwkbrwcw@paraplu> (raw)

Hi, folks

Like last year[1], we're aiming to submit a KVM Forum 2020 "recap"
article for LWN.

This won't be a comprehensive summary of a lot of talks — LWN normally
aims for 1500 words; they say "fewer can sometimes work, and more is
generally OK too".  Given that, the write-up can cover about four
topics, similar to previous year's recap.

So I'm looking for a couple of volunteers.  Meanwhile, I'll write LWN
folks an email to see if they're amenable to this.  If they can't accept
it for some reason, Plan-B is qemu.org blog articles.

- KVM Forum 2020 schedule: https://kvmforum2020.sched.com/  
- And LWN.net's author guidelines: https://lwn.net/op/AuthorGuide.lwn

I volunteer to summarize Janosch Frank's "The Common Challenges of
Secure VMs" talk.

Let me know, on-list or off-list, on what topic you'd like to pick.

PS: Just like it was noted in the last year's call for volunteers, we
    will not ask LWN.net for money.

[1] https://lwn.net/Articles/805097/ -- A recap of KVM Forum 2019
[2] https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg03536.html

-- 
/kashyap



             reply	other threads:[~2020-10-29 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 14:27 Kashyap Chamarthy [this message]
2020-11-03  9:59 ` Call for Volunteers: Summaries of a few KVMForum-2020 talks for an LWN article Kashyap Chamarthy

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=20201029142707.eyjimaffcwkbrwcw@paraplu \
    --to=kchamart@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=libvir-list@redhat.com \
    --cc=qemu-devel@nongnu.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).