qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eldon Stegall <eldon-qemu@eldondev.com>
To: Simon Sharwood <simon@jargonmaster.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Sad to see the advent calendar go
Date: Mon, 5 Dec 2022 19:07:13 +0000	[thread overview]
Message-ID: <Y45BEF1B1Pbx9yZ2@invalid> (raw)
In-Reply-To: <CAHW_L2i3WBULFk+Gh2cxqwB-mrvB1iE3NOgFdozaN9hDVuFK1Q@mail.gmail.com>

Hi Simon,

Thanks for your interest in the calendar! I am not a regular QEMU
contributor, but I am a longtime user, and ran the calendar in 2020. I
also put out a submission request for the calendar this past year, but
there wasn't much response. The cost to host the calendar is trivial, we
just need to convert some of the sysadmin responsibilities, and that is
in progress.

As far as future calendars go, the effort to construct a new calendar
with novel, thematic content is substantial. Some of the difficulty lies
in the technical element, but a lot of it lies in the synthesis and
ideation.

In 2020 I had a number of community submissions, and good pointers,
but I also put in substantial effort, which I was capable of as a result
of a holiday sabbatical. This year was a little different.

I'm not sure if others in the community have the same perspective, but
that is my perspective, and I would be committed to the 2023 calendar if
folks were interested. I assembled some resources for the 2022 calendar,
but I think with a little more upfront planning, and some directed
request, I can coordinate a much better outcome for 2023.

Thanks,
Eldon


  reply	other threads:[~2022-12-05 19:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05  4:41 Sad to see the advent calendar go Simon Sharwood
2022-12-05 19:07 ` Eldon Stegall [this message]
2022-12-06  8:08   ` Thomas Huth

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=Y45BEF1B1Pbx9yZ2@invalid \
    --to=eldon-qemu@eldondev.com \
    --cc=qemu-devel@nongnu.org \
    --cc=simon@jargonmaster.com \
    /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).