Re: Portal Project - beginnings of a taxonomy

Ted Leung wrote:
> <http://wiki.osafoundation.org/bin/view/Journal/PortalProjectMtg20060407>

> Also, we are looking for some help in fleshing out parts of the 
> taxonomy.  On pages 3 and 4 of Mimi's document, there are spaces which 
> are broken down by team and project.  We could really use some input 
> from QA, Build/Release, and some folks in engineering on what should go 
> in those spaces.

Here's the architecture doc -- it would be nice if the "project" 
taxonomy was consistent:
http://chandler.osafoundation.org/docs/0.6/overview.html#Layers

The "Platform" team currently tends to work on these layers:
- services
- domain model
- parcel framework
- repository

The platform team also works on these sub-projects that are really 
external to Chandler:
- PyICU (related to i18n)
- PyLucene (related to search and the repository)
- Zanshin (related to search)
- M2Crypto (security)

I'd say the list of "projects" looks something like this:
- email service
- calendar service
- sharing
- "servlets" or "chandler server"
- domain model
- parcel framework
    - schema api (data model)
    - eggs
    - startup
- repository
    - search
    - collections, notification
    - indexes
- internationalization
- security
- performance
- accessibility
- example parcels

Note that we no longer have a separate "services" or "repository" group.

The bugzilla components were revamped at the beginning of 0.7, these 
also give a window into how we're classifying the project, and should be 
consistent.
http://wiki.osafoundation.org/bin/view/Projects/BugzillaComponentsZeroPointSeven

Cheers,
Katie



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general