← Back to team overview

launchpad-dev team mailing list archive

[tech] Technical Architect Team Meeting Guidelines

 

Hi,

We discussed earlier about how the Technical Architect team should
discuss and coordinate things, and decided to try out an e-mail based
approach.

In short, e-mails with a subject tag of [tech], are topics that the team
should pay extra attention too. I've written up some guidelines here:

    https://dev.launchpad.net/TechnicalArchitect/Team

The most important things are to keep discussions short (switch to phone
early), and to at the very least reply privately to me, confirming that
you've read the topic. The latter is like the roll-call in a traditional
meeting, to show that you don't ignore the mails.

Expect a [tech] mail shortly.

For simplicity, here's a copy of the section from the wiki page:


== Meeting Guidelines ==

The team doesn't have scheduled meetings. Instead discussion and
coordination happen on the `launchpad-dev` mailing list, and through
phone calls.

When a topic is meant for the team, the e-mail subject has a `[tech]`
tag.  Members of the team should pay special attention to such mail, and
'''should reply promptly, even if it's just to say that they have no
comments.''' It's important to answer, to acknowledge that you have read
the mail. If all you want to do is to acknowledge, reply directly to the
Technical Architect, to reduce noise on the list.

E-mail discussion tend to be long-drawn and have high latency. To try to
avoid this, please consider the following tips:

    * If the discussion has already gone on too long, or you feel that a
      subject will need a lot of discussion (more than 1-2 e-mails),
      '''arrange a phone call with interested parties''', and report back
      with the outcome of the discussion.

    * '''Predict which questions other people will ask you when reading
       your mail.''' Try to answer the questions before they are asked.

    * '''When asking questions, predict which follow-up questions you
      might ask when you get your answer.''' Ask these questions directly,
      together with the first question.




-- 
Björn Tillenius | https://launchpad.net/~bjornt