Thanks for your interest in contributing to Second Life! This document summarizes some of the most important points for people looking to contribute to the platform especially those looking to provide bug reports and code changes.
Second Life has multiple channels for communication. Some of these channels are more end-user focused, while others are more tailored for developer-to-developer or support.
- feedback.secondlife.com is Second Life's primary community engagement forum. Ideas and bug reports should be placed here unless they relate to ongoing development issues and developer-to-developer communication.
- Public user groups are held on a regular basis, including those for discussing open source development, content creation, server topics and more.
- Github issues provide a means for staff to organize their work and collaborate with other developers. By default most user-facing discussions should happen on feedback.secondlife.com so that they are visible to more people, can build consensus, and be placed onto our public roadmap. Github issues are useful for collaboration between viewer forks and the official upstream and when engineering-specific and technical collaboration is beneficial.
- Official forums exist for many topics including content creation, scripting, social topics and more.
- The opensource-dev mailing list is useful for announcements and discussion between viewer maintainers.
Report bugs and provide ideas for features using the respective board on Second Life's feedback portal:
- Features
- Scripting bugs
- Scripting features
- Server bugs
- Viewer bugs
- Web/Marketplace bugs
- Web/Marketplace features
Creating posts on feedback.secondlife.com is important as it allows the greatest exposure and input from Second Life users. It also allows Linden Lab staff to place work on a single public roadmap.
Issues created on feedback.secondlife.com are imported onto Github after they have been reviewed by staff and accepted.
If you wish to contribute a new pull request, please ensure that:
- You talk to other developers about how best to implement the work.
- The functionality is desired. Be sure to talk to users and Second Life staff to ensure the work is a good idea and will be accepted.
- The work is high quality and the PR follows PR etiquette
- You have tested the work locally
The Git Style Guide is also a good reference for best git practices.