Marcus Stollsteimer

I think it‘s more important to concentrate on current news, 2019 and 2018, see www.ruby-lang.org/admin/translation-status. So let‘s close this issue...?

I'm not convinced yet that automatic disabling is a good thing. Besides that, I think "_plugins/translation_status.rb" is not the right place to define the "languages_json" tag, it should be separate.

Personally, I do not like handling cookies, I'd prefer keeping the site as simple as possible.

@tkhr `ja` is kind of decoupled from the rest, I assume most of the content is or has been maintained by core team members directly. It probably needs a separate...

I'm not too convinced. On my machine, already now the header takes up half of the screen, on the home page with code example almost all of it.

I updated the *-request addresses etc. However, I think there still should be some restructuring of these pages (mailing-lists and mailing-lists/manual-instructions), to better reflect the 3 possibilities: "our" simple form,...

The Ruby license (for code) is linked to on the downloads page (though only the latest version which might not apply to older branches).

Note: this currently only affects the mobile view.

I do not see yet how this is supposed to work in practice. Using the commit hash would not be possible nor would it help.

That probably could work (but relies heavily on the thoroughness of the translators). _I misunderstood the proposed system, because the given example also added a `commit` field in the `en`...