Difference between revisions of "Project Snowstorm"

From Second Life Wiki
Jump to navigation Jump to search
m (add link to codereview documentation)
(Clean up quick links display, remove some outdated Q&A)
Line 18: Line 18:
* Share work processes, branches, and backlog.
* Share work processes, branches, and backlog.
* Demonstrate rapid responsiveness to feedback and contributions from the open source community
* Demonstrate rapid responsiveness to feedback and contributions from the open source community
* Provide builds from the Development (integration) repository bi-weekly
* Provide daily builds from the Development (integration) repository
'''Improve user experience''':
'''Improve user experience''':
* Clean up broken glass
* Clean up broken glass
Line 29: Line 29:
* [[User:Esbee Linden|Esbee Linden]] - Product/Business Lead
* [[User:Esbee Linden|Esbee Linden]] - Product/Business Lead
* [[User:Oz_Linden|Oz Linden]] - Open Source Lead
* [[User:Oz_Linden|Oz Linden]] - Open Source Lead
* [[User:Merov_Linden|Merov Linden]] and three contract engineers. Alas, [[User:Tofu_Linden|Tofu Linden]] and [[User:Aimee_Linden|Aimee Linden]] are no longer with the team.
* [[User:Merov_Linden|Merov Linden]]  
* Grumpity ProductEngine and three contract engineers.
* Open Source Contributors
* Open Source Contributors
}}
}}
{{Project Snowstorm Nav|width=100%}}


|valign="top" width="50%"|
|valign="top" width="50%"|
{{Box|News, Dec 9, 2010|2=
The Snowstorm team has kicked off Sprint 9. Here's a link to our task board for this sprint (hopefully the link will work!):
https://jira.secondlife.com/secure/TaskBoard.jspa?selectedBoardId=&type=VB&selectedProjectId=10244&colPage=1


The team is in the process of triaging additional tickets for this sprint that might be of interest to the community.
{{Box|Quick Links|2={{Project Snowstorm Nav|nobox=true}}}}
}}
{{Box|Communications|2=
{{Box|Communications|2=
*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])
Line 56: Line 52:
{{ViewerDevelopmentInstallers}}
{{ViewerDevelopmentInstallers}}
}}
}}
{{Box|Processes|2=
 
|-
|}
==Processes==


Snowstorm uses a modified [http://en.wikipedia.org/wiki/Scrum_%28development%29 scrum] process.   
Snowstorm uses a modified [http://en.wikipedia.org/wiki/Scrum_%28development%29 scrum] process.   
Line 77: Line 76:
''Note: Changes that introduce new Viewer features may not be submitted for integration without having been reviewed and accepted into the product backlog.  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.''
''Note: Changes that introduce new Viewer features may not be submitted for integration without having been reviewed and accepted into the product backlog.  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.''
}}
}}
|-
|}


==Questions & Answers==
==Questions & Answers==


; What is the team process?
: We use a modified Scrum process
:* We intend to release development builds every Wednesday
:** We focus on integration of new things on Mondays.
:** Wednesday is test, release, and reprioritization day.
:** We will create a Second Life Development Viewer channel for the releases.
; What is our release strategy?
: See the [[Viewer Integration and Release Processes]] page
; What are the steps to develop a Viewer change?
: See [[Develop Viewer Code]]
; How are “big features” released?
: The project team for the feature (whether inside or outside Linden Lab) creates a clone of the development repository and develops the feature there; we call this a "Project branch".
: Projects are encouraged to build the Viewer from the Project branch and give it to residents to test and experiment with the feature.
: When the feature is ready, the Snowstorm team pulls it back to the development repository.
: Our goal is short term, low cost, individual fixes, aimed at incremental improvements that will improve the Viewer.  Other teams within Linden Lab will normally be aiming for larger, feature-centered, high-value projects that will require integration of resources across multiple technology centers.
; Who gets commit access?
; Who gets commit access?
: Individual development teams decide who has commit access to their Project branches.
: Individual development teams 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. Nothing in that queue should be a surprise, as all of it should have gone through the Viewer Product Team. The Snowstorm team commits to servicing the items in that queue within 1 business day.
: For the Development branch, the Snowstorm Team has a JIRA-based queue for requests for integration (pull requests) from Project branches. Nothing in that queue should be a surprise, as all of it should have gone through the Viewer Product Team. The Snowstorm team commits to servicing the items in that queue within 1 business day.
; Which issue tracker are we using?
; Which issue tracker are we using?
: We’ll continue to use pJira until the new integrated Jira 4 becomes available. We’ll be using VWR and moving appropriate open issues from SNOW and Linden Lab internal projects (these will become part of the Snowstorm Team backlog).
: We use the public [https://jira.secondlife.com/ Jira]. New issues should be created in the VWR project, and we'll move appropriate open issues from SNOW and Linden Lab internal projects (these will become part of the Snowstorm Team backlog) to the public STORM process.


[[Category:Open Source Portal]]
[[Category:Open Source Portal]]

Revision as of 05:56, 24 December 2010

Snowstorm-icon.png
Snowstorm is the name of the team responsible for coordinating development and integration of the Second Life Viewer 2, and for engaging the open source development community in its evolution. The Snowstorm team and Project Snowstorm started in August, 2010.


Mission

To improve the performance, reliability, and ease of use of the Second Life Viewer, while enabling the rapid, effective deployment of new Viewer features and functionality to the Second Life Resident population.

Goals

Evaluate & Prioritize work by asking:

Does it make Second Life faster, easier, and more fun?

Work in the open:

  • Share work processes, branches, and backlog.
  • Demonstrate rapid responsiveness to feedback and contributions from the open source community
  • Provide daily builds from the Development (integration) repository

Improve user experience:

  • Clean up broken glass
  • Fix Viewer bugs
  • Import improvements from Snowglobe, other Third Party Viewers, and open source contributors
  • Add small features that have high value/low cost

Team


Testing

Latest Development Viewers:
Windows | Macintosh | Linux
Details for these builds (build logs, included changesets)


Processes

Snowstorm uses a modified scrum process.

We maintain a list of all the work we'd like to be doing, called the Product Backlog; it is a public living document, and new proposals may be added to it at any time:

Work is organized into two week sprints. At the beginning of each sprint, we choose items to work on from the product backlog to construct the sprint backlog, the list of tasks we are committing to complete in the sprint. Once defined, we do not normally change this list during the sprint. We track progress daily at the Snowstorm Team Standup - a short (target: 15 minutes) meeting in which contributors who have committed to deliverables in the sprint report on daily progress, goals, and impediments:

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.

Note: Changes that introduce new Viewer features may not be submitted for integration without having been reviewed and accepted into the product backlog. 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. }}

Questions & Answers

Who gets commit access?
Individual development teams 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. Nothing in that queue should be a surprise, as all of it should have gone through the Viewer Product Team. 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 SNOW and Linden Lab internal projects (these will become part of the Snowstorm Team backlog) to the public STORM process.
Retrieved from "https://wiki.secondlife.com/w/index.php?title=Project_Snowstorm&oldid=1129352"