Difference between revisions of "Open Source Portal"
m (Remove references to bitbucket) |
|||
(67 intermediate revisions by 20 users not shown) | |||
Line 1: | Line 1: | ||
{{Multi-lang}} | |||
__NOTOC__ | |||
{{Open Source Portal/Links}} | |||
{{Open Source Portal/Featured}} | |||
{|cellspacing="5px" | |||
|-- | |||
|valign="top" width="50%"| | |||
<div id="box"> | |||
= | <h2>[[Documentation]]</h2> | ||
<div style="padding: 0.5em"> | |||
* [ | A lot of the documentation below is geared toward developers. However, many aspects of the system don't require a deep technical background to learn. | ||
* [ | |||
* [ | * '''[[Viewer Integration and Release Processes]]''' | ||
* '''[[Viewer source|Viewer Source Code]]''' | |||
** '''[[Viewer Doxygen]]''' - browse source and documentation | |||
** '''[[Coding Standard]]''' | |||
* '''[[Linden Lab Official:Second Life Viewer Licensing Program|Viewer Licensing]]''' | |||
* '''[[Viewer architecture]]''' - Overview of the Viewer from a developer's perspective. | |||
* '''[[XUI Reference]]''' | |||
* '''[[Third Party Libraries]]''' | |||
* '''[[Features]]''' - An overview of the major components of the system as seen from an end user's perspective, including links to specifications, test plans and other documentation. | |||
* '''[[Protocol]]''' - in depth documentation of the protocol | |||
* '''[[Server architecture|Server Architecture]]''' | |||
* '''[[Glossary]]''' | |||
[[Documentation|more...]] | |||
<h2>Puppetry</h2> | |||
<div style="padding: 0.5em"> | |||
* '''[[How Puppetry Works]]''' | |||
* '''[[Puppetry Development]]''' | |||
* '''[[Puppetry Network Control]]''' | |||
* '''[[Puppetry Mocap]]''' | |||
</div></div> | |||
|valign="top" width="50%"| | |||
<div id="box"> | |||
<h2>Ways to Participate</h2> | |||
<div style="padding: 0.5em"> | |||
* [[Developer communication tools|Communication tools (mailing list/IRC/etc)]] | |||
* [[Get source and compile]] | |||
* Read about the [[Linden_Lab_Official:GitHub_CLA|simpler CLA process]] | |||
* Testing efforts | |||
** [[Downloading test builds]] | |||
** [[Bug Reporting 101|File and vet bugs]] | |||
* Work on one of [https://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=14035 these outstanding open development suggestions] | |||
* [[Feature Contributions|Propose and refine feature contributions]] | |||
* [[Submitting code|Submit code]] | |||
* [[Crash Reports|Inspect crash reports]] | |||
* [[Implementing new features|Implement new features]] | |||
* [[Profiling and Optimization|Profile and Optimize]] | |||
* [[Finding leaks|Find memory leaks]] | |||
Help make the Second Life Viewer better! You don't need to know C++ or even programming to help. Some of the toughest jobs in software development have nothing to do with writing code. Just grab [[Downloading test builds|a test build]] and try playing around with it. Let us know what you think on email, on the forum, or IRC. If it's not working for you, try to get help there. If it is working, try helping someone else. If you run into issues, see if a bug report has been filed; if not, file one. | |||
Of course, if you ''are'' a developer, we can use your help. Download the code - try your hand at fixing a bug, or extending the software through one of the APIs. There's a ton of ways you can help, and we welcome you regardless of your skill level. | |||
</div></div> | |||
|} | |||
[[Category:Portals]] |
Latest revision as of 16:03, 31 March 2023
Quick Links
Featured Links
Project Snowstorm
Open Source for the Linden Lab Second Life Viewer, and the ultimate integration point for all development of the official viewer both inside and outside Linden Lab. |
Where Are Contributors?
There are contributors to the Second Life Viewer all around the world... |
DocumentationA lot of the documentation below is geared toward developers. However, many aspects of the system don't require a deep technical background to learn.
Puppetry |
Ways to Participate
Help make the Second Life Viewer better! You don't need to know C++ or even programming to help. Some of the toughest jobs in software development have nothing to do with writing code. Just grab a test build and try playing around with it. Let us know what you think on email, on the forum, or IRC. If it's not working for you, try to get help there. If it is working, try helping someone else. If you run into issues, see if a bug report has been filed; if not, file one. Of course, if you are a developer, we can use your help. Download the code - try your hand at fixing a bug, or extending the software through one of the APIs. There's a ton of ways you can help, and we welcome you regardless of your skill level. |