launchpad-dev team mailing list archive

[Robert Collins <robert.collins@xxxxxxxxxxxxx>]

So at the Epic I proposed some architectural values that I hope will
help us reach some goals for the system. This wiki page:
https://dev.launchpad.net/ArchitectureGuide lays those goals, values
and draft metrics out.

Our review team is very good at having sensible discussions about all
the code that comes into the system, and I've asked (via the normal
process for review changes) that they start including in those
discussions questions/comments about those values and metrics on the
ArchitectureGuide page.

There will be specific things like ('does this page/API do more
queries as it gets more data') which we may want to accumulate as
things-to-look for - please put them on *their* relevant wiki page
(e.g. for the example I gave, dev.launchpad.net/Database/Performance
might be a sensible place, or just /Performance).

The goal I have here is to provoke *discussion and analysis*, so that
our shared body of knowledge for delivering a fast, robust & flexible
product increases in the areas I've highlighted on the
ArchitectureGuide page, which were not previously covered at all. We
all own the guide, so like the rest of the wiki, this is a living
page: please dive in and improve it.

I'm totally sure the metrics I'm suggesting are noddy and
dialed-wrongly : lets fix those as we go, or perhaps even take them
out. Though I think it is nice to a ballpark figure to aim for for
things, just to prompt one to think about the issues.

I'm going to follow up in the review meetings over the next few weeks
to see how reviewers are finding these discussions, and how its
working for everyone.

In short, I'd love it if you can:
 - Please read the ArchitectureGuide. It contains useful stuff. In a
very broad sense, follow its recommendations/request or fix it if its
wrong.
 - I believe that doing this will help us all have a better product in
a very significant fashion.
 - In every review, whether you are the reviewee or reviewer, try to
talk about -even one- of the values I mention. For instance, talk
performance.

Cheers,
Rob