From: "vo.x (Vit Ondruch)" <noreply@ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Subject: [ruby-core:111073] [Ruby master Misc#19030] [ANN] Migrate lists.ruby-lang.org to Google Groups
Date: Tue, 29 Nov 2022 17:29:30 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-100333.20221129172929.572@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-19030.20220929073053.572@ruby-lang.org
Issue #19030 has been updated by vo.x (Vit Ondruch).
The emails are now containing too much empty lines. It already starts with the Redmine header which looks like:
~~~
----------------------------------------
Bug #19158: Ruby 3.1.3 installs wrong gemspec for debug gem
https://bugs.ruby-lang.org/issues/19158
* Author: deivid (David Rodríguez)
* Status: Open
* Priority: Normal
* ruby -v: ruby 3.1.3p185 (2022-11-24 revision 1a6b16756e) [arm64-darwin22]
* Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
~~~
And the preformatted content is mostly unreadable due to this :/
----------------------------------------
Misc #19030: [ANN] Migrate lists.ruby-lang.org to Google Groups
https://bugs.ruby-lang.org/issues/19030#change-100333
* Author: hsbt (Hiroshi SHIBATA)
* Status: Closed
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
----------------------------------------
Our mailing-list server that is `lists.ruby-lang.org` is too old. And it's difficult to replace new server on AWS because building mail-service on AWS has a lot of limitations. I and @shugo decided to migrate lists.ruby-lang.org to Google Groups.
* In Nov-Dec 2022, we migrate the current list member to Google Groups of our google workspace.
* I hope to migrate to the last list-id, But I'm not sure we can do that.
* What will be used as an archive viewer has yet to be TBD status.
* blade is still down.
* I prefer plain text viewer like blade instead of google groups. Should we build it?
I will update this plan in this thread.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/
prev parent reply other threads:[~2022-11-29 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 7:30 [ruby-core:110145] [Ruby master Misc#19030] [ANN] Migrate lists.ruby-lang.org to Google Groups hsbt (Hiroshi SHIBATA)
2022-10-04 0:01 ` [ruby-core:110174] " hsbt (Hiroshi SHIBATA)
2022-11-09 2:23 ` [ruby-core:110665] " hsbt (Hiroshi SHIBATA)
2022-11-18 7:27 ` [ruby-core:110806] " hsbt (Hiroshi SHIBATA)
2022-11-25 3:05 ` [ruby-core:110885] " hsbt (Hiroshi SHIBATA)
2022-11-25 3:13 ` [ruby-core:111001] " hsbt (Hiroshi SHIBATA)
2022-11-25 6:40 ` [ruby-core:111003] " hsbt (Hiroshi SHIBATA)
2022-11-25 7:21 ` [ruby-core:111004] " hsbt (Hiroshi SHIBATA)
2022-11-25 8:14 ` [ruby-core:111005] " hsbt (Hiroshi SHIBATA)
2022-11-28 0:43 ` [ruby-core:111031] " hsbt (Hiroshi SHIBATA)
2022-11-29 0:02 ` [ruby-core:111041] " hsbt (Hiroshi SHIBATA)
2022-11-29 17:29 ` vo.x (Vit Ondruch) [this message]
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-100333.20221129172929.572@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=ruby-core@ml.ruby-lang.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.
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).