Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

lists.ruby-lang.org forwards ruby-de archive to blade, which isn't available on blade

Open
#2,737 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale

Research direction

Start by checking the Mailman configuration behind lists.ruby-lang.org and the archive forwarding from /pipermail/ruby-de/ to blade.nagaokaut.ac.jp/ruby. Compare the ruby-de entry with lists that have working blade archives; done means the ruby-de archive URL no longer forwards to a 404 and its archived messages are available.

Written by the indexing model from the issue text.

Description

Dear all,

I as moderator of the ruby-de@ruby-lang.org mailing list received a complaint about the ruby-de archives not being available, hence I decided to open this ticket. It appears that the Mailman software running at lists.ruby-lang.org has been updated or modified recently so that archives, which used to be hosted at http://lists.ruby-lang.org/pipermail/ are in general forwarded to http://blade.nagaokaut.ac.jp/ruby . This works fine for lists which do have an archive on blade, but some -- like ruby-de -- don’t have an archive on blade.

For the ruby-de list, the archives used to be at http://lists.ruby-lang.org/pipermail/ruby-de/, which now forwards to a 404 page on blade.

Please, either reinstate the archives on http://lists.ruby-lang.org/pipermail/ or add archives for all lists listed at https://lists.ruby-lang.org/cgi-bin/mailman/listinfo (specifically ruby-de) to blade.

Thank you for considering this!

Dominant language
HTML
Stars
944
Forks
673
Avg merge
2d 6h
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruby/www.ruby-lang.org

All issues in ruby/www.ruby-lang.org

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.