Test Pilot/Meeting/2017-05-22
From MozillaWiki
< Test Pilot | Meeting
Contents
General Topics / Roundtable
(Want to share a useful library? Blocked on something? Wondering how other experiment teams do something?)
- Chuck is presenting a workshop on contributing to open source in June, and will be using the various Test Pilot experiments as fodder for attendees to make their first contributions.
- He’s made an assistant site to contain the presentation content and provide some bugs for attendees to work on during the workshop: https://good-first-bug.herokuapp.com/ (needs Chrome for now)
- (Firefox bug, where fetch fails if the preflight request returns a 204)
- It uses GitHub issue tags to aggregate issues, and will be filterable by project and skills required to complete.
- Calls for action:
- Go through your projects’ backlogs and label each appropriate bug with the label `good first bug`.
- File new bugs for these contributors. There’s likely going to be a wide variety of skill levels at the workshop, so even bugs to fix typos in documentation are very welcome.
- Ensure that each issue with the label `good first bug` has one or more corresponding skill tags to indicate the expertise necessary to contribute. The current list, which I’m happy to expand if there are specific needs.
- skill:html
- skill:css
- skill:js
- skill:react
- skill:documentation
- Skill:webextensions
- Code: https://github.com/chuckharmston/good-first-bug
- He’s made an assistant site to contain the presentation content and provide some bugs for attendees to work on during the workshop: https://good-first-bug.herokuapp.com/ (needs Chrome for now)
- Luke has a branch that makes the testpilot-containers repo “build-able” as a Test Pilot add-on or a Shield add-on.
Friends of the Test Pilot team
(Give a shoutout/thanks to people for helping fix and test bugs in Test Pilot or experiments. Introductions for new contributors)
- No volunteer contributions in the past two weeks ;_; *snif*
Project Updates
(Product, engineering, & community updates. For more ideas, see the meeting proposal doc.)
Test Pilot
(includes eng, UX, user research, product)
- We are having a blog! Discourse thread RE: topics
- Standards proposal for embedding feedback directly into experiments
- Planning for post-SDK
- Expose Test Pilot as a webextension experiments API
- https://github.com/mozilla/testpilot/issues/2396
Add-ons
- Perf work (with the goal of enabling the WE version of screenshots) continues, see [bug 1363905 https://bugzil.la/1363905]
Activity Stream
Cliqz
Containers
- 2.3.0 releasing this week: drops as much SDK code as possible and adds a “site assignment” on-boarding panel to increase site assignments, which we know improves feature engagement
Hoverpad
Min Vid
- New milestone for replacing the SDK https://github.com/meandavejustice/min-vid/milestone/7
Pulse
- Currently more-or-less feature complete, in a holding pattern while data is being collected.
- Numbers are currently projecting to fall short of KR. Any suggestions for novel ways to market it or increase engagement are welcome.
- Not sure there’s a meaningful difference between 50k reports (projected) and 100k reports (KR).
- Could be that we’re at a natural cap, given the nature of the experiment.
- Will be graduated this summer, with two blog posts:
- Learnings as they relate to Firefox dev (Test Pilot blog)
- Learnings for web developers (probably on Hacks?)
Screenshots
- Slipped from 54 due to late-breaking performance concerns about startup time
- Addons team is working to get WebExtension code fast enough at startup
- Screenshots team is also working on a backup plan for 55:
- move the context menu and toolbar button code into bootstrap.js
- lazily init the WebExtension code only after the first click
