Ticket #165 (closed bug: wontfix)

Opened 6 years ago

Last modified 4 years ago

Disable perl6-internals@perl.org mailing list.

Reported by: pmichaud Owned by:
Priority: normal Milestone:
Component: website Version:
Severity: medium Keywords: web
Cc: Language:
Patch status: Platform:

Description

We continue to get messages addressed to the <perl6-internals@…> mailing list, even though it has long been obsolete. I propose that we change the address to provide an auto-response message like the following:

The <perl6-internals@perl.org> mailing list is no longer active.
Please re-send your message to one of the following destinations
(and possibly update your address book accordingly):

- If your message is a bug report or patch for Parrot, enter a new
  ticket at http://trac.parrot.org/ (registration required).

- If your message is a bug report or patch for Rakudo Perl,
  send the message to <rakudobug@perl.org>.  You might also
  want to check http://rt.perl.org/ to see if the bug has already
  been reported.

- If your message is about the Parrot virtual machine, send it
  to <parrot-dev@lists.parrot.org>.

- If your message is about Rakudo Perl or any other Perl 6
  implementation, send it to <perl6-compiler@perl.org>.

- If you have a question about how something should work in Perl 6,
  send the message to <perl6-users@perl.org>.

- If your message is a Perl 6 language design comment or issue,
  send it to <perl6-language@perl.org>.

- If none of the above seem to apply to you, then
  <perl6-compiler@perl.org> is often a reasonably safe
  default for Perl 6 related items, and <parrot-dev@parrot.org>
  is a safe default for Parrot related items.

Thank you,

The Management

We might also wish to do a similar thing for the <parrot-porters@…> and <parrotbug@…> addresses.

Pm

Change History

  Changed 6 years ago by pmichaud

  • type changed from todo to bug

  Changed 6 years ago by coke

  • component changed from none to website

  Changed 6 years ago by coke

  • owner set to coke

Sending this ticket to the post masters at perl.org.

follow-up: ↓ 5   Changed 6 years ago by coke

Note from Robrt:

perl6-internals is still around.  parrot-porters is just an alias to
it.  Internally, the list still considers itself to be
perl6-internals.

in reply to: ↑ 4   Changed 6 years ago by pmichaud

Replying to coke:

Note from Robrt: {{{ perl6-internals is still around. parrot-porters is just an alias to it. Internally, the list still considers itself to be perl6-internals. }}}

Robert's message seems to be beside the original point of the ticket, which is that AFAIK neither the perl6-internals nor parrot-porters are "correct" addresses for any of the lists.

It's okay with me if parrot-porters automatically forwards to parrot-dev@…. But because of the "perl6" in its name, perl6-internals@… really should respond with an autoreply like I outlined above. Otherwise we end up with "orphan" messages like the one at  http://groups.google.com/group/perl.perl6.internals/browse_thread/thread/5e9f3fadd849193c# .

Phrased differently: there are still messages ending up on the perl6-internals mailing list (that aren't going to one of the other lists). There really shouldn't be.

Pm

  Changed 5 years ago by coke

  • keywords web added

  Changed 5 years ago by coke

  • owner coke deleted

follow-up: ↓ 9   Changed 4 years ago by pmichaud

I propose to close this ticket as either 'fixed' or 'wontfix'.

(If no comments occur in the next 72 hours I'll consider the above proposal accepted; if someone wants to close this ticket before then that's perfectly fine with me.)

Pm

in reply to: ↑ 8   Changed 4 years ago by jkeenan

Replying to pmichaud:

I propose to close this ticket as either 'fixed' or 'wontfix'. (If no comments occur in the next 72 hours I'll consider the above proposal accepted; if someone wants to close this ticket before then that's perfectly fine with me.) Pm

Am trying to contact perl.org for a final update on this.

kid51

  Changed 4 years ago by pmichaud

  • status changed from new to closed
  • resolution set to wontfix

Based on communications with perl.org, we've decided to do nothing. Closing ticket as "wontfix".

Thanks,

Pm

Note: See TracTickets for help on using tickets.