From: Claudio Fontana <claudio.fontana@huawei.com>
To: Stefan Weil <sw@weilnetz.de>,
qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] QEMU website (wiki) improvements
Date: Mon, 2 Mar 2015 14:36:48 +0100 [thread overview]
Message-ID: <54F46770.7060104@huawei.com> (raw)
In-Reply-To: <54F1DEE8.3010903@weilnetz.de>
On 28.02.2015 16:29, Stefan Weil wrote:
> Hello Michael,
>
> here are some suggestions / thoughts for the QEMU website.
>
> * http://wiki.qemu.org/Main_Pagedoes not pass the W3C validator, see
> http://validator.w3.org/check?uri=http%3A%2F%2Fwiki.qemu.org.
> They can be easily fixed, but not by normal wiki users.
>
> * It tracks users (g+ image https://ssl.gstatic.com/images/icons/gplus-32.png).
> Do we need that, or could we improve privacy?
>
> * It does not support secure access (https), so each login is insecure.
> Can we get a free server certificate?
>
> Regards
> Stefan
Another suggestion for the QEMU website: improve the testing page,
adding at least one ready-to-run image for smoke testing for each supported arch.
http://wiki.qemu.org/Testing
In particular I would like to see a minimal sparc64 image added, as well as a
minimal x86_64 image. It is useful for testing tcg backends to have little endian and big endian 64-bit images.
Ciao,
Claudio
--
Claudio Fontana
Server Virtualization Architect
Huawei Technologies Duesseldorf GmbH
Riesstraße 25 - 80992 München
office: +49 89 158834 4135
mobile: +49 15253060158
next prev parent reply other threads:[~2015-03-02 13:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 15:29 [Qemu-devel] QEMU website (wiki) improvements Stefan Weil
2015-03-02 13:36 ` Claudio Fontana [this message]
2015-03-02 14:01 ` Peter Maydell
2015-03-02 14:31 ` Claudio Fontana
2015-03-02 22:12 ` Stefan Hajnoczi
2017-01-22 15:19 ` Stefan Weil
2017-01-23 10:28 ` Stefan Hajnoczi
2017-03-28 19:37 ` Stefan Weil
2017-07-01 17:35 ` Stefan Weil
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=54F46770.7060104@huawei.com \
--to=claudio.fontana@huawei.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).