Mailing Lists

Y Announcement List (y-announce)

A low-volume, read-only list for announcements of new releases, etc.

~~y-announce list info page (subscribe/unsubscribe/preferences)~~

Y Developers List (y-devel)

For general discussions about the development of Y.

~~y-devel list info page (subscribe/unsubscribe/preferences)~~

There is no y-users list yet, as it is not suitable for general use, yet.

Due to abuse by spam crawlers, I've disabled subscription to the list. I'm not sure what they aim to achieve by chewing through 1000 subscription attempts per day, but all it does is annoy me.

Mailing List Etiquette

Don't top post. Top-posting makes involved discussions difficult to follow; you may just be ignored if the amount of effort required to understand your idea exceeds the level of interest in it.
By the same token, write emails in proper English and remove unnecessary quotes from previous emails which aren't relevant.
Signatures should be prefixed with a line containing the string "-- " (two dashes and a space) so that they can be automatically stripped when replying to messages.
Individual patches that you wish merged into Mark's main tree should be sent in an email with a subject of the form
```
        [PATCH] Short one-line description of patch
```
otherwise it is unlikely to get noticed and applied.
Patches sent to the list should make just one change; send several seperate patches to make several changes instead of mailing a single uber-patch which alters code all over the place. Mega-patches will not be accepted.
For best results, try to ask intelligent questions. The guidelines laid out by Eric Raymond give good suggestions on how to achieve this.