SLDev@lists.secondlife.com - mailing list for discussing software development issues related to Second Life. This is a high-traffic mailing list (as many as 30-40 messages/day on a busy day).
- Subscribe to SLDev@lists.secondlife.com
- Read a weekly summary of this mailing list: SLDev Traffic
- Browse the archive
- Search the archive
- View SLDev Usage Stats
The sldev mailing list is for software development issue related to Second Life. The following policies are meant to ensure we can keep conversation civil and on-topic.
- This mailing list is for discussing problems and ideas that software developers can directly address and for collaboration on solutions and improvements, not for turning Linden Lab development staff into proxies to reach other parts of Linden Lab (e.g. legal, executive, human resources, etc).
- Please adhere to the guidelines for blog.secondlife.com. Since we can't delete comments that are in violation, we're going to instead preemptively set the "moderated" bit for repeat violators. Given how much spam we also get, that will probably have the effect of making the list read-only for those members.
- Constructive criticism is welcome, but general complaints which only serve to discourage use of Second Life or discourage cooperation with Linden Lab should be taken elsewhere.
The sldev mailing list is for any software development issue related to Second Life (though most LSL scripting issues are better addressed on the secondlifescripters mailing list). In addition to the policies above, here's some guidelines. These aren't hard-and-fast rules, but rather, good etiquette. There are a lot of people on this list (552 as of this writing), so please follow these guidelines when you post:
- If you are asking a question to the list, search the archives first to check if your question has already been responded.
- If a topic generates more than five replies in less than 24 hours, it's time to redirect that conversation to one of our other tools, either the wiki, the bug tracker, or a thread in the appropriate forum.
- If the topic is not specifically a Second Life development-related topic (e.g. mailing list policy or a licensing discussion), it should be redirected to the wiki, the bug tracker, or the appropriate forum immediately. One post per 48 hours should be sufficient to bring it to everyone's attention.
- If after 48 hours, the topic seems to have died out on the alternate forum, it's ok to reraise the issue on this mailing list, summarizing the offlist conversation thus far, and calling for further comment in the alternate forum.
These guidelines try to balance between making sure that people have a large forum to raise and discuss a broad spectrum of issues, while at the same time ensuring that the list doesn't become overwhelmed with discussion on a single topic that may not be of interest to everyone on the list.
If you have autoreply software to notify people that you are out of the office, please make sure that the software complies with the "Personal Responder" guidelines defined in RFC 3834 - Recommendations for Automatic Responses to Electronic Mail. In particular:
- Personal and Group responses whose purpose is to notify the sender of a message of a temporary absence of the recipient (e.g., "vacation" and "out of the office" notices) SHOULD NOT be issued unless a valid address for the recipient is explicitly included in a recipient (e.g., To, Cc, Bcc, Resent-To, Resent-Cc, or Resent-Bcc) field of the subject message. Since a recipient may have multiple addresses forwarded to the same mailbox, recipient SHOULD be able to specify a set of addresses to the responder which it will recognize as valid for that recipient.
If your autoreply software sends mail to the sldev mailing list, you will be marked as a moderated member of the mailing list, meaning that all messages you send to the mailing list will need to be approved by a list moderator. You may request to be switched to an unmoderated member only after you can assure the list moderators that your autoreply software has been upgraded to comply with RFC 3834.