"Geir Magnusson Jr." wrote:
> Then Agora is a project, Catalog is a project,
> and I think you can eliminate the library service idea, since each
> entity in the Library service is a completely self-supporting project in
> it's own right, so it might as well be a peer to Agora and Catalog, just
> to keep people from having to dig too far to find things. In a diagram
Heretofore, Jakarta subprojects have used CVS, mailing-list, and
Bugzilla services to create and maintain codebases.
Agora really wouldn't be a "subproject", since it is really just a
maverick CVS repository for Jakarta committers (a little like a
teacher's lounge).
I expect that the codebase for the catalog would be maintained in the
Library CVS repository, but the Commons would also be offering a working
INSTANCE of the catalog.
So, both of these really look like services, running along side the
actual library CVS repository.
Jakarta
|
| -> Jakarta-site2
| |Mailing Lists
| |-> Tomcat
| |-> Commons
| |-> Turbine
| |...
| |Bugzilla
| |-> Tomcat
| |-> Commons
| |-> Turbine
| |...
| -> Commons
| |Agora CVS
| |Catalog instance
| |Library CVS
| |-> Catalog (codebase)
| |-> DBConnectionPool
| |-> XMLConfig
| |...
| -> Tomcat CVS
| |-> Catalina
| |-> Jasper
|
| -> Turbine
etc
Though, it might be cleaner if the Catalog instance and Agora CVS were
an expansion of the core Jakarta-site, and acted as services alongside
the
Mailing Lists and Bugzilla, so there would be
Jakarta
|
| -> Jakarta-site
| |Mailing Lists
| |-> Tomcat
| |-> Commons
| |-> Turbine
| |-> ...
| |Bugzilla
| |-> Tomcat
| |-> Commons
| |-> Turbine
| |-> ...
| |Catalog instance
| |-> ...
| |Agora CVS
| |-> ...
| |Gump instance
| |-> Tomcat
| |-> Commons
| |-> Turbine
| |Site2 CVS
| |-> Web site
| -> Library CVS
| |-> Catalog (codebase)
| |-> DBConnectionPool
| |-> XMLConfig
| |-> Gump (codebase)
| |-> Web site
| |...
| -> Tomcat CVS
| |-> Catalina
| |-> Jasper
| |-> Web site
| -> Turbine CVS
etc
It's just that, IMHO, a Sandbox or Agora CVS and a catalog are both
essential to the longterm success of a Library subproject, and so
there's been a tendancy to group them together.
-Ted.
