Loop/wiki: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 10: Line 10:
* [https://wiki.mozilla.org/Firefox/Iterative_Hello_Development#Product_Backlog Product Backlog and Triage guidelines]
* [https://wiki.mozilla.org/Firefox/Iterative_Hello_Development#Product_Backlog Product Backlog and Triage guidelines]
* etherpad for [https://etherpad.mozilla.org/5S7ih39ybp Weekly Loop project sync 11:30 AM PST Tuesdays]  
* etherpad for [https://etherpad.mozilla.org/5S7ih39ybp Weekly Loop project sync 11:30 AM PST Tuesdays]  
* etherpad for [https://etherpad.mozilla.org/haeLwWEkZV daily 8 AM PST stand-up]
* google doc for [https://docs.google.com/document/d/1zTRjghpxL_znjE8BJTiZgOsYUuUrtkpYsajodeT9aiA/edit daily 8 AM PST stand-up]
* etherpad for [https://etherpad.mozilla.org/loop-retrospectives Friday 8 AM Retrospective]
* etherpad for [https://etherpad.mozilla.org/loop-retrospectives Friday 8 AM Retrospective]
* etherpad for [https://etherpad.mozilla.org/brainstormtesthello prioritizing tech-debt]
* [https://wiki.mozilla.org/Loop/Try_Loop#Desktop_Firefox_Loop_Client Trying Hello information]
* [https://wiki.mozilla.org/Loop/Try_Loop#Desktop_Firefox_Loop_Client Trying Hello information]
  |-  
  |-  
Line 19: Line 18:
* Current relevant links to PM working areas
* Current relevant links to PM working areas
  |  
  |  
* [https://mozilla.aha.io/published/ee01babdb1248b9a575ff26253c08819?page=1 in discussion plan for Fx39]
* [need to update link for Aha roadmap]
* [https://docs.google.com/a/mozilla.com/presentation/d/1ewzf4EP5xlKsjvRas9z8Nsg0Mk_k59cYPmJSlRfjORw/edit?usp=drive_web February Roadmap review]
* [need to update link Roadmap review]
* [https://mozilla.aha.io/published/65261d18ecddc6fdd7788a16ae416306?page=2 Aha roadmap]
* [https://mozilla.aha.io/published/65261d18ecddc6fdd7788a16ae416306?page=2 Aha roadmap]
  |-  
  |-  
Line 27: Line 26:
*[https://useradvocacy.mozilla.org/dashboards/hello-v1/ Feedback] from last 42 days
*[https://useradvocacy.mozilla.org/dashboards/hello-v1/ Feedback] from last 42 days
*[https://metrics.services.mozilla.com/loop-server-dashboard/ Metrics Dashboard (in development)]
*[https://metrics.services.mozilla.com/loop-server-dashboard/ Metrics Dashboard (in development)]
*[https://docs.google.com/a/mozilla.com/spreadsheets/d/12noPqQ2fJXH_5cJbaY8J1eAKqDBN0PHti4saykmIZRs/edit#gid=319952689 Getting Started and Link Clicker numbers]
  |-  
  |-  


Line 37: Line 37:
* [https://wiki.mozilla.org/QA/Services/LoopTestEnvironments Loop-Server Test Environments]
* [https://wiki.mozilla.org/QA/Services/LoopTestEnvironments Loop-Server Test Environments]
* [https://wiki.mozilla.org/QA/Services/LoopServerLoadTesting Loop-Server Load Testing]
* [https://wiki.mozilla.org/QA/Services/LoopServerLoadTesting Loop-Server Load Testing]
|- 
* [https://wiki.mozilla.org/Services/Loop Cloud Services for Loop]
 
| UX
* Current relevant links to UX working areas
|
* [https://projects.invisionapp.com/share/GU1Z0XTXR#/screens Reference doc for V1 of Sharing]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1128101 in progress: Integration with Share Panel]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1115340 in progress: Context Sharing]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1087934 in progress: Panel Redesign]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1130425 in progress: Link Clicker Parity]
* [http://cl.ly/image/0r3U2T1M3I2k in progress: LinkClicker UI re-design]
  |-  
  |-  


Line 61: Line 51:
* etherpad for [https://etherpad.mozilla​.org/webrtcweekly Weekly webRTC platform stand-up]
* etherpad for [https://etherpad.mozilla​.org/webrtcweekly Weekly webRTC platform stand-up]
* [https://wiki.mozilla.org/Electrolysis#Schedule e10s timing plan]
* [https://wiki.mozilla.org/Electrolysis#Schedule e10s timing plan]
* etherpad for [https://etherpad.mozilla.org/hello-push-jan-2015 collaboration with Push team]
* etherpad for [https://webrtc.etherpad.​mozilla.org/tokbox-meeti​ng Weekly sync between Mozilla and TokBox]
* etherpad for [https://webrtc.etherpad.​mozilla.org/tokbox-meeti​ng Weekly sync between Mozilla and TokBox]
  |-  
  |-  
Line 68: Line 57:
* In process of identifying new QA contacts as teams have moved around
* In process of identifying new QA contacts as teams have moved around
  |  
  |  
* [https://moztrap.mozilla.org/manage/cases/? Moztrap for covering desktop cases]
* [https://moztrap.mozilla.org/manage/cases/? Moztrap for covering desktop cases.] Go to "Manage" tab and search Loop or Hello or webRTC
* [https://wiki.mozilla.org/Media/WebRTC/Testing WebRTC testing]
* [https://wiki.mozilla.org/Media/WebRTC/Testing WebRTC testing]
* [https://drive.google.com/a/mozilla.com/file/d/0B1KBl68pRmhsalpMUGZJQ1lvSlk/edit perf focused test cases]
* [https://drive.google.com/a/mozilla.com/file/d/0B1KBl68pRmhsalpMUGZJQ1lvSlk/edit perf focused test cases]
Line 98: Line 87:
  |-  
  |-  


| Links that need a home or to be deprecated
*give input/ideas to [mailto:shell@mozilla.com Shell]
|
* [https://wiki.mozilla.org/Media/WebRTC/Peak Notes on getting WebRTC working on a Peak]
* [https://wiki.mozilla.org/Media/WebRTC/Peak Notes on getting WebRTC working on a Peak]
* [https://wiki.mozilla.org/Media/WebRTC/Updating_Process Updating from upstream webrtc.org]
* [https://wiki.mozilla.org/Media/WebRTC/Updating_Process Updating from upstream webrtc.org]

Latest revision as of 00:07, 7 July 2015

Current links, wiki pages, and tools

This list is not exhaustive and some wiki's will likely only make sense if you were at the meeting. Many wiki's though are good reference if you can't attend a meeting or to put in agenda items before the next meeting.

Area Links
Hello Client Front-end
Product Management
  • Current relevant links to PM working areas
  • [need to update link for Aha roadmap]
  • [need to update link Roadmap review]
  • Aha roadmap
Metrics
Technical Documentation
  • Client Architecture
  • Server Architecture
Cross Team Collaboration
QA
  • In process of identifying new QA contacts as teams have moved around
Marketing and Communications
Support
Continued Improvement
  • Every couple of releases we have a postmortem to review what we could have done better.
  • We take the hottest topics and brainstorm on ways to improve and action items.