Difference between revisions of "OpenSource-Dev"

From Second Life Wiki
Jump to: navigation, search
m (Guidelines: removed spurious "the")
m
Line 1: Line 1:
 
{{Open Source Portal|parent=Developer communication tools}}
 
{{Open Source Portal|parent=Developer communication tools}}
  
[https://lists.secondlife.com/cgi-bin/mailman/listinfo/opensource-dev opensource-dev@lists.secondlife.com] - mailing list for discussing open source development issues related to Second Life.  This is a high-traffic mailing list (as many as 30-40 messages/day on a busy day).
+
[https://lists.secondlife.com/cgi-bin/mailman/listinfo/opensource-dev opensource-dev@lists.secondlife.com] - mailing list for discussing open source development issues related to Second Life.
  
 
*  '''[https://lists.secondlife.com/cgi-bin/mailman/listinfo/opensource-dev Subscribe to opensource-dev@lists.secondlife.com]''' (or [https://lists.secondlife.com/cgi-bin/mailman/options/opensource-dev unsubscribe])
 
*  '''[https://lists.secondlife.com/cgi-bin/mailman/listinfo/opensource-dev Subscribe to opensource-dev@lists.secondlife.com]''' (or [https://lists.secondlife.com/cgi-bin/mailman/options/opensource-dev unsubscribe])
Line 27: Line 27:
 
*  Please remember the old mantra "praise in public, criticize in private".  On-list reprimands are rarely of interest to the general mailing list.
 
*  Please remember the old mantra "praise in public, criticize in private".  On-list reprimands are rarely of interest to the general mailing list.
 
*  If you are asking a question to the list, either [https://lists.secondlife.com/pipermail/opensource-dev/ browse the archives] or do a [http://www.google.com/search?hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&hs=POT&q=site%3Alists.secondlife.com%2Fpipermail%2Fopensource-dev%2F&btnG=Search keyword search of the archives] first to check if your question has already been asked and answered.
 
*  If you are asking a question to the list, either [https://lists.secondlife.com/pipermail/opensource-dev/ browse the archives] or do a [http://www.google.com/search?hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&hs=POT&q=site%3Alists.secondlife.com%2Fpipermail%2Fopensource-dev%2F&btnG=Search keyword search of the archives] first to check if your question has already been asked and answered.
*  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.  
+
*  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.  One post per 48 hours should be sufficient to bring it to everyone's attention.
+
*  If the topic is not specifically a Second Life development-related topic, it should be redirected to an appropriate forum immediately.  
*  It may be helpful to use the keywords below (in the "Subject Line Keywords" section) when posting, especially the "strongly recommended" keywords.
+
 
*  Most LSL scripting issues are better addressed on the [https://lists.secondlife.com/cgi-bin/mailman/listinfo/secondlifescripters secondlifescripters mailing list].
 
*  Most LSL scripting issues are better addressed on the [https://lists.secondlife.com/cgi-bin/mailman/listinfo/secondlifescripters secondlifescripters mailing list].
  
 
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.
 
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.
 
== Subject Line Keywords ==
 
 
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
 
 
Strongly recommended (since they are arguably a little off-topic):
 
* [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:
 
* [ANN] announcements
 
* [VWR] questions about viewer releases.  Analogous to [https://jira.secondlife.com/browse/VWR the "VWR" project on jira.secondlife.com]
 
* [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]
 
* [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:OpenSource-Dev|the talk page]].
 
  
 
== Autoreply Software ==
 
== Autoreply Software ==
Line 72: Line 47:
 
== SLDev Traffic ==
 
== SLDev Traffic ==
  
Old copies of [[SLDev Traffic]], a weekly summary of this mailing list, are still available, but are no longer being written.  Volunteers to help revive this useful service would be greatly appreciated.
+
Old copies of [[SLDev Traffic]], a weekly summary of this mailing list, are still available, but are no longer being written.   
  
 
== Related mailing lists ==
 
== Related mailing lists ==
  
=== sldev-commits ===
+
;viewer-development-commits
 +
:This is for automated notices of code being committed to the viewer-development repository.  See https://lists.secondlife.com/cgi-bin/mailman/listinfo/viewer-development-commits  
  
This is for automated notices of activity on svn.secondlife.com.  See https://lists.secondlife.com/cgi-bin/mailman/listinfo/sldev-commits for more information
+
;viewer-development-builds
 +
:This is for automated notices of build results in the internal Linden Lab build farm of the viewer-development repository.  See https://lists.secondlife.com/cgi-bin/mailman/listinfo/viewer-development-builds

Revision as of 06:15, 22 December 2010

opensource-dev@lists.secondlife.com - mailing list for discussing open source development issues related to Second Life.

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

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 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.
  • 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 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.
  • If you are asking a question to the list, either browse the archives or do a keyword search of the archives first to check if your question has already been asked and answered.
  • 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.
  • Most LSL scripting issues are better addressed on the secondlifescripters mailing list.

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.

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.

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.

SLDev Traffic

Old copies of SLDev Traffic, a weekly summary of this mailing list, are still available, but are no longer being written.

Related mailing lists

viewer-development-commits
This is for automated notices of code being committed to the viewer-development repository. See https://lists.secondlife.com/cgi-bin/mailman/listinfo/viewer-development-commits
viewer-development-builds
This is for automated notices of build results in the internal Linden Lab build farm of the viewer-development repository. See https://lists.secondlife.com/cgi-bin/mailman/listinfo/viewer-development-builds