Difference between revisions of "Open Source Portal"

From Second Life Wiki
Jump to navigation Jump to search
m (Main Page moved to Open Source Portal: Will be creating a new Main Page, current prototype is at New Main Page (which is too sparse to use just yet))
m (Remove references to bitbucket)
 
(49 intermediate revisions by 17 users not shown)
Line 1: Line 1:
{{Multi-lang}}
__NOTOC__
__NOTOC__
{{Open Source Portal/Links}}
{{Open Source Portal/Featured}}


{|cellspacing="5px"
{|cellspacing="5px"  
|--
|valign="top" width="50%"|
|valign="top" width="50%"|
<div style="border: 1px solid #000">
<div id="box">
<h2 style="align: center; margin:0;background:#f9ff9b;font-size:120%;font-weight:bold;border:1px solid #f0ff00;text-align:left;color:#000;padding:0.2em 0.4em;">News</h2>
<div style="padding: 0.5em">
'''December 3, 2006''' - We're working on a new homepage for this wiki, at [[New Main Page]].  The idea is that multiple projects (volunteers, open source) will share this wiki, and that we'll have portal pages that are the home pages for those various projects.
</div></div>
|valign="top" width="50%"|
<div style="border: 1px solid #000">


<h2 style="margin:0;background:#e8cece;font-size:120%;font-weight:bold;border:1px solid #f2cece;text-align:left;color:#000;padding:0.2em 0.4em;">Project of the Week</h2>
<h2>[[Documentation]]</h2>
<div style="padding: 0.5em">
'''[[Protocol]]''' - A lot of our security audit is going to be centered around the protocol, so let's make sure we've got this documented as well as we possibly can.  Since most of the pages are currently empty, a simple (but very useful) exercise is to hit each of these pages with a top-of-your-head assessment of what files to look at and other hints that a reasonably competent but not specifically SL-knowledgeable programmer could use to document each item.  Something as simple as "I think most of what you need is in foobar/blech.cpp, but you might want to check ackbar/bleh.cpp as well".
</div></div>
|}
<div style="border: 1px solid #000">
<center>''Getting started''</center>
{|cellspacing="5px"
|valign="top" width="50%"|
<div style="border: 1px solid #000">
<h2 style="align: center; margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;">Learn</h2>
<div style="padding: 0.5em">
<div style="padding: 0.5em">


{{OSWikiLearnBox}}
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.   
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.  Much of this is still a work in progress, but since this is a wiki, you can help fill in the blanks!


* '''[[Features]]''' - An overview of the major components of the system as seen from an end user's perspective.  Links to specifications, test plans and other documentation can be found here.   
* '''[[Viewer Integration and Release Processes]]'''
* '''[[Viewer architecture]]''' - This is an overview of the viewer from a developer's perspective.
* '''[[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
* '''[[Protocol]]''' - in depth documentation of the protocol
* '''[[Extended FAQ]]''' - For questions that don't get covered in {{OSWebsite|faq|alt=the main open source FAQ}}.
* '''[[Server architecture|Server Architecture]]'''
* '''[[Glossary]]'''  


[[Documentation|more...]]
[[Documentation|more...]]
<h2>Puppetry</h2>
<div style="padding: 0.5em">
* '''[[How Puppetry Works]]'''
* '''[[Puppetry Development]]'''
* '''[[Puppetry Network Control]]'''
* '''[[Puppetry Mocap]]'''


</div></div>
</div></div>
|valign="top" width="50%"|
|valign="top" width="50%"|
<div style="border: 1px solid #000">
<div id="box">


<h2 style="margin:0;background:#cecee8;font-size:120%;font-weight:bold;border:1px solid #cecef2;text-align:left;color:#000;padding:0.2em 0.4em;">Participate</h2>
<h2>Ways to Participate</h2>
<div style="padding: 0.5em">
<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]]


{{OSWikiContribBox}}
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.  
 
We want your help to 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 for you, try helping someone who isn't having as much luck as you are.  If you run into issues, see if a bug report has been filed, and if it isn't file it.  If it has been filed, vote for it, perhaps filling in more detail.


Of course, if you ''are'' a developer, we can use your help.  Download the code, and see if you can get it to build.  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.
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.


[[Participating|more...]]
</div></div>
</div></div>
|-
|}
|}
</div>
 
 
[[Category:Portals]]

Latest revision as of 16:03, 31 March 2023

Featured Links

New-Snowstorm-icon.png
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...

Documentation

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.

more...

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.