qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Hannes Reinecke <hare@suse.de>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PULL for-2.4 0/7] update ipxe roms, fix efi support
Date: Thu, 23 Jul 2015 09:26:46 +0100	[thread overview]
Message-ID: <CAJSP0QWSj8qADmVB97_CLJoLiHD5gmqkayPucMn+D-GyENr3rA@mail.gmail.com> (raw)
In-Reply-To: <55AFF852.1040605@redhat.com>

On Wed, Jul 22, 2015 at 9:08 PM, Laszlo Ersek <lersek@redhat.com> wrote:
> On 07/22/15 13:42, Stefan Hajnoczi wrote:
>> On Wed, Jul 22, 2015 at 11:05 AM, Laszlo Ersek <lersek@redhat.com> wrote:
>>> On 07/22/15 11:05, Stefan Hajnoczi wrote:
>>>> On Wed, Jul 22, 2015 at 12:58:59AM +0200, Laszlo Ersek wrote:
>>>>> On 07/21/15 18:10, Stefan Hajnoczi wrote:
>>>>>> On Tue, Jul 21, 2015 at 3:28 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>>>>>> On 21/07/2015 16:25, Peter Maydell wrote:
>>>>>> or work
>>>>>> with others to add upstream maintainers.
>>>>>
>>>>> When we can't get the maintainer's attention for our patches, and when
>>>>> the maintainer tends to rewrite even those patches he more or less
>>>>> likes, how do you propose we convince him to give *push access* to
>>>>> random people?
>>>>>
>>>>>> I see that Hannes Reinecke
>>>>>> also has patches on ipxe-devel that look ignored, so Gred and Laszlo
>>>>>> are not the only ones struggling to get patches upstream into ipxe.
>>>>>
>>>>> I've said it several times (on other lists too), and I'll say it again:
>>>>> ipxe is not an "open process" community project at this point. The last
>>>>> half year, as Paolo indicated, and as I proved above, has been ample
>>>>> experience.
>>>>
>>>> I understand the frustration with upstream.  Thanks for posting a
>>>> summary of stranded patch series, it helped explain that.
>>>>
>>>> The reason I'm suggesting reaching out to Michael Brown is that the
>>>> downstream repo will only be an "open process" for us virtualization
>>>> developers.  It won't have a user community, support, or help improve
>>>> the situation for non-virtualization developers - all things which
>>>> matter for a healthy long-term open source project.
>>>
>>> All the things upstream ipxe has been lacking for at least half a year
>>> now, without much indication that it could improve.
>>>
>>>> It may be simplest if Gerd maintains a QEMU downstream repository.  I'm
>>>> not against that.  But let's notify Michael Brown so he has a chance to
>>>> consider the problem.
>>>
>>> If you can reach out to Michael Brown, that would be highly appreciated.
>>> Personally I lost all hope.
>>
>> Done.
>
> Thanks. Looks like you got through. Obviously, that cannot be ascribed
> to anything else than blind luck, or a personal relationship from the
> past. Ie. things that should not matter in open source.

Maybe a bit of both.

I sent a link to the email thread via IRC.

Stefan

  reply	other threads:[~2015-07-23  8:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17 14:37 [Qemu-devel] [PULL for-2.4 0/7] update ipxe roms, fix efi support Gerd Hoffmann
2015-07-17 14:37 ` [Qemu-devel] [PULL 1/7] ipxe: update from 35c53797 to 24112d9 (upstream/master) Gerd Hoffmann
2015-07-17 14:37 ` [Qemu-devel] [PULL 2/7] ipxe: update to 87981bb (qemu) Gerd Hoffmann
2015-07-17 14:37 ` [Qemu-devel] [PULL 3/7] ipxe: rm local config in cleanup Gerd Hoffmann
2015-07-17 14:37 ` [Qemu-devel] [PULL 4/7] ipxe: disable load file protocol Gerd Hoffmann
2015-07-17 14:37 ` [Qemu-devel] [PULL 5/7] ipxe: add qemu branding Gerd Hoffmann
2015-07-17 14:37 ` [Qemu-devel] [PULL 6/7] ipxe: don't override GITVERSION Gerd Hoffmann
2015-07-17 14:37 ` [Qemu-devel] [PULL 7/7] ipxe: update binaries Gerd Hoffmann
2015-07-20 10:04 ` [Qemu-devel] [PULL for-2.4 0/7] update ipxe roms, fix efi support Peter Maydell
2015-07-21  8:21   ` Peter Maydell
2015-07-21  8:51     ` Paolo Bonzini
2015-07-21 13:27       ` Peter Maydell
2015-07-21 13:47         ` Paolo Bonzini
2015-07-21 13:57           ` Peter Maydell
2015-07-21 14:09             ` Paolo Bonzini
2015-07-21 14:25               ` Peter Maydell
2015-07-21 14:28                 ` Paolo Bonzini
2015-07-21 16:10                   ` Stefan Hajnoczi
2015-07-21 16:18                     ` Peter Maydell
2015-07-21 23:00                       ` Laszlo Ersek
2015-07-21 22:58                     ` Laszlo Ersek
2015-07-21 23:22                       ` Laszlo Ersek
2015-07-22  9:05                       ` Stefan Hajnoczi
2015-07-22 10:05                         ` Laszlo Ersek
2015-07-22 11:42                           ` Stefan Hajnoczi
2015-07-22 20:08                             ` Laszlo Ersek
2015-07-23  8:26                               ` Stefan Hajnoczi [this message]
2015-07-22 20:06                       ` Michael Brown
2015-07-22 20:10                         ` Laszlo Ersek

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=CAJSP0QWSj8qADmVB97_CLJoLiHD5gmqkayPucMn+D-GyENr3rA@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=hare@suse.de \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).