Difference between revisions of "Project Snowstorm"
Jump to navigation
Jump to search
Snowstorm is the name of the team responsible for coordinating development and integration of the Second Life Viewer, and for engaging the open source development community in its evolution. The Snowstorm team and Project Snowstorm started in August, 2010.
m (→Processes) |
m |
||
| Line 6: | Line 6: | ||
{{Box|Communications|2= | {{Box|Communications|2= | ||
*[[User:Oz_Linden|Oz Linden]], Snowstorm lead | |||
*Email list: [https://lists.secondlife.com/cgi-bin/mailman/listinfo/opensource-dev opensource-dev] ([http://lists.secondlife.com/pipermail/opensource-dev/ archive]) | *Email list: [https://lists.secondlife.com/cgi-bin/mailman/listinfo/opensource-dev opensource-dev] ([http://lists.secondlife.com/pipermail/opensource-dev/ archive]) | ||
*IRC: [irc://irc.freenode.org/opensl #opensl on freenode] | *IRC: [irc://irc.freenode.org/opensl #opensl on freenode] | ||
| Line 18: | Line 19: | ||
The following is links to the most recent builds from the main viewer-development integration repository: | The following is links to the most recent builds from the main viewer-development integration repository: | ||
{{ViewerDevelopmentInstallers}} | {{ViewerDevelopmentInstallers}} | ||
and we also frequently publish [[Downloading test builds|test builds]] for things that have not yet been integrated. | and we also frequently publish [[Downloading test builds|test builds]] for things that have not yet been integrated. | ||
}} | }} | ||
| Line 25: | Line 24: | ||
==Processes== | ==Processes== | ||
By nature, open source contributions generally do not fit well into schedules, but getting them into the main stream of viewer development does require some structure. If you have work that you'd like to do, it helps to understand our [[Viewer Integration and Release Processes]]. | |||
There is a page on [[How To Propose A Viewer Feature]]; the Snowstorm team meets every other week with the Product Team to review open source proposals for open source contributions. The goals of this review are: | |||
* To determine whether or not the proposal is one that fits into our vision of how the viewer should work | |||
* To ensure that it does not conflict with other work being done inside the Lab | |||
It helps to have a comprehensive and specific description of the proposed change; what the user interface will be, how it will affect the shared experience of users, what backward compatibility issues it may have, etc. For obvious bug fixes, the review can be nearly pro forma, but even then we may ask you to wait until another time or to modify the proposed fix in some way. The result of this review may be that we will ask you to modify or refine the idea further, or we may decide that it is not suitable for inclusion in the main viewer code. | |||
{{KBnote|Changes that introduce new Viewer features may not be submitted for integration without having a proposal reviewed and accepted first. Changes to fix a bug that the triage process has Accepted may be submitted at any time so long as all integration criteria have been met (but a proposal for these is a good idea). | {{KBnote|Changes that introduce new Viewer features may not be submitted for integration without having a proposal reviewed and accepted first. Changes to fix a bug that the triage process has Accepted may be submitted at any time so long as all integration criteria have been met (but a proposal for these is a good idea). | ||
}} | }} | ||
In addition to its own development tasks, the Snowstorm team is responsible for integration of all contributions to the Viewer from other Linden Lab development teams and from open source. The submission process is described in [[How To Submit A Viewer Change]]. | |||
===Other Helpful Links=== | |||
* [[Develop Viewer Code]] a quick overview of how to set up and manage your working repositories | |||
** [[Basic Mercurial Workflow|More comprehensive Mercurial workflow]] (not needed for small changes) | |||
==Questions & Answers== | ==Questions & Answers== | ||
Revision as of 09:55, 7 December 2011
Communications
|
TestingThe following is links to the most recent builds from the main viewer-development integration repository: Latest Development Viewers: Windows | Macintosh | Linux Details for these builds (build logs, included changesets)
|
Processes
By nature, open source contributions generally do not fit well into schedules, but getting them into the main stream of viewer development does require some structure. If you have work that you'd like to do, it helps to understand our Viewer Integration and Release Processes.
There is a page on How To Propose A Viewer Feature; the Snowstorm team meets every other week with the Product Team to review open source proposals for open source contributions. The goals of this review are:
- To determine whether or not the proposal is one that fits into our vision of how the viewer should work
- To ensure that it does not conflict with other work being done inside the Lab
It helps to have a comprehensive and specific description of the proposed change; what the user interface will be, how it will affect the shared experience of users, what backward compatibility issues it may have, etc. For obvious bug fixes, the review can be nearly pro forma, but even then we may ask you to wait until another time or to modify the proposed fix in some way. The result of this review may be that we will ask you to modify or refine the idea further, or we may decide that it is not suitable for inclusion in the main viewer code.
 |
Note: Changes that introduce new Viewer features may not be submitted for integration without having a proposal reviewed and accepted first. Changes to fix a bug that the triage process has Accepted may be submitted at any time so long as all integration criteria have been met (but a proposal for these is a good idea). |
In addition to its own development tasks, the Snowstorm team is responsible for integration of all contributions to the Viewer from other Linden Lab development teams and from open source. The submission process is described in How To Submit A Viewer Change.
Other Helpful Links
- Develop Viewer Code a quick overview of how to set up and manage your working repositories
- More comprehensive Mercurial workflow (not needed for small changes)
Questions & Answers
- Who gets commit access?
- Commit access by open source contributors is not available to any Linden Lab repository, including viewer-development.
- Individual development teams, whether inside or outside Linden Lab, decide who has commit access to their Project branches.
- For the Development branch, the Snowstorm Team has a JIRA-based queue for requests for integration (pull requests) from Project branches that have met the integration criteria. The Snowstorm team commits to servicing the items in that queue within 1 business day.
- Which issue tracker are we using?
- We use the public Jira. New issues should be created in the VWR project, and we'll move appropriate open issues from there and Linden Lab internal projects (these will become part of the Snowstorm Team backlog) to the public STORM process.