qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [RFC] Bug Day - June 1st, 2010
Date: Wed, 19 May 2010 07:04:31 +0200	[thread overview]
Message-ID: <20100519050431.GA25432@ohm.aurel32.net> (raw)
In-Reply-To: <4BF316E3.6020002@linux.vnet.ibm.com>

On Tue, May 18, 2010 at 05:38:27PM -0500, Anthony Liguori wrote:
> Hi,
> 
> In an effort to improve the 0.13 release quality, I'd like to host a
> Bug Day on June 1st, 2010.  I've setup a quick wiki page with some
> more info (http://wiki.qemu.org/BugDay/June2010).
> 
> Here's my basic thinking:
> 
>  - Anyone who can should try to spend some time either triaging
> bugs, updating bug status, or actually fixing bugs.
>  - We'll have a special IRC channel (#qemu-bugday) on OFTC.  As many
> QEMU and KVM developers as possible should join this channel for
> that day to help assist people working on bugs.
>  - We'll try to migrate as many confirmable bugs from the Source
> Forge tracker to Launchpad.
> 
> If this is successful, we'll try to have regular bug days.  Any
> suggestions on how to make the experience as fun and productive as
> possible are certainly appreciated!

The idea is nice, but would it be possible to hold this on a week-end,
I personally won't be able to attend such thing on a day week.

Or maybe holding that on two days: friday and saturday so that people
can participate at least one of the two days, depending if they do that
from work or from home.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

  parent reply	other threads:[~2010-05-19  5:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 22:38 [Qemu-devel] [RFC] Bug Day - June 1st, 2010 Anthony Liguori
2010-05-19  0:58 ` Natalia Portillo
2010-05-19  1:45   ` Jamie Lokier
2010-05-19  1:48     ` Natalia Portillo
2010-05-19 13:35       ` Anthony Liguori
2010-05-19 14:10         ` Natalia Portillo
2010-05-19 13:09     ` Anthony Liguori
2010-05-19 13:19       ` Michael Tokarev
2010-05-19 13:32         ` Anthony Liguori
2010-05-19 15:57         ` Jamie Lokier
2010-05-19 22:29         ` Andre Przywara
2010-05-19 22:30           ` Anthony Liguori
2010-05-20  5:58             ` Michael Tokarev
2010-05-20  7:15               ` Andre Przywara
2010-05-20 21:32                 ` Michael Tokarev
2010-05-19 14:06       ` Natalia Portillo
2010-05-20  7:43   ` Jes Sorensen
2010-05-19  5:04 ` Aurelien Jarno [this message]
2010-05-19 12:21   ` Miguel Di Ciurcio Filho
2010-05-19 13:34   ` Anthony Liguori
2010-05-20  7:50     ` Jes Sorensen
2010-05-19 14:52 ` Luiz Capitulino
2010-05-19 17:02   ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2010-05-19 14:17 Riccardo Magliocchetti

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=20100519050431.GA25432@ohm.aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --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).