← Back to team overview

canonical-ci-engineering team mailing list archive

Moved Monday's team meeting to Tuesday and some thoughts on CI Airline

 

Hi everyone,

I've moved next week's Monday standup to Tuesday. My flight back to
London lands at 2pm, and I doubt I'll even make it out of the airport
in the 30 minutes I'd have before the meeting. Sorry if this ends up
inconveniencing you.

I've also booked some time once we're done going through our activity
reports to continue the discussion around the CI Airline:

https://docs.google.com/a/canonical.com/presentation/d/1Ehcw8lfoMM7R69BiIgeCft2jstX5ua786Q1HMslhhUI/edit

Start giving the airline some thought this weekend as you're driving
around town or standing in line at the grocery:

- What are the microservices going to be in this SOA?
- What are the APIs?
- What is going to fall over?
- What do we measure to know we're on the right path?

Obviously none of us have the full picture yet, but the pieces should
start forming in our heads more and more so we know what needs to be
done. Start thinking about where you can make the most effective
contribution.

We're going to work as a team, obviously. You guys really impressed me
at the sprint with how well you build off each other, and I'm super
excited for that to continue. I'll assign ownership of leading
individual pieces to completion though, even as we get our hands dirty
across all parts.

I want you to feel like you own this, that what we build is not only
something you can be really proud of, but something that is truly
constructed with your ideas. Tweak the design, shape it from your own
experiences and learnings. Bring some new, clever ideas to the table.
Get excited and get engaged.

I get the impression from my conversations with some of you that
you're chomping at the bit to do big things and you see real
opportunity in this idea. I'll clear the path so you guys can build
the most rock-solid and game-changing CI story. The whole of Ubuntu
Engineering is relying on us to give them the clearest, fastest path
to getting software ready for and into Ubuntu.

Finally and most importantly, start thinking of a code name. :)

As always, if you have questions, I'm only a Google Hangout away. If
you're worried about the amount of work on your plate, come talk to
me. We'll work through what you have and descope until you're back to
safety.

Thanks. I couldn't be more excited to start down this road together.


Follow ups