canonical-ci-engineering team mailing list archive

[Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx>]

I've been looking for a good way to keep track of the actions that we
agree to on the back of the 1:1 calls and I've come back to Asana
after James Troup showed me how effective it has been in IS.

I could set up some blueprints for this sort of thing, but there are a
few problems with that approach:
- Tracking private tasks has to happen in a separate place.
- No time-based deadlines.
- No priorities.
- The list either grows large or we sacrifice history. There's no
separate archive of completed tasks.
- Noisy. Unless I create a blueprint per-person, you'll see updates
for everyone when you may not want that.

Asana has some additional benefits over blueprints for this:
- Tight Google Docs integration.
- You can comment on tasks (maybe the task isn't clear?).
- You can nest tasks.
- You can follow individual tasks (when you're waiting on someone to
complete a task before you can get started).
- Reminders when deadlines are coming up or you have overdue items.
- Very easy to factor out additional projects or further divide a
project by sections other than milestones.
- You can easily follow and unfollow (by email) projects as needed.
- Slick burndown charting:
https://burndown.admin.canonical.com/isp-charts.html :)

We should still use blueprints to track projects that come out of UDS for 14.04.

I've sent you all invites, so you should have access to the Ubuntu CI
team. If you want to factor out some additional projects (when you
have a small project you're working on with a few of your peers) or
use it to track your personal work, do feel free.

If you have any questions, please do follow up.

Thanks,
Ev