<div dir="ltr"><div><div><div><div>Hey gang,<br><br></div>Summary of our discussions:<br><br></div><u><b>Tuesday</b> </u><br><b>AM</b>: <br>All hands - Plenary session<br></div><b>PM</b>: <br>Fx Plenary session<br></div>Team time<br><div><br></div><div><u><b>Wednesday<br></b></u></div><div><b>AM:</b><br></div><div>2017 Planning<br></div><div>11:30am - Karlof org 2017 planning<br></div><div><b>PM:<br></b></div><div>nothing planned as of now<br><br></div><div><u><b>Thursday<br></b></u></div><div><b>AM:<br></b></div><div>Possible talks with QA<br></div><div><b>PM:<br></b></div><div>Continuous deployment discussions?<br></div><div>3pm - adavis and cmore elective ;)<br><br></div><div><u><b>Friday<br></b></u></div><div>How to minimize password resets? Approximately 7% of login attempts results in a password reset. <br>Goals: 1- Avoid data loss 2- Make adding another device easier 3- Improve UX 4- Could maybe help regain access to an account?<br></div><div><u><b><br></b></u></div><div><b></b></div><div><b></b></div><div><u><b></b></u></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div></div><div>--<br>Alex Davis <span>// Mountain View</span></div><div>Product Manager // FxA & Sync<br></div>(415) 769-9247</div><span></span></div><div>IRC & Slack: adavis<br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Nov 22, 2016 at 8:04 PM, Ryan Kelly <span dir="ltr"><<a href="mailto:rfkelly@mozilla.com" target="_blank">rfkelly@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 23/11/16 09:23, Sean McArthur wrote:<br>
> Much of that all sounds great to me! Should we add these things to the<br>
> FxA schedule in sched? It looks like most other teams in the Firefox<br>
> org[1] have sub-tags, I'm not sure what it takes to get<br>
> <a href="https://hawaiiallhands2016.sched.org/overview/type/Firefox/Accounts" rel="noreferrer" target="_blank">https://hawaiiallhands2016.<wbr>sched.org/overview/type/<wbr>Firefox/Accounts</a><br>
<br>
</span>I'd like to, but it's not obvious to me whether we can just add events<br>
to that thing ourselves, or if it's populated based on room reservations<br>
for the week (which we won't be able to get, because there's no free rooms).<br>
<br>
In any case, taking a look at the sched, here's the broader shape of the<br>
week that we need to fit in around:<br>
<br>
* Tuesday: plenary in the morning, firefox all-hands in the afternoon,<br>
a couple of free hours from 2-5pm.<br>
<br>
* Wednesday: ckarlof org 2017 from 11:30 to lunch, electives from 3pm,<br>
so no really large chunks of free space.<br>
<br>
* Thursday: nothing scheduled for the morning, electives from 3pm<br>
<br>
* Friday: free team time for the whole day!<br>
<br>
<br>
So my suggestion for a high-level schedule would be:<br>
<br>
* Tuesday afternoon seems like a good opportunity to go do something<br>
fun as a team and just enjoy being all together. The afternoon<br>
backs on to free-form Resort Dining time so we could also go to<br>
dinner together somewhere nearby.<br>
<br>
* Wednesday morning is a good opportunity for 2017 planning and<br>
vision-setting, both as a team before-hand, and at the larger<br>
session with the rest of :ckarlof's org. We can pitch ideas and<br>
haggle about OKRs and other fun stuff like that.<br>
<br>
* That leaves big chunks of time free on Thursday and Friday for<br>
hacking sessions or smaller group sessions as mentioned in this<br>
thread. The downside though being that we might be exhausted by<br>
the time that rolls around...and might need another out-and-about<br>
activity on the Friday afternoon :-P<br>
<br>
Thoughts?<br>
<br>
<br>
Ryan<br>
<span class=""><br>
> On Tue, Nov 22, 2016 at 1:13 PM Alex Davis <<a href="mailto:adavis@mozilla.com">adavis@mozilla.com</a><br>
</span><span class="">> <mailto:<a href="mailto:adavis@mozilla.com">adavis@mozilla.com</a>>> wrote:<br>
><br>
> +1 for 2017 planning<br>
> +100 for fun in the sun :)<br>
><br>
> --<br>
> Alex Davis // Mountain View<br>
> Product Manager // FxA & Sync<br>
</span>> <a href="tel:%28415%29%20769-9247" value="+14157699247">(415) 769-9247</a> <tel:(415)%20769-9247><br>
<span class="">> IRC & Slack: adavis<br>
><br>
> On Tue, Nov 22, 2016 at 11:47 AM, Ryan Kelly <<a href="mailto:rfkelly@mozilla.com">rfkelly@mozilla.com</a><br>
</span><div><div class="h5">> <mailto:<a href="mailto:rfkelly@mozilla.com">rfkelly@mozilla.com</a>>> wrote:<br>
><br>
> On 23/11/16 06:42, Alex Davis wrote:<br>
> > I propose we make a schedule so we can do a few different things. I<br>
> > don't think we need to limit ourselves. Many things can benefit from the<br>
> > team getting together.<br>
> ><br>
> > Here are proposed ideas I suggest we dedicate time to since we can get a<br>
> > lot of value discussing them as a team:<br>
> > - tools and hacks to boost productivity (suggested by Shane) - maybe a<br>
> > half day<br>
> > - meeting with the QA team that will help us moving forward (discuss<br>
> > process with them) - only 1-2 hrs<br>
> > - tackle data loss via password reset (OKR #3) ... might be worth<br>
> > including Sync team on this one - maybe a full day<br>
> ><br>
> > Also maybe worth exploring/discussing:<br>
> > - release cycle speed<br>
><br>
> Two other topics I think we should fit into the schedule:<br>
><br>
> * 2017 and our plans for it; big-picture thinking type stuff.<br>
><br>
> * (as Shane reminded me just now) Something fun and outdoors<br>
> in the sunshine :-)<br>
><br>
><br>
> Cheers,<br>
><br>
> Ryan<br>
><br>
> > As per catching up on technical debt, I'm not sure if there is any<br>
> > benefit in doing it together. (correct me if I am wrong) In yesterday's<br>
> > retrospective, it was proposed to take time every week for this<br>
> > (Fridays). This makes more sense to me. I think it's something we should<br>
> > do regularly and not just as a one off.<br>
> ><br>
> > Thoughts?<br>
> ><br>
> ><br>
> > --<br>
> > Alex Davis // Mountain View<br>
> > Product Manager // FxA & Sync<br>
</div></div><span class="">> > <a href="tel:%28415%29%20769-9247" value="+14157699247">(415) 769-9247</a> <tel:%28415%29%20769-9247><br>
> > IRC & Slack: adavis<br>
> ><br>
</span><span class="">> > On Mon, Nov 21, 2016 at 10:01 AM, Shane Tomlinson<br>
> > <<a href="mailto:stomlinson@mozilla.com">stomlinson@mozilla.com</a> <mailto:<a href="mailto:stomlinson@mozilla.com">stomlinson@mozilla.com</a><wbr>><br>
</span>> <mailto:<a href="mailto:stomlinson@mozilla.com">stomlinson@mozilla.com</a> <mailto:<a href="mailto:stomlinson@mozilla.com">stomlinson@mozilla.com</a><wbr>>>><br>
<div><div class="h5">> wrote:<br>
> ><br>
> > Following on from this conversation, albeit somewhat<br>
> tangential to<br>
> > "shippable" work.<br>
> ><br>
> > One thing I'm interested in learning more about is how<br>
> other people<br>
> > work and what<br>
> > tools and hacks they use to boost productivity. For<br>
> example, I've<br>
> > been using vim for years,<br>
> > the key sequences I use all the time are burned into my<br>
> brain, and I<br>
> > get frustrated when<br>
> > going to a machine that doesn't have all the same keys<br>
> mapped and<br>
> > plugins. I've been<br>
> > using Atom for the last week to see whether it can make<br>
> certain<br>
> > things easier, and<br>
> > unsurprisingly, it does. I see Vlad and Vijay use<br>
> WebStorm, and I'm<br>
> > sure it has<br>
> > some awesomeness too. Another example is both Phil and I<br>
> use iTerm,<br>
> > a couple<br>
> > of months ago Phil showed me a "replay" feature that<br>
> re-runs the<br>
> > command line<br>
> > history - my head exploded. jrgm pulls out bash foo all<br>
> the time<br>
> > that I'm just like<br>
> > "whaaa? That's possible?". Each time I see things like<br>
> these, I feel<br>
> > like I'm<br>
> > slightly more productive.<br>
> ><br>
> > What other secrets do people have that could make others more<br>
> > productive?<br>
> ><br>
> > Things I'm personally interested in:<br>
> ><br>
> > * Keeping up with the Mozilla Firehose.<br>
> > * Speeding up the dev cycle.<br>
> > * Editors and what they provide.<br>
> > o vim shortcuts, plugins.<br>
> > * Searching/finding snippets.<br>
> > * Writing tests to be more reliable.<br>
> > * Anything related to git.<br>
> > * Searching server logs for problems.<br>
> ><br>
> > What can I show? I dunno what's worthwhile to others, is there anything<br>
> > others wonder how their teammates approach?<br>
> ><br>
> > We might not need a full-on session for this, but if anybody has<br>
> > anything they wouldn't<br>
> > mind showing off, you have an audience of at least 1.<br>
> ><br>
> > Shane<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > On Fri, Nov 18, 2016 at 2:40 AM, Alex Davis <<a href="mailto:adavis@mozilla.com">adavis@mozilla.com</a> <mailto:<a href="mailto:adavis@mozilla.com">adavis@mozilla.com</a>><br>
</div></div><div><div class="h5">> > <mailto:<a href="mailto:adavis@mozilla.com">adavis@mozilla.com</a> <mailto:<a href="mailto:adavis@mozilla.com">adavis@mozilla.com</a>>>> wrote:<br>
> ><br>
> > Following up on what Ryan and Shane said...<br>
> > Here are a couple of things that might be nice to work on with<br>
> > Feeley (if he is around) since it could really help to have<br>
> > engineering, product and UX putting their brains together at the<br>
> > same time:<br>
> ><br>
> > * OKR #3: Reduce likelihood of user losing Sync data<br>
> ><br>
> > KR<br>
> ><br>
> ><br>
> ><br>
> > Rating<br>
> ><br>
> > Establish metrics and dashboard for measuring when users lose<br>
> > their data.<br>
> ><br>
> ><br>
> ><br>
> > Reduce voluntary password resets by 20%. 7% → 5.4%<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > This one seems particularly hard since the challenge of<br>
> > balancing good UX and solid security is a tremendous challenge.<br>
> ><br>
> > * Get Feeley's proposed reversed sign-up flow up and<br>
> running<br>
> > and ready to A/B test.<br>
> ><br>
> > * Phase 3-4 of email confirmation flow that we<br>
> worked on in<br>
> > Toronto<br>
> ><br>
> ><br>
> ><br>
> > Just throwing those out there...<br>
> ><br>
> > --<br>
> > Alex Davis // Mountain View<br>
> > Product Manager // FxA & Sync<br>
> > <a href="tel:%28415%29%20769-9247" value="+14157699247">(415) 769-9247</a> <tel:%28415%29%20769-9247><br>
> <tel:%28415%29%20769-9247><br>
> > IRC & Slack: adavis<br>
> ><br>
> > On Thu, Nov 17, 2016 at 3:37 PM, Shane Tomlinson<br>
> > <<a href="mailto:stomlinson@mozilla.com">stomlinson@mozilla.com</a> <mailto:<a href="mailto:stomlinson@mozilla.com">stomlinson@mozilla.com</a><wbr>><br>
</div></div>> <mailto:<a href="mailto:stomlinson@mozilla.com">stomlinson@mozilla.com</a> <mailto:<a href="mailto:stomlinson@mozilla.com">stomlinson@mozilla.com</a><wbr>>>><br>
<span class="">> wrote:<br>
> ><br>
> > I have a not-so-secret-secret (as in, it's not secret at<br>
> > all, I talk about it regularly). I take a little bit of time<br>
> > every train to pay down technical debt and only rarely do I<br>
> > feel that time could be better spent elsewhere. FxA is 3<br>
> > years old now and has tons of little niggles. Those little<br>
> > niggles can seem like a big burden, so it's nice to get rid<br>
> > of them.<br>
> ><br>
> > I find paying down debt helps to keep me engaged - sometimes<br>
> > a small win is all that's needed to brighten an otherwise<br>
> > difficult day. I take pride in the code and enjoy making it<br>
> > better, it has become a regular process.<br>
> ><br>
> > My idea for maximizing Hawaii is to work on things that are<br>
> > easier to coordinate when others are in the room. If an item<br>
> > of debt meets that criteria, then yeah, perfect. The way my<br>
> > quarter is shaping up, I have a feeling I'm going to be<br>
> > bugging people mostly for "connect another device" and<br>
> > related tasks.<br>
> ><br>
> > Shane<br>
> ><br>
> ><br>
> > On Thu, Nov 17, 2016 at 3:34 PM, Phil Booth<br>
> > <<a href="mailto:pbooth@mozilla.com">pbooth@mozilla.com</a> <mailto:<a href="mailto:pbooth@mozilla.com">pbooth@mozilla.com</a>><br>
</span><span class="">> <mailto:<a href="mailto:pbooth@mozilla.com">pbooth@mozilla.com</a> <mailto:<a href="mailto:pbooth@mozilla.com">pbooth@mozilla.com</a>>>> wrote:<br>
> ><br>
> > Oh Vijay, that's a great shout!<br>
> ><br>
> > I have so many open quality issues on the back-burner,<br>
> > which I never seem to make time for but really want to<br>
> > work on. Maybe I'm just bad at prioritising stuff but<br>
> > having some official technical-debt time would be<br>
> > brilliant I reckon.<br>
> ><br>
> > +1<br>
> ><br>
> ><br>
> > On Thu, Nov 17, 2016 at 3:04 PM, Vijay Budhram<br>
> > <<a href="mailto:vbudhram@mozilla.com">vbudhram@mozilla.com</a> <mailto:<a href="mailto:vbudhram@mozilla.com">vbudhram@mozilla.com</a>><br>
</span><span class="">> <mailto:<a href="mailto:vbudhram@mozilla.com">vbudhram@mozilla.com</a> <mailto:<a href="mailto:vbudhram@mozilla.com">vbudhram@mozilla.com</a>>><wbr>> wrote:<br>
> ><br>
> > I think having a focused 2-day hack sprint would be<br>
> > great. However, I have a counter proposal.<br>
> ><br>
> > > What should we try to do<br>
> ><br>
> > I think it would be cool to help reduce some of the<br>
> > technical debt that has accumulated. These are<br>
> > things that we normally don't get to make explicit<br>
> > time for but would make our lives better in the long<br>
> > run.<br>
> ><br>
> > 1) More stable testing environments<br>
> > 2) Faster functional tests<br>
> > 3) Migrate projects to Yarn?<br>
> > 4) Build trigger to test entire stack against<br>
> > specific commit in any project<br>
> ><br>
> > I'm sure there are more things that could be added<br>
> > but that is off the top of my head.<br>
> ><br>
> ><br>
> > On Wed, Nov 16, 2016 at 7:56 PM, Sean McArthur<br>
> > <<a href="mailto:smcarthur@mozilla.com">smcarthur@mozilla.com</a> <mailto:<a href="mailto:smcarthur@mozilla.com">smcarthur@mozilla.com</a>><br>
</span><span class="">> > <mailto:<a href="mailto:smcarthur@mozilla.com">smcarthur@mozilla.com</a> <mailto:<a href="mailto:smcarthur@mozilla.com">smcarthur@mozilla.com</a>><wbr>>> wrote:<br>
> ><br>
> > The Hawaii work week is only 3 weeks away! We're<br>
> > starting to see more and more that can be part<br>
> > of our schedule, and we could try to plan<br>
> > something FxA-related that we want to get done<br>
> > that week. With travel days, plenary and other<br>
> > required bigger-org meetings, we could have<br>
> > around 2.5 days to be together and get something<br>
> > done.<br>
> ><br>
> > Would you all be interested in planning some<br>
> > sort of sprint thingy, similar to what happened<br>
> > in Toronto? Maybe we can plan a 2-day hack<br>
> > sprint where on Friday afternoon we can show off<br>
> > a working thing-a-ma-jig.<br>
> ><br>
> > What should we try to do? Should we continue on<br>
> > the idea that was brainstormed in Toronto? Or is<br>
> > there some other small experiment someone has<br>
> > wished we could just make happen with some<br>
> > concentrated effort?<br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > Dev-fxacct mailing list<br>
> > <a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><wbr>><br>
</span>> > <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><br>
<span class="">> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><wbr>>><br>
> ><br>
> <a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/dev-fxacct</a><br>
> > <<a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/dev-fxacct</a>><br>
> ><br>
> ><br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > Dev-fxacct mailing list<br>
> > <a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><br>
</span>> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><wbr>> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><br>
<span class="">> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><wbr>>><br>
> > <a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/dev-fxacct</a><br>
> > <<a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/dev-fxacct</a>><br>
> ><br>
> ><br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > Dev-fxacct mailing list<br>
> > <a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><br>
</span>> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><wbr>> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><br>
<span class="">> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><wbr>>><br>
> > <a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/dev-fxacct</a><br>
> > <<a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/dev-fxacct</a>><br>
> ><br>
> ><br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > Dev-fxacct mailing list<br>
> > <a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><br>
</span>> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><wbr>> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><br>
<div class="HOEnZb"><div class="h5">> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><wbr>>><br>
> > <a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/dev-fxacct</a><br>
> > <<a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/dev-fxacct</a>><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > Dev-fxacct mailing list<br>
> > <a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><wbr>><br>
> > <a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/dev-fxacct</a><br>
> ><br>
> ______________________________<wbr>_________________<br>
> Dev-fxacct mailing list<br>
> <a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><wbr>><br>
> <a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/dev-fxacct</a><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Dev-fxacct mailing list<br>
> <a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a> <mailto:<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><wbr>><br>
> <a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/dev-fxacct</a><br>
><br>
</div></div></blockquote></div><br></div>