<div dir="ltr">+1 for 2017 planning<br><div>+100 for fun in the sun :)<br></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 11:47 AM, 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 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>
</span>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>
<span class=""><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>
> <a href="tel:%28415%29%20769-9247" value="+14157699247">(415) 769-9247</a><br>
> IRC & Slack: adavis<br>
><br>
> On Mon, Nov 21, 2016 at 10:01 AM, Shane Tomlinson<br>
</span><div><div class="h5">> <<a href="mailto:stomlinson@mozilla.com">stomlinson@mozilla.com</a> <mailto:<a href="mailto:stomlinson@mozilla.com">stomlinson@mozilla.com</a><wbr>>> wrote:<br>
><br>
> Following on from this conversation, albeit somewhat tangential to<br>
> "shippable" work.<br>
><br>
> One thing I'm interested in learning more about is how other people<br>
> work and what<br>
> tools and hacks they use to boost productivity. For example, I've<br>
> been using vim for years,<br>
> the key sequences I use all the time are burned into my brain, and I<br>
> get frustrated when<br>
> going to a machine that doesn't have all the same keys mapped and<br>
> plugins. I've been<br>
> using Atom for the last week to see whether it can make certain<br>
> things easier, and<br>
> unsurprisingly, it does. I see Vlad and Vijay use WebStorm, and I'm<br>
> sure it has<br>
> some awesomeness too. Another example is both Phil and I use iTerm,<br>
> a couple<br>
> of months ago Phil showed me a "replay" feature that re-runs the<br>
> command line<br>
> history - my head exploded. jrgm pulls out bash foo all the time<br>
> that I'm just like<br>
> "whaaa? That's possible?". Each time I see things like 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>
</div></div>> * 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>
<span class="">><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><br>
</span><span class="">> <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>
</span>> * OKR #3: Reduce likelihood of user losing Sync data<br>
<span class="">><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>
</span>> * Get Feeley's proposed reversed sign-up flow up and running<br>
<span class="">> and ready to A/B test.<br>
><br>
</span>> * Phase 3-4 of email confirmation flow that we worked on in<br>
<span class="">> Toronto<br>
><br>
><br>
><br>
> Just throwing those out there...<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:%28415%29%20769-9247><br>
<span class="">> IRC & Slack: adavis<br>
><br>
> On Thu, Nov 17, 2016 at 3:37 PM, Shane Tomlinson<br>
</span><span class="">> <<a href="mailto:stomlinson@mozilla.com">stomlinson@mozilla.com</a> <mailto:<a href="mailto:stomlinson@mozilla.com">stomlinson@mozilla.com</a><wbr>>> 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>
</span><span class="">> <<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>
</span><span class="">> <<a href="mailto:vbudhram@mozilla.com">vbudhram@mozilla.com</a> <mailto:<a href="mailto:vbudhram@mozilla.com">vbudhram@mozilla.com</a>>> 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><br>
</span><span class="">> <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><br>
</span>> <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>
<span class="">> <<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>
</span>> <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>
<span class="">> <<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>
</span>> <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>
<span class="">> <<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>
</span>> <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>
<div class="HOEnZb"><div class="h5">> <<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><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><br>
<a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/dev-fxacct</a><br>
</div></div></blockquote></div><br></div>