qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Thomas Huth" <thuth@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Cleber Rosa" <cleber@redhat.com>,
	"Jeff Cody" <codyprime@gmail.com>,
	"Stefan Hajnoczi" <stefanha@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Michael Roth" <mdroth@linux.vnet.ibm.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: Migrating custom qemu.org infrastructure to GitLab
Date: Thu, 9 Jul 2020 12:33:58 +0200	[thread overview]
Message-ID: <8e1276e2-8957-49db-0409-e85ab2f09739@redhat.com> (raw)
In-Reply-To: <3dacddaa-c739-445b-a24a-02f9e51b9b0e@redhat.com>

On 09/07/20 12:22, Thomas Huth wrote:
> FWIW, seems like we could use the "pandoc" tool to convert Mediawiki
> (our old Wiki) to Markdown (Gitlab wiki). I've done a quick test and
> converted https://wiki.qemu.org/Contribute/MailingLists into
> https://gitlab.com/huth/qemu/-/wikis/Contribute/MailingLists with some
> few clicks.
> 
> But the longer I look at most Wiki pages, the more I think that we
> should convert the important pages rather into a part of qemu-web
> instead. I'll have a closer look and will suggest some patches when time
> permits...

The wiki was cleaned up more or less at the same time as the
qemu-web.git repo was created (actually as a prerequisite), it's
actually not in a bad shape.  The idea was that the wiki kept:

- stuff that really belonged in documentation (such as completed
features and developer information)

- stuff that needs to be edited quickly (such as feature pages or or
internship ideas)

- developer-targeted information that doesn't belong in documentation
(such as CI status), even if it's linked from qemu.org (e.g.
https://www.qemu.org/contribute/

while qemu-web got the more user-targeted information.  This is because
updating qemu-web is a bit slower, requiring review and all that.

We can certainly move some wiki pages to qemu-web, like we did for
"report a bug" in the past and like Alex did recently for the
Conservancy page.  But I think there aren't that many left, most of them
are in the first category above and should be moved to docs/devel (for
example https://wiki.qemu.org/Contribute/SubmitAPatch).

Once we have docs CI on GitLab we can easily link to them from
qemu-web.git, so setting up docs CI is probably a good first step
towards relying more on GitLab and also cleaning up the wiki.

Paolo



  reply	other threads:[~2020-07-09 10:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08  9:52 Migrating custom qemu.org infrastructure to GitLab Stefan Hajnoczi
2020-07-08 10:53 ` Daniel P. Berrangé
2020-07-08 11:17   ` Paolo Bonzini
2020-07-08 11:31     ` Daniel P. Berrangé
2020-07-08 11:48   ` Thomas Huth
2020-07-08 13:19     ` Philippe Mathieu-Daudé
2020-07-08 13:32       ` Daniel P. Berrangé
2020-07-08 13:38         ` Philippe Mathieu-Daudé
2020-07-09 10:16   ` Gerd Hoffmann
2020-07-09 10:22     ` Thomas Huth
2020-07-09 10:33       ` Paolo Bonzini [this message]
2020-07-09 12:08         ` Thomas Huth
2020-07-09 13:10         ` Delete some Wiki pages (was: Migrating custom qemu.org infrastructure to GitLab) Thomas Huth
2020-07-09 13:17           ` Daniel P. Berrangé
2020-07-09 13:22           ` Paolo Bonzini
2020-10-23  5:59       ` Migrate Wiki to Gitlab? " Thomas Huth
2020-10-23  9:09         ` Daniel P. Berrangé
2020-07-08 16:09 ` Migrating custom qemu.org infrastructure to GitLab Stefan Hajnoczi
2020-07-10 14:04 ` Philippe Mathieu-Daudé
2020-07-13  8:39   ` Philippe Mathieu-Daudé
2020-07-13  8:48     ` Peter Maydell
2020-07-10 14:09 ` Philippe Mathieu-Daudé

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=8e1276e2-8957-49db-0409-e85ab2f09739@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=cleber@redhat.com \
    --cc=codyprime@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --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).