The development mailing list archives are outdated (current date: 13th dec, last archive entry: 9th dec). Other mailing list archive links (from the drupal.org mailing list page) simply give 404. These lists include the themes list, the translations and consulting lists.

Comments

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Active » Fixed

has been fixed.

oadaeh’s picture

oadaeh commented
Status: Fixed » Active

There are three mail lists [0] that don't seem to have any archives, though I know e-mail has gone through at least two of them:
- Translations: http://lists.drupal.org/archives/translations/
- Consulting: http://lists.drupal.org/archives/consulting/
- DrupalCON: http://lists.drupal.org/archives/drupal-con/

(I'm not entirely sure about that last one, as I have not been subscribed to it.)

The links are returning a "Not Found" message. And, looking at the main archive page [1] shows that those three lists are not there.

[0] http://drupal.org/mailing-lists
[1] http://lists.drupal.org/archives/

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Oadae has some valid points. Why are these archives missing?

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Closed (fixed)

They are available, just at slightly different urls:

http://lists.drupal.org/pipermail/translations/
http://lists.drupal.org/pipermail/consulting/
http://lists.drupal.org/private/drupal-con/

If anything this should be a bug for "create alialiases for archives to "private" and/or "pipermail" for certain subdirectories or somesuch similar issue. Personally, I think it should just be closed (and am doing so).

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Closed (fixed) » Active

The http://drupal.org/mailing-lists page has archive links. Those are not working. This is an active bug. Needs fixing.

dries’s picture

dries commented

Please send an e-mail to support@osuosl.org describing the problem. Thanks.

chx’s picture

chx commented

Dries, we can't really expect the OSU OSL to fix up our lists.module which prints the wrong links...

dries’s picture

dries commented

Arr, I got confused as well. Sorry. :)

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Chx, Dries: The problem is not in lists module. The problem is that the lists archive URLs are not following a pattern. These work:

http://lists.drupal.org/archives/support/
http://lists.drupal.org/archives/development/
http://lists.drupal.org/archives/themes/
http://lists.drupal.org/archives/documentation/
http://lists.drupal.org/pipermail/translations/
http://lists.drupal.org/pipermail/consulting/
http://lists.drupal.org/archives/drupal-cvs/
http://lists.drupal.org/private/infrastructure/ (private archive)
http://lists.drupal.org/private/drupal-con/ (private archive)

The problem in lists.module, is that it should know whether a list has public or private archives. The last two have private archives. The problem with the server setup is that all archives should be able to get accessed with the archives/* URL pattern, but as you can see, the translations and consulting list does not follow this pattern.

Please point me to the lists.module code so I can fix the mailing list handling on the Drupal side. The URL inconsistency should be pointed out at support@osuosl.org?

oadaeh’s picture

oadaeh commented
Component: mailing lists » Broken link
Status: Active » Fixed

It looks like this was fixed by changing it so that all the public URLs use the pipermail address, rather than the archives address:

http://lists.drupal.org/pipermail/support/
http://lists.drupal.org/pipermail/development/
http://lists.drupal.org/pipermail/themes/
http://lists.drupal.org/pipermail/documentation/
http://lists.drupal.org/pipermail/translations/
http://lists.drupal.org/pipermail/consulting/
http://lists.drupal.org/pipermail/drupal-cvs/

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.