canonical-ci-engineering team mailing list archive

[Andy Doan <andy.doan@xxxxxxxxxxxxx>]

On 05/13/2014 06:16 AM, Evan Dandrea wrote:

> I've created a document for us to set goals and flag any needed discussions:
>
> https://docs.google.com/a/canonical.com/document/d/1Y64OIeCtPi_j1mPLUYJjT7UnKNqL-n1tG09Tao_dm34/edit

We have a nice list going, but I was wondering if we shouldn't try to 
nail down some times to work on these goals. I usually resist attempts 
at organization, so maybe this a bad idea :) But I thought if we put 
this down, we could make sure we'd have the proper time for group 
hacking activities.

These things seem to have mornings spent doing more team-wide type 
discussions and hangover recovery. While afternoons could be mostly 
focused on completing real goals. Here's a straw-man proposal I was 
thinking about adding to this document to cover some stuff I had in mind:

= Monday Afternoon Hacking:

  doanac/plars/psivva - x86 emulator in daily image testing

= Tuesday Afternoon Hacking:

  doanac/josepht - live status on webui
  doanac - see if ogra/sergio want to talk about phablet-tools

= Wednesday Afternoon Hacking:

  doanac/fginther - ticket pause/continue support

= Thursday Afternoon Hacking:

  doanac/cprov - charm hacking for prodstack?

What do you guys think? Is it worth moving into the document and organizing?