From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Stefan Weil" <sw@weilnetz.de>, "Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] No archives to download from www.qemu.org/download/
Date: Thu, 18 Jul 2019 14:20:48 +0200 [thread overview]
Message-ID: <CAL1e-=hXg6HpAjtsxC+qaHMBXKU7-PKHf0QL+3mRKOh8ojNpOA@mail.gmail.com> (raw)
In-Reply-To: <20190718114352.GE15411@redhat.com>
On Thu, Jul 18, 2019 at 1:43 PM Daniel P. Berrangé <berrange@redhat.com>
wrote:
> On Thu, Jul 18, 2019 at 01:29:02PM +0200, Thomas Huth wrote:
> > On 18/07/2019 12.55, Aleksandar Markovic wrote:
> > > On Thu, Jul 18, 2019 at 10:58 AM Philippe Mathieu-Daudé <
> philmd@redhat.com>
> > > wrote:
> > >>
> > >> On 7/18/19 9:10 AM, Thomas Huth wrote:
> > >>> On 18/07/2019 08.25, Philippe Mathieu-Daudé wrote:
> > >
> > >>>> ...
> > >
> > >>>> Now there are no archive to download at this url...
> > >>>
> > >>> You just have to click on the "Source code" tab ... is that too hard?
> > >>
> > >> Argh it has been a rough night, now I feel ashamed. I scrolled but
> > >> missed that tab. Really sorry for crying wolf here :/
> > >>
> > >
> > > Download QEMU page <https://www.qemu.org/download/>
> > >
> > > In all fairness to Philippe, this page could be better in terms of
> > > human-computer interaction... If one presses 'Download', one
> > > expects to get to the download links directly or obviously easily.
> >
> > I guess we should simply re-arrange the order of the tabs ... the
> > OS-agnostic source code tab should come first (since this is about what
> > we provide for download on our site), and then the others with
> > references to the distros etc.
>
> I'm not sure it is clear cut. I think its reasonable to say that users
> coming to QEMU are best served by using distro provided packages. Only
> those wishing to actually hack on QEMU, or who need newer than the
> distro provides, should prefer the source. Building from source has many
> more potential hurdles / failure points than installing distro packages,
> which can leave users with a worse first experience of QEMU.
>
>
Yes, Daniel, but here we blend two visitor activities onto a single page:
download source (and build), and install QEMU (from prebuilt binaries).
Now wonder a confusion arises.
Yours,
Aleksandar
> Regards,
> Daniel
> --
> |: https://berrange.com -o-
> https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org -o-
> https://fstop138.berrange.com :|
> |: https://entangle-photo.org -o-
> https://www.instagram.com/dberrange :|
>
next prev parent reply other threads:[~2019-07-18 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 6:25 [Qemu-devel] No archives to download from www.qemu.org/download/ Philippe Mathieu-Daudé
2019-07-18 7:10 ` Thomas Huth
2019-07-18 8:58 ` Philippe Mathieu-Daudé
[not found] ` <CAL1e-=iLLQfAdfFrKpAT9k48X0sEMevBXFWAmny7PRPwtBMiEQ@mail.gmail.com>
2019-07-18 11:29 ` Thomas Huth
2019-07-18 11:43 ` Daniel P. Berrangé
2019-07-18 11:53 ` Thomas Huth
2019-07-18 12:20 ` Aleksandar Markovic [this message]
2019-07-18 11:49 ` Stefan Weil
2019-07-18 13:14 ` Peter Maydell
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='CAL1e-=hXg6HpAjtsxC+qaHMBXKU7-PKHf0QL+3mRKOh8ojNpOA@mail.gmail.com' \
--to=aleksandar.m.mail@gmail.com \
--cc=berrange@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
--cc=thuth@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).