From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "classpath@gnu.org" <classpath@gnu.org>,
"Andrew Hughes" <gnu.andrew@redhat.com>,
Andïï <gnu_andrew@member.fsf.org>,
Andïï <gnu.andrew.rocks@gmail.com>,
"Andrew Haley" <aph@redhat.com>,
java@gcc.gnu.org, "Mario Torre" <neugens@redhat.com>
Subject: Re: Status of GNU Classpath
Date: Wed, 13 Sep 2023 12:06:49 +0200 [thread overview]
Message-ID: <CABDcavbU7nAYQDQGU+G2OAvBUMSJ+xqEV+__VKWt1zgPaE_SEQ@mail.gmail.com> (raw)
In-Reply-To: <CABDcavZSbvUAFqh1JMSRH8rmcXhSRLLN-Ww4NcTc3QUX24-e+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]
Hi Mark,
Were you able to have a look at this?
Current status seems to be the same as in February.
Thank you,
Guillermo
El mar, 7 feb 2023 a las 14:00, Guillermo Rodriguez Garcia (<
guille.rodriguez@gmail.com>) escribió:
> Hi Mark,
>
> El mar, 7 feb 2023 a las 11:47, Mark Wielaard (<mark@klomp.org>) escribió:
> >
> > Hi Guillermo,
> >
> > On Mon, 2023-02-06 at 13:55 +0100, Guillermo Rodriguez Garcia wrote:
> > > Summary: It does not seem to be possible to join the mailing list
> > > anymore. Additionally, emails sent to the list are not being delivered
> > > to subscribers, nor included in the archives (see details in the email
> > > below).
> >
> > Urgh. Sorry. I did see your earlier email, but then Fosdem happened and
> > I forgot. So at one point classpath got so much email that
> > lists.gnu.org couldn't handle it in time. So we arranged to handle all
> > emails on developer.classpath.org. But at some point that machine had
> > to be migrated and the mailinglist archives haven't been put back.
> > There are backups and I'll contact the fsf-tech team to see if they can
> > incorporate those archives and handle the mailinglist directly again.
>
> Thank you. There are a number of issues actually. I'll summarize here
> in case you want to forward this to the relevant team:
>
> 1. Archives are not up to date, e-mails sent after March 2010 do not
> show up in the archives (although they are visible in other,
> non-official archives). See:
> * Official archive: https://lists.gnu.org/archive/html/classpath/
> * Non-official archives:
> https://www.mail-archive.com/classpath@gnu.org/maillist.html ,
> https://www.spinics.net/lists/gnu-classpath/
> 2. It is not possible to subscribe to the mailing list anymore
> ("subscribe" button has no associated action, does not submit the
> form). See:
> * https://lists.gnu.org/mailman/listinfo/classpath
> 3. (I believe) emails sent to the mailing list are not delivered to
> current subscribers
>
> A functioning mailing list is important as otherwise it is difficult
> to discuss anything in the open.
>
> Eventually I think it would be good to discuss what is the current
> status and future of GNU Classpath, and what can be done to help it
> move forward -- assuming there is enough interest.
>
> Thanks,
>
> Guillermo Rodriguez Garcia
> guille.rodriguez@gmail.com
>
--
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
next prev parent reply other threads:[~2023-09-13 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABDcavY1sfVXs=zhF3fB+LS+HbszaDzs4KUzbkryFyz13ngtwQ@mail.gmail.com>
2023-02-06 12:55 ` Guillermo Rodriguez Garcia
2023-02-06 14:25 ` Ricardo Wurmus
2023-02-06 16:16 ` Guillermo Rodriguez Garcia
2023-02-08 10:42 ` Ricardo Wurmus
2023-02-08 15:55 ` Guillermo Rodriguez Garcia
2023-02-10 19:08 ` Ricardo Wurmus
2023-02-07 10:34 ` Andrew Haley
2023-02-07 10:55 ` Mark Wielaard
2023-02-07 10:47 ` Mark Wielaard
2023-02-07 13:00 ` Guillermo Rodriguez Garcia
2023-09-13 10:06 ` Guillermo Rodriguez Garcia [this message]
2023-09-14 8:15 ` Mark Wielaard
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=CABDcavbU7nAYQDQGU+G2OAvBUMSJ+xqEV+__VKWt1zgPaE_SEQ@mail.gmail.com \
--to=guille.rodriguez@gmail.com \
--cc=aph@redhat.com \
--cc=classpath@gnu.org \
--cc=gnu.andrew.rocks@gmail.com \
--cc=gnu.andrew@redhat.com \
--cc=gnu_andrew@member.fsf.org \
--cc=java@gcc.gnu.org \
--cc=mark@klomp.org \
--cc=neugens@redhat.com \
/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).