From: Thomas Huth <thuth@redhat.com>
To: "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>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: Migrating custom qemu.org infrastructure to GitLab
Date: Thu, 9 Jul 2020 12:22:19 +0200 [thread overview]
Message-ID: <3dacddaa-c739-445b-a24a-02f9e51b9b0e@redhat.com> (raw)
In-Reply-To: <20200709101602.lc2uipjlxobjvjn3@sirius.home.kraxel.org>
On 09/07/2020 12.16, Gerd Hoffmann wrote:
> Hi,
>
>>> 2. wiki.qemu.org is a MediaWiki instance. Account creation is a hurdle
>>> to one-time or new contributors. It is unclear whether GitLab's wiki
>>> is expressive enough for a lossless conversion of the existing QEMU
>>> wiki. Any volunteers interested in evaluating the wiki migration would
>>> be appreciated.
>>
>> Yeah, this is a potentially big piece of work. We didn't finish this
>> in libvirt either. Looking at the libvirt mediawiki though, I decided
>> not todo a straight export/import of all content.
>
> FYI: gitlab wiki is basically just a git repo with markdown pages +
> renderer + gui editor. You can also update the wiki using git clone +
> edit + git commit + git push.
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...
Thomas
next prev parent reply other threads:[~2020-07-09 10:23 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 [this message]
2020-07-09 10:33 ` Paolo Bonzini
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=3dacddaa-c739-445b-a24a-02f9e51b9b0e@redhat.com \
--to=thuth@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=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).