Difference between revisions of "OpenSource-Dev"

From Second Life Wiki
Jump to: navigation, search
(adding unsubscribe direct link)
m
 
(28 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 +
{{KBnote|'''This list was recently migrated from the old mailman list to a new Google Group.'''
 +
 +
:Invitations were sent to all existing list members but may have been eaten by spam filters or other mail monsters; see below for how to subscribe.}}
 +
 
{{Open Source Portal|parent=Developer communication tools}}
 
{{Open Source Portal|parent=Developer communication tools}}
  
[https://lists.secondlife.com/cgi-bin/mailman/listinfo/sldev 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).
+
This list is for discussion of issues related to developing  and contributing to Second Life viewers.
  
'''[https://lists.secondlife.com/cgi-bin/mailman/listinfo/sldev Subscribe to SLDev@lists.secondlife.com]''' (or [https://lists.secondlife.com/cgi-bin/mailman/options/sldev unsubscribe])
+
'''IMPORTANT''': Please be sure to read the [[#Posting Policies and Guidelines]] below before posting to this mailing list.
*  '''Read a weekly summary of this mailing list: [[SLDev Traffic]]'''
+
*  [https://lists.secondlife.com/pipermail/sldev/ Browse the archive]
+
*  [http://www.google.com/coop/cse?cx=001010425210852223575%3Aogwhgz5_tue Search the archive]
+
*  View [[SLDev Usage Stats]]
+
  
== Policies ==
+
===Subscriptions===
  
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.
+
'''To subscribe to the list, send an email to [mailto:opensource-dev+subscribe@lists.secondlife.com opensource-dev+subscribe@lists.secondlife.com]''' (content does not matter).
  
*  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).
+
===Archives===
*  Please adhere to the [http://blog.secondlife.com/guidelines-for-blog-comments/ 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. 
+
*  If you have auto-reply email software (such as out-of-office notification), please make sure that it's configured correctly.  Failure to do so will cause you to receive moderated access until you assure us it's fixed.  See the Autoreply Software section below for more details.
+
  
== Posting guidelines ==
+
* [https://groups.google.com/a/lists.secondlife.com/forum/?utm_medium=email&utm_source=footer#!forum/opensource-dev opensource-dev@lists.secondlife.com Current list archive (also supports posting to the list via the web]
 +
* [https://list-archives.secondlife.com/ Browse the archives of the older incarnations of this list]
  
The sldev mailing list is for any software development issue related to Second Life (though most LSL scripting issues are better addressed on the [https://lists.secondlife.com/cgi-bin/mailman/listinfo/secondlifescripters 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:
+
== Posting Policies and Guidelines ==
  
*  Please remember the old mantra "praise in public, criticize in private".  On-list reprimands are rarely of interest to the general mailing list.
+
The opensource-dev mailing list is for development issue related to Second Life open source codeThe following policies are meant to ensure we can keep conversation civil and on-topic. "Policies" are rules that need to be followed to ensure continued posting privileges"Guidelines" have more wiggle room, but should be considered before posting.
* If you are asking a question to the list, search the [https://lists.secondlife.com/pipermail/sldev/ 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.
+
*  Please use the keywords below (in the "Subject Line Keywords" section) when posting, especially the "strongly recommended" keywords.
+
  
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.
+
=== Policies ===
  
== Subject Line Keywords ==
+
*  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 [https://wiki.secondlife.com/wiki/Linden_Lab_Official:Community_Participation_Guidelines community participation guidelines ].  We're going to preemptively set the "moderated" bit for repeat violators.
 +
*  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. 
 +
*  If you have auto-reply email software (such as out-of-office notification), please make sure that it's configured correctly.  Failure to do so will cause you to receive moderated access until you assure us it's fixed.  See the Autoreply Software section below for more details.
 +
*  If someone else is violating mailing list policy, do not reply to them on the list.  Reply to them offlist if you feel you need to engage them.  If you feel disciplinary action is required, send mail to the list administrator (<opensource-dev-owner@lists.secondlife.com>).  Engaging with them on-list is itself disruptive, and so may result in the moderation bit being set on your account.
  
When posting to the list, please take your best guess at the right subject line keyword to put on your email.  Some of the keywords below are strongly recommended, while some are purely optional.  However, all of them will help people organize
+
=== Guidelines ===
  
Strongly recommended (since they are arguably a little off-topic):
+
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 (800+ as of this writing), so please follow these guidelines when you post:
* [POLICY] issues about policy and etiquette on wiki, jira, and the mailing list, some licensing/legal logistics issues NOTE: licensing issues should be directed to licensing@lindenlab.com
+
* [META] repositories, creating inworld meeting places, getting and keeping the community organized, product cycle processes
+
* [WEB] questions/complaints about the website, jira, wiki, etc
+
  
Optional:
+
Please remember the old mantra "praise in public, criticize in private". On-list reprimands are rarely of interest to the general mailing list.
* [ANN] announcements
+
* Keep threads on topic.  If you want to talk about something unrelated to the subject of a thread, please '''do not begin your new topic by replying to an existing message'''.  Even if you change the Subject line, most threaded email readers and archives will still think that your reply is related and will sort it incorrectly.  This not only disrupts the thread you replied to, it can cause people to miss your message entirelySend a new message to the list address with your new topic.
* [VWR] questions about viewer releases. Analogous to [https://jira.secondlife.com/browse/VWR the "VWR" project on jira.secondlife.com]
+
If the topic is not specifically a Second Life development-related topic, it should be redirected to an appropriate forum immediately.  
* [SVC] questions about the Second Life service (simulators, login servers, web apis, general grid questions)Analogous to [https://jira.secondlife.com/browse/SVC the "SVC" project on jira.secondlife.com]
+
* This list is not for LSL questions or other SL issues besides open source software development.
* [IDEA] for new features ideas and proposals
+
* [VOICE] about voice activation features
+
* [HELP] for topic about building the viewer or other support request
+
* [I18N] for internationalization and localization problems
+
* [EVENTLET] eventlet questions
+
* [MULIB] mulib questions
+
* [PATCH] for patchy patches! For feedback on a patch, or just to let people know it exists so they can try it.
+
* [AWG] [[Architecture Working Group]]
+
  
If you have suggested changes for these keywords, please put your suggestion on [[Talk:SLDev|the talk page]].
 
  
 
== Autoreply Software ==
 
== Autoreply Software ==
Line 61: Line 46:
 
: ''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.''
 
: ''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.
+
If your autoreply software sends mail to the opensource-dev 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.
 
+
== Second Life <-> mailing list name mapping ==
+
 
+
Editing on this wiki is done using Second Life names, but posting on the mailing list is often done using another name (real name or non-Second Life alias).  We don't ask anyone to reveal any information they don't want to, but we do encourage those who don't use their Second Life names on the mailing list to put their name in the [[SLDev Resident Names]] table.
+

Latest revision as of 07:15, 18 May 2020

KBnote.png Note: This list was recently migrated from the old mailman list to a new Google Group.
Invitations were sent to all existing list members but may have been eaten by spam filters or other mail monsters; see below for how to subscribe.

This list is for discussion of issues related to developing and contributing to Second Life viewers.

IMPORTANT: Please be sure to read the #Posting Policies and Guidelines below before posting to this mailing list.

Subscriptions

To subscribe to the list, send an email to opensource-dev+subscribe@lists.secondlife.com (content does not matter).

Archives

Posting Policies and Guidelines

The opensource-dev mailing list is for development issue related to Second Life open source code. The following policies are meant to ensure we can keep conversation civil and on-topic. "Policies" are rules that need to be followed to ensure continued posting privileges. "Guidelines" have more wiggle room, but should be considered before posting.

Policies

  • 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 community participation guidelines . We're going to preemptively set the "moderated" bit for repeat violators.
  • 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.
  • If you have auto-reply email software (such as out-of-office notification), please make sure that it's configured correctly. Failure to do so will cause you to receive moderated access until you assure us it's fixed. See the Autoreply Software section below for more details.
  • If someone else is violating mailing list policy, do not reply to them on the list. Reply to them offlist if you feel you need to engage them. If you feel disciplinary action is required, send mail to the list administrator (<opensource-dev-owner@lists.secondlife.com>). Engaging with them on-list is itself disruptive, and so may result in the moderation bit being set on your account.

Guidelines

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 (800+ as of this writing), so please follow these guidelines when you post:

  • Please remember the old mantra "praise in public, criticize in private". On-list reprimands are rarely of interest to the general mailing list.
  • Keep threads on topic. If you want to talk about something unrelated to the subject of a thread, please do not begin your new topic by replying to an existing message. Even if you change the Subject line, most threaded email readers and archives will still think that your reply is related and will sort it incorrectly. This not only disrupts the thread you replied to, it can cause people to miss your message entirely. Send a new message to the list address with your new topic.
  • If the topic is not specifically a Second Life development-related topic, it should be redirected to an appropriate forum immediately.
  • This list is not for LSL questions or other SL issues besides open source software development.


Autoreply Software

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 opensource-dev 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.