i-scream Mailing Lists
- -i-scream runs a number of mailing lists geared towards both developers and -users of i-scream products. At the present time the lists are generic to all -products, but if the volume of e-mail rises it may become necessary to create -per-project mailing lists. Here are a current lists.
- -dev@i-scream.org
- -
-Information: http://lists.i-scream.org/mailman/listinfo/dev
-State: Closed
-Purpose: A discussion forum for developers only. This can also be used to
-contact the development team as a whole.
-
commits@i-scream.org
- -
-Information: http://lists.i-scream.org/mailman/listinfo/commits
-State: Open for subscription, but no posts should be sent here.
-Purpose: Daily commit logs from the i-scream CVS repository are sent to this
-list. If you wish to keep up on development, join this list.
-
cvs-all@i-scream.org
- -
-Information: http://lists.i-scream.org/mailman/listinfo/cvs-all
-State: Open for subscription, but no posts should be sent here.
-Purpose: Emails are sent to this list whenever a commit happens to the i-scream
-cvs repository. If you want to be informed about commits as they happen, join
-this list.
-
users@i-scream.org
- -
-Information: http://lists.i-scream.org/mailman/listinfo/users
-State: Open for subscription and posts.
-Purpose: For discussion between users, developers, and anyone else. This is the
-place to ask questions and get support.
-
Subscribing
- --If you wish to join one of the open lists, follow the information link by -by the relevant link above. You can also email listname-request@i-scream.org, -where listname is one of the lists above, with subscribe in the body. -
- -Archives
- --We now have archives of the lists, from May 2003. A link to the archives can -be found on the information page for each list above. -
- -Viruses and Spam
- --All lists are scanned using -MailScanner to remove viruses before they get sent out to list members. -We also use MailScanner to tag spam messages accordingly, and ensure that such -messages are moderated. -
-+ i-scream Mailing Lists +
++ i-scream runs a number of mailing lists geared towards both + developers and users of i-scream products. At the present + time the lists are generic to all products, but if the + volume of e-mail rises it may become necessary to create + per-project mailing lists. Here are a current lists. +
++ dev@i-scream.org +
+
+ Information:
+ http://lists.i-scream.org/mailman/listinfo/dev
+ State: Closed
+ Purpose: A discussion forum for developers only.
+ This can also be used to contact the development team as a
+ whole.
+
+ commits@i-scream.org +
+
+ Information:
+ http://lists.i-scream.org/mailman/listinfo/commits
+ State: Open for subscription, but no posts should be
+ sent here.
+ Purpose: Daily commit logs from the i-scream CVS
+ repository are sent to this list. If you wish to keep up on
+ development, join this list.
+
+ cvs-all@i-scream.org +
+
+ Information:
+ http://lists.i-scream.org/mailman/listinfo/cvs-all
+ State: Open for subscription, but no posts should be
+ sent here.
+ Purpose: Emails are sent to this list whenever a
+ commit happens to the i-scream cvs repository. If you want
+ to be informed about commits as they happen, join this
+ list.
+
+ users@i-scream.org +
+
+ Information:
+ http://lists.i-scream.org/mailman/listinfo/users
+ State: Open for subscription and posts.
+ Purpose: For discussion between users, developers,
+ and anyone else. This is the place to ask questions and get
+ support.
+
+ Subscribing +
++ If you wish to join one of the open lists, follow the + information link by by the relevant link above. You can + also email listname-request@i-scream.org, where listname is + one of the lists above, with subscribe in the body. +
++ Archives +
++ We now have archives of the lists, from May 2003. A link to + the archives can be found on the information page for each + list above. +
++ Viruses and Spam +
++ All lists are scanned using + MailScanner to + remove viruses before they get sent out to list members. + We also use MailScanner to tag spam messages accordingly, + and ensure that such messages are moderated. +
+