user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] doc/hosted: drop some links and clarify wording
Date: Thu, 30 May 2019 07:11:37 +0000	[thread overview]
Message-ID: <20190530071137.12801-1-e@80x24.org> (raw)

I don't have time to check and train spam for all these
projects.

Spam filtering is especially difficult on ruby-core: it
enters via Redmine, so it doesn't have a distinct Received:
chain, and also gets mixed with non-spam bug-report text,
throwing off Bayes training.

And I'm not sure if those mirrors did anybody any good, even;
so lets not say its' a "service" to anybody :P

The actual mirrors remain up, for now, but who knows...
I care about decentralization too much to ask anybody
to trust me to keep anything up :P
---
 Documentation/hosted.txt | 19 ++-----------------
 1 file changed, 2 insertions(+), 17 deletions(-)

diff --git a/Documentation/hosted.txt b/Documentation/hosted.txt
index 0b1fb92..188ad25 100644
--- a/Documentation/hosted.txt
+++ b/Documentation/hosted.txt
@@ -2,10 +2,10 @@ unofficially hosted mirrors at public-inbox.org
 
 In addition to eating our own dogfood at <https://public-inbox.org/meta/>,
 public-inbox.org hosts unofficial archives for several other projects
-as a service to their users and to further test our own software.
+to further test our own software.
 
 These mirrors are NOT to be considered reliable or permanent.
-Interested parties are strongly encouraged to host mirrors.
+Interested parties are strongly encouraged to host their own mirrors.
 
 The presence of these archives does not imply these projects endorse
 public-inbox or public-inbox.org in any way.
@@ -25,26 +25,11 @@ public-inbox or public-inbox.org in any way.
   Mailing list for GNU C library development
   https://www.gnu.org/software/libc/involved.html
 
-* https://public-inbox.org/libreplanet-discuss/
-  libreplanet-discuss@libreplanet.org
-  LibrePlanet discussion list
-  https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
-
 * https://public-inbox.org/rack-devel/
   rack-devel@googlegroups.com
   Development list for the Ruby webserver interface
   https://groups.google.com/group/rack-devel
 
-* https://public-inbox.org/ruby-core/
-  ruby-core@ruby-lang.org
-  Core development list for the Ruby programming language
-  https://www.ruby-lang.org/en/community/mailing-lists/
-
-* https://public-inbox.org/ruby-dev/
-  ruby-dev@ruby-lang.org
-  Japanese development list for the Ruby programming language
-  https://www.ruby-lang.org/en/community/mailing-lists/
-
 * https://public-inbox.org/sox-users/
   sox-users@lists.sourceforge.net
   Users' list for the SoX sound processing tool
-- 
EW


                 reply	other threads:[~2019-05-30  7:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190530071137.12801-1-e@80x24.org \
    --to=e@80x24.org \
    --cc=meta@public-inbox.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/public-inbox.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).