launchpad-dev team mailing list archive

[Bjorn Tillenius <bjorn@xxxxxxxxxxxxx>]

On Wed, Mar 31, 2010 at 12:02:19PM -0300, Guilherme Salgado wrote:
> On Wed, 2010-03-31 at 12:59 +0300, Bjorn Tillenius wrote:
> > Hi guys,
> > 
> > so, it's time for the Technical Architect team to tackle its first task.
> > Create the Launchpad Architectural Vision.
> > 
> > First of all, what is it? It's aimed to be documents that describe the
> > different parts of Launchpad. It will explain how Launchpad works, which
> > moving parts are involved, and how it will fit together. It will also
> > explain the various sub-systems, and explain how to do various things in
> > Launchpad code. For example, how do I send and receive e-mail? How do I
> > add an html page? How do I write a script? Etc.
> > 
> > An important goal of the Vision is to avoid people doing duplicate work,
> > so it should document that canonical way of doing various things in
> > Launchpad. If you implement a new feature, and for example don't know
> > how the implementation should look like, the Vision should be the place
> > to look, to see what existing code you can re-use. That's why I want to
> > focus on things that are shared (or supposed to be shared) across
> > applications to start with.
> > 
> > I need your help, though! It's a lot of work, and some of you have a lot
> > of expertise of certain areas of Launchpad. I need help figuring out
> > what should be included in the Vision. I also need volunteers describing
> > the different parts. For example, someone from the Code team would be a
> > good candidate writing about the job system. Although, not necessarily.
> > If you're interested in how a certain part works, trying to document it
> > is a great way of learning! Also, you don't have to volunteer yourself,
> > finding other volunteers is also acceptable :)
> > 
> > These are the things I thought of so far that should be included:
> > 
> >     * Overview of Launchpad and its moving parts
> >     * job system
> >     * e-mail (sending/receiving)
> >     * Database garbage collection (garbo)
> >     * expose API methods/attributes
> >     * Web app
> >         * Browser views
> >         * TAL formatters
> 
>   * Breadcrumbs
>   * canonical_url
>   * AJAX
> 
> >     * Librarian
> >     * Comments
> >     * DB Schema
> 
> Master/slave DBs and when/how to use them
> 
> Vocabularies, maybe?

Yes, all of these should be in there, thanks.



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