MozillaWiki

Firefox/searchandaddon: Difference between revisions

Page Discussion

Firefox/searchandaddon (view source)

Revision as of 18:52, 17 May 2016

6,380 bytes added ,  17 May 2016
m
→‎Key Bugzilla Queries: fixed query
(→‎Themes: risks)
 
(35 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=Firefox Search=
=Firefox Search=
problem statement or why we do this project and the scope of work focused on - intro for someone brand new.
problem statement or why we do this project and the scope of work focused on - intro for someone brand new.
==Project Introduction==
* '''Team Mailing list:''' if applicable
* '''Team IRC Channel:''' where does this team "hang-out"
*[https://wiki.mozilla.org/Firefox/IterativeDevelopment Summary of our plans for this year]
**links back to main Firefox page - Marco to create a section on main page for team summaries. 
**Quick high-level plans for the year for Desktop management and contributors. Likely completed by Kev/Dave with EPM help as needed.
***Here's an example of the overview from [https://wiki.mozilla.org/Platform/Roadmap#WebRTC_.2F_WebAudio Platform team for webRTC]
* '''Dependencies:''' feature, partner, resource, etc. that impact this projects ability to succeed - put links to other project pages.
==Links to Current info==
The [https://wiki.mozilla.org/Firefox/searchandaddon/links Links wiki page] is the central location for current focus, Roadmap, Metrics, UX, Marketing, tech-architecture, and more.
==Roles and Responsibilities==
The [https://wiki.mozilla.org/Firefox/Contacts Contacts Page] has the Roles and Responsibilities for Firefox teams, partner teams, and external partners.


==Meetings & Communications==
==Meetings & Communications==
Line 23: Line 8:
! Meeting !! Day of week !! Pacific Time !! Eastern Time !! Central European Time !! Vidyo Room !! Notes
! Meeting !! Day of week !! Pacific Time !! Eastern Time !! Central European Time !! Vidyo Room !! Notes
|-
|-
| '''Planning''' || bi-weekly at the start of the iteration on ___ || 0:00AM - 0:30AM || 0:00AM - 0:30PM || 0:00PM - 0:30PM || team vidyo room || [https://etherpad.mozilla.org/searchplanning etherpad]
| '''Planning''' || bi-weekly at the start of the iteration on Tuesday|| 9:00AM - 10:00AM || 0:00AM - 0:30PM || 0:00PM - 0:30PM || team vidyo room || [https://etherpad.mozilla.org/searchplanning etherpad]
|-
| '''Stand-up''' || Team decides || 0:00AM - 0:30AM || 0:00AM - 0:30PM || 0:00PM - 0:30PM || Team vidyo room || [https://etherpad.mozilla.org/searchplanning etherpad]
|-
|-
| '''Triage''' || Team decides || 0:00AM - 0:30AM || 0:00AM - 0:30PM || 0:00PM - 0:30PM || Team vidyo room || [https://wiki.mozilla.org/Firefox/searchandaddon#Key_Bugzilla_Queries Bugzilla queries], [https://etherpad.mozilla.org/searchplanning etherpad]
| '''Stand-up''' & '''Triage''' || TBD - 1 hour off week (first 1/2 stand-up, second half optional triage) || 0:00AM - 0:30AM || 0:00AM - 0:30PM || 0:00PM - 0:30PM || Team vidyo room || [https://wiki.mozilla.org/Firefox/searchandaddon#Key_Bugzilla_Queries Bugzilla queries], [https://etherpad.mozilla.org/searchplanning etherpad]
|-
|-
| '''Retrospective''' || Team decides || 0:00AM - 0:00AM || 0:00AM - 0:00PM || 0:00PM - 0:00PM || team vidyo room || [https://etherpad.mozilla.org/searchandaddon-retrospectives etherpad]
|}
|}


<p> </p>
==Key Bugzilla Queries==
* '''[http://mzl.la/1TGrUtG Team Product Backlog]:''' 
** Add '''fxsearch''' to triaged bugs and set Priority
**Optional
***Add a '''short descriptive area tag''' in the whiteboard when possible, to visually group bugs quickly in a list. ex: "[visual refresh] fxsearch"
**'''Importance''' will be left at default, "normal", unless a bug is on the line of being one Priority higher and lower - and then will be marked "Major" or "Minor" accordingly.
* '''Priorities''' follow this Standard:
** Priority 1 - Blocker, must-fix before shipping or a priority feature we are including in this release.
** Priority 2 - Major impact,  considering severity × probability. Not a blocker for shipping.  For Features we'd really like it, but wouldn't hold shipping for it.
** Priority 3 - Average Bug.  definitely a problem, but doesn't stop someone from using the product.
** Priority 4 - Minor or polish bugs that are real issues (especially in aggregate) and annoying.
** Priority 5 - Low-impact. something we'd fix, but mostly only bothers the discerning user. Little impact on usability.
<p> </p>
<p> </p>
*'''[http://mzl.la/1LqCwiy Untriaged Bugs]:'''Bugs under Firefox::Search without [fxsearch] in whiteboard
<p> </p>
<p> </p>


Line 48: Line 48:
* '''Iteration 42.3:'''  Tuesday July 28 - Monday August 10
* '''Iteration 42.3:'''  Tuesday July 28 - Monday August 10
<p> </p>
<p> </p>
==Themes==
==Themes==
As we plan what's coming next, [https://docs.google.com/a/mozilla.com/document/d/1de2o8Osl_z98BBfkt243i-dHdcKmQB15xJ9rShkwk3Q/edit?usp=sharing these are areas being discussed].  This is not a commitment to the next projects - just our scratch area, but it is in order of relative priority - including the work we've pulled for the sprints.
As we plan what's coming next, [https://docs.google.com/a/mozilla.com/document/d/1de2o8Osl_z98BBfkt243i-dHdcKmQB15xJ9rShkwk3Q/edit?usp=sharing these are areas being discussed].  This is not a commitment to the next projects - just our scratch area, but it is in order of relative priority - including the work we've pulled for the sprints.
*'''Unified Autocomplete:''' Necessary maintenance work to make the awesomebar easier to improve
*'''Partner Engine:''' issues relating to the integration of our partner's search engines
*'''Search Suggestions:''' Adding search suggestions to the awesomebar
*'''Search Suggestions:''' Adding search suggestions to the awesomebar
*'''Search Hijacking:''' Keep users on the search engine that they want
*'''Search Hijacking:''' Keep users on the search engine that they want
**'''Add-on Signing'''  
**'''Add-on Signing'''  
*'''Search UI:''' basically how our search access points work/look
*'''Search UI:''' basically how our search access points work/look
*'''Partner Engine:''' issues relating to the integration of our partner's search engines
 
<p></p>
<p></p>
Things we want to do - but not starting until higher priorities are done:
Things we want to do - but not starting until higher priorities are done:
Line 72: Line 72:


==Current==
==Current==
===Iteration - 40.3 May 11===
===Iteration - 41.3, through June 29===
* Focus on folks [http://tinyurl.com/ppcdd7f wrapping up bugs carried over from previous projects in addition to taking on new work as free up].
[https://bugzilla.mozilla.org/show_bug.cgi?id=958204 Theme 958204] '''Search Suggestions'''
<p> </p>
{| class="wikitable collapsible collapsed" style="width: 100%"
! Suggestions: Allow user to select a query from search suggestions in Awesome Bar
 
|-
|
* '''ID:'''  [https://bugzilla.mozilla.org/show_bug.cgi?id=1162140 Bug 1162140]
** Suggestions was turned on in Nightly to find bugs
** Disabled now until we land "opt-in/opt-out" user choice control.
 
<p> </p>
<bugzilla>
{
"f1":"blocked",
"o1":"equals",
"v1":"1162140",
"include_fields":"id, summary, status, assigned_to, cf_fx_points"
}
</bugzilla>
|}
<p> </p>
 
<p> </p>
{| class="wikitable collapsible collapsed" style="width: 100%"
! Suggestions: Search Suggestions in the AwesomeBar should be clearly identified as such
 
|-
|
* '''ID:'''  [https://bugzilla.mozilla.org/show_bug.cgi?id=1162142 Bug 1162142]
* UX done - hoping work will be done as well - dependent on bugs from landing first part of search and auto complete bugs
<p> </p>
<bugzilla>
{
"f1":"blocked",
"o1":"equals",
"v1":"1162142",
"include_fields":"id, summary, status, assigned_to, cf_fx_points"
}
</bugzilla>
|}
<p> </p>
 
{| class="wikitable collapsible collapsed" style="width: 100%"
! Partner Engine: Support server-driven setting of search defaults
 
|-
|
* '''ID:'''  [https://bugzilla.mozilla.org/show_bug.cgi?id=1169280 Bug 1169280]
* Asked for status on server side work - checking on other potentially required bugs.
<p> </p>
<bugzilla>
{
"f1":"blocked",
"o1":"equals",
"v1":"1169280",
"include_fields":"id, summary, status, assigned_to, cf_fx_points"
}
</bugzilla>
|}
<p> </p>
 
 
'''Details'''
* Biz dev project has taken priority.  Florian is 100% devoted to that work
* UX design for opt-in/opt-out is a priority (as Search Suggestions is disabled until this lands)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=1169280 Bug 959567[User Story] Implement search suggestions opt-in/out UI] is candidate for Aurora uplift if we don't get implemented in 41.3
*'''Unified Autocomplete''' bugs are being resolved (large project / several bugs)
**Will enable in Nightly in this iteration
<p> </p>
Collection of priority work the team has committed to complete on in a two-week iteration.
<p> </p>
*[https://wiki.mozilla.org/Firefox/searchandaddon#Key_Bugzilla_Queries view in Bugzilla]
 
<p> </p>
<bugzilla>
{
        "assigned_to": "dtownsend@mozilla.com, dao@mozilla.com, mak77@bonardo.net, mjaritz@mozilla.com, shorlander@mozilla.com, adw@mozilla.com, markh@mozilla.com, florian@queze.net",
        "include_fields":"id, summary, status, assigned_to, whiteboard, cf_fx_points",
        "cf_fx_iteration":"41.3 - Jun 29"
 
}
</bugzilla>
 
<p> </p>
 
 
<p> </p>
 
==Past==
===Iteration - 41.2, through June 8===
User Story this iteration: "As a user, when I enter text in the location bar, I will be presented with suggested search queries from the search default in the AwesomeBar dropdown that update as I continue to enter text to provide me with common queries related to the text I have entered."
 
No selection actions, no queries, just suggests being fetched from the provider and displayed in the AwesomeBar dropdown. We know that Unified Complete is a blocker, and as such wasn't positioned as a story, but some parts are required to complete the work to address the first story.
 
'''Details'''
* Still figuring out who is on which teams based on work load, so some flux.  will update before Stand-up.
* Folks finishing up work from existing projects in this iteration still, as developers free up moving onto highest priority work.
* UX for User Stories was taken and first User stories for '''Suggestions''' related to [https://docs.google.com/document/d/1de2o8Osl_z98BBfkt243i-dHdcKmQB15xJ9rShkwk3Q/edit top 3 users stories for search '''suggestions''']
**'''Unified Autocomplete''' bugs completing (large project) - bug to enable in Nightly in this iteration
* Live view into bugzilla for all contributors on Partner Search and tagged for Iteration 41.1
**Other [https://wiki.mozilla.org/Firefox/searchandaddon#Key_Bugzilla_Queries Key Bugzilla Queries are here]
 
<p> </p>
<bugzilla>
{
        "assigned_to": "dtownsend@mozilla.com, dao@mozilla.com, mak77@bonardo.net, mjaritz@mozilla.com, shorlander@mozilla.com, adw@mozilla.com, markh@mozilla.com, florian@queze.net",
        "include_fields":"id, summary, status, assigned_to, whiteboard, cf_fx_points",
        "cf_fx_iteration":"41.2 - Jun 8"
 
}
</bugzilla>
 
<p> </p>
 
 
<p> </p>
 
===Iteration - 41.1, through May 25===
User Story this iteration: "As a user, when I enter text in the location bar, I will be presented with suggested search queries from the search default in the AwesomeBar dropdown that update as I continue to enter text to provide me with common queries related to the text I have entered."
 
No selection actions, no queries, just suggests being fetched from the provider and displayed in the AwesomeBar dropdown. We know that Unified Complete is a blocker, and as such wasn't positioned as a story, but some parts are required to complete the work to address the first story.
 
'''Details'''
* Folks finishing up work from existing projects in this iteration still, as developers free up moving onto highest priority work.
* Started bugs related to [https://docs.google.com/document/d/1de2o8Osl_z98BBfkt243i-dHdcKmQB15xJ9rShkwk3Q/edit top 3 users stories for search '''suggestions''']
**'''Unified Autocomplete''' bugs that are blocking Search Suggestions are under [https://bugzilla.mozilla.org/show_bug.cgi?id=1157952 bug 1157952] for this iteration
*Search hijacking is work that wasn't a newly started Theme, but was under progress and bugs are being taken from that area.
* Live view into bugzilla for all contributors on Partner Search and tagged for Iteration 41.1
**Other [https://wiki.mozilla.org/Firefox/searchandaddon#Key_Bugzilla_Queries Key Bugzilla Queries are here]
 
<p> </p>
<bugzilla>
{
        "assigned_to": "dtownsend@mozilla.com, dao@mozilla.com, mak77@bonardo.net, mjaritz@mozilla.com, shorlander@mozilla.com, adw@mozilla.com, markh@mozilla.com, florian@queze.net",
        "include_fields":"id, summary, status, assigned_to, whiteboard, cf_fx_points",
        "cf_fx_iteration":"41.1 - May 25"
 
}
</bugzilla>
 
<p> </p>
 
 
<p> </p>
 
 
===Iteration - 40.3 through May 11===
* Focus on folks [http://tinyurl.com/m7kz29w wrapping up bugs carried over from previous projects in addition to taking on new work as free up].
* '''Search Suggestions''' will be the first feature focus for this team
* '''Search Suggestions''' will be the first feature focus for this team
**As a team we reviewed the working [https://docs.google.com/document/d/1de2o8Osl_z98BBfkt243i-dHdcKmQB15xJ9rShkwk3Q/edit User Story document]
**As a team we reviewed the working [https://docs.google.com/document/d/1de2o8Osl_z98BBfkt243i-dHdcKmQB15xJ9rShkwk3Q/edit User Story document]
Line 85: Line 233:
<bugzilla>
<bugzilla>
{
{
         "assigned_to": "dtownsend@mozilla.com, dao@mozilla.com, mak77@bonardo.net, mjaritz@mozilla.com, shorlander@mozilla.com, adw@mozilla.com, mhammond@mozilla.com",
         "assigned_to": "dtownsend@mozilla.com, dao@mozilla.com, mak77@bonardo.net, mjaritz@mozilla.com, shorlander@mozilla.com, adw@mozilla.com, markh@mozilla.com",
         "include_fields":"id, summary, status, assigned_to, cf_fx_points",
         "include_fields":"id, summary, status, assigned_to, cf_fx_points",
         "cf_fx_iteration":"40.3 - 11 May"
         "cf_fx_iteration":"40.3 - 11 May"
Line 97: Line 245:
<p> </p>
<p> </p>


==Past==
 
===Iteration - 40.2 April 27===
===Iteration - 40.2 April 27===
*Normally there would be a summary of features worked on / progress / blockers
*Normally there would be a summary of features worked on / progress / blockers
Line 109: Line 257:
* Improve visibility so that the stakeholders make the best decisions about the direction of the product (call out risks early, relative priorities, trade-offs)
* Improve visibility so that the stakeholders make the best decisions about the direction of the product (call out risks early, relative priorities, trade-offs)
<p> </p>
<p> </p>
<p> </p>
==Key Bugzilla Queries==
* '''Team Product Backlog:'''  [http://mzl.la/1EjFTk8 Bugs marked Firefox-backlog+ and [fxsearch]]
**Add the "Rank" Column to your results and sort on Rank (option to "Change columns" is at bottom of search results)
*'''Bugs Pulled Current Iteration:'''[http://tinyurl.com/ppcdd7f Bugs in the Backlog with a current iteration tag]
**for  Assignee: dtownsend@mozilla.com, dao@mozilla.com, mak77@bonardo.net, mjaritz@mozilla.com, shorlander@mozilla.com, adw@mozilla.com, mhammond@mozilla.com
*'''Untriaged Bugs marked Firefox-backlog+:''' [http://tinyurl.com/nnlffev Bugs marked Firefox-backlog+ without [fxsearch]] in the Whiteboard under Search
*'''Untriaged Bugs:'''[http://tinyurl.com/naufrjz Bugs NOT marked Firefox-backlog+ without [fxsearch]] in whiteboard under Search
<p> </p>
<p> </p>


Line 162: Line 302:
*for company goal x, we are in _____ state because ______.  Please consider ______(propose fix or adjustment of goal).
*for company goal x, we are in _____ state because ______.  Please consider ______(propose fix or adjustment of goal).
*for release goal for ______ ,  we are in _____ state because ______.  Please consider ______(propose fix or adjustment of goal).
*for release goal for ______ ,  we are in _____ state because ______.  Please consider ______(propose fix or adjustment of goal).
==Project Introduction==
* '''Team Mailing list:''' if applicable
* '''Team IRC Channel:''' where does this team "hang-out"
*[https://wiki.mozilla.org/Firefox/IterativeDevelopment Summary of our plans for this year]
**links back to main Firefox page - Marco to create a section on main page for team summaries. 
**Quick high-level plans for the year for Desktop management and contributors. Likely completed by Kev/Dave with EPM help as needed.
***Here's an example of the overview from [https://wiki.mozilla.org/Platform/Roadmap#WebRTC_.2F_WebAudio Platform team for webRTC]
* '''Dependencies:''' feature, partner, resource, etc. that impact this projects ability to succeed - put links to other project pages.
==Links to Current info==
The [https://wiki.mozilla.org/Firefox/searchandaddon/links Links wiki page] is the central location for current focus, Roadmap, Metrics, UX, Marketing, tech-architecture, and more.
==Roles and Responsibilities==
The [https://wiki.mozilla.org/Firefox/Contacts Contacts Page] has the Roles and Responsibilities for Firefox teams, partner teams, and external partners.
Sescalante
Confirmed users
1,094

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1072058...1133043"