public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yunseong Kim <ysk@kzalloc.com>
To: Rik van Riel <riel@surriel.com>
Cc: Matt Mackall <mpm@selenic.com>,
	kernelnewbies@kernelnewbies.org, linux-kernel@vger.kernel.org,
	Yunseong Kim <yunseong.kim@ericsson.com>,
	Yunseong Kim <yunseong.kim@est.tech>
Subject: [REPORT] kernelnewbies.org is down (502 Bad Gateway)
Date: Fri, 1 May 2026 20:34:39 +0200	[thread overview]
Message-ID: <fc60e7db-fa60-44c9-8e48-08d4d3b1c915@kzalloc.com> (raw)

Hi Rik,

I'm reporting that the KernelNewbies main page is currently unreachable,
returning a 502 Bad Gateway error:

  https://kernelnewbies.org/

The latest archived version (from April 20th) can be found here:

  https://web.archive.org/web/20260000000000*/https://kernelnewbies.org/LinuxChanges

I think it's not an unrelated topic, but the Linux perf wiki had the same
problem a few years ago, so I migrated it to GitHub using the mkdocs
framework. Most wiki formats are quite compatible with Markdown, and it
has served as a stable alternative for the community. This is migrated version
for the perf wiki:

  https://perf.wiki.kernel.org/

The discussion regarding the perf wiki migration can be found here:

  https://lore.kernel.org/linux-perf-users/7f2b1c74-4087-4da4-94eb-51d37f3d8fc2@gmail.com/

Moving to a platform like GitHub (or any other) helps address the issue where
users cannot contribute freely immediately after registration. Currently,
I can invite anyone who wishes to contribute via email, and I also accept pull
requests.

For the perf wiki, we fortunately had a backup repository thanks to
Konstantin:

  https://github.com/mricon/perfwiki

Is there a similar backup repository or a recent data dump available for
kernelnewbies? I think moving to a Git-based workflow with a framework like
mkdocs might be a good way to ensure long-term availability and prevent
future downtime.

Thank you for building such an invaluable resource, it has been a massive
help to the next generation of kernel contributors like me.

Please let me know if there is anything I can do to help. I would be more
than happy to assist in any way I can.

Best regards,
Yunseong

             reply	other threads:[~2026-05-01 18:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 18:34 Yunseong Kim [this message]
2026-05-02  8:26 ` [REPORT] kernelnewbies.org is down (502 Bad Gateway) Luna Jernberg
2026-05-02 11:50   ` Yunseong Kim

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=fc60e7db-fa60-44c9-8e48-08d4d3b1c915@kzalloc.com \
    --to=ysk@kzalloc.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=riel@surriel.com \
    --cc=yunseong.kim@ericsson.com \
    --cc=yunseong.kim@est.tech \
    /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