From: Junio C Hamano <gitster@pobox.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: git@vger.kernel.org
Subject: Re: The sad state of git.wiki.kernel.org
Date: Fri, 03 Feb 2023 11:43:26 -0800 [thread overview]
Message-ID: <xmqqedr6o7q9.fsf@gitster.g> (raw)
In-Reply-To: <20230203182255.lqla3hsme6riy4w7@meerkat.local> (Konstantin Ryabitsev's message of "Fri, 3 Feb 2023 13:22:55 -0500")
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> Today, most information found on the wiki is probably outdated and therefore
> potentially harmful. I would like to solicit ideas what to do with this
> resource.
>
> # Should it be migrated to RTD-style docs?
>
> We have stopped providing new Mediawiki instances at kernel.org quite some
> time back, replacing the offering with Dokuwiki. Today, we don't spin up new
> Dokuwiki instances either and everyone is steered towards readthedocs-style
> documentation instead, which is a much more sane and manageable medium than
> wikis, especially when it comes to technical docs (see
> https://korg.docs.kernel.org/docs.html).
>
> However, it's unclear if this is even needed for this wiki, considering the
> existence of https://git-scm.com/doc.
I tend to agree with this point. Presense on RTD is nice, but what
is left in git.wiki.k.o is not something I'd consider porting it
over; the contents of git-scm.com/ might be but that is off topic
here.
> # Should it be archived as a static site?
>
> It's possible to turn git.wiki.kernel.org into a static site with a large
> header on every page that it contains historical archival information, with a
> link to https://git-scm.com/doc
I do not know the size of regular traffic to the git.wiki.k.o; if
many people visit (on purpose or by mistake) there to warrant such a
redirection, then it is very much appreciated. No current contents
with just "redirect in 5 seconds---please update your bookmark" may
be fine.
> # Should it be archived and put out of its misery?
>
> The last option is to just archive the site and put it out of its increasingly
> irrelevant existence.
Archiving so that people can retrieve the contents for whatever
reason may be needed no matter what other things are done, I would
imagine.
Thanks.
next prev parent reply other threads:[~2023-02-03 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 18:22 The sad state of git.wiki.kernel.org Konstantin Ryabitsev
2023-02-03 19:43 ` Junio C Hamano [this message]
2023-02-04 11:27 ` Jeff King
2023-02-04 13:13 ` Andrei Rybak
2023-02-04 14:03 ` Christian Couder
2023-02-06 21:41 ` Konstantin Ryabitsev
2023-02-07 11:53 ` Christian Couder
2023-02-07 18:09 ` Jeff King
2023-02-09 21:31 ` Konstantin Ryabitsev
2023-02-09 21:46 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqedr6o7q9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).