I like the idea of making space to pay down technical debt.  But I also
want to make sure that we're taking advantage of the together-time to
work on things that we couldn't do effectively while scattered around
the globe.

Do we have any technical-debt items that would really benefit from some
close synchronous collaboration?


  Ryan


On 18/11/16 02:34, Phil Booth 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]>> 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]>> 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]>
>         https://mail.mozilla.org/listinfo/dev-fxacct
>         <https://mail.mozilla.org/listinfo/dev-fxacct>
> 
> 
> 
>     _______________________________________________
>     Dev-fxacct mailing list
>     [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
> 
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct

Reply via email to