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