It looks like we all are in agreement. To get this to work without
impacting the daily builds will require me to make some minor tweaks to my
cron scripts and the like, so I plan to do this over the weekend.
The plan is to create a new jakarta-alexandria-data cvs module, and grant
everyone who currently has karma to jakarta-alexandria to this new cvs
tree. I'll seed this with the contents of the following proposal/gump
directories: dtd, profile, project (which I will rename to module in the
process), and repository. I'm also inclined to include rubix.xml and
rubypad.xml as working examples of workspaces, and the infamous naglist.
No code is to be placed into this repository, not even stylesheets. The
data that should be placed in this cvs module will be the ones used to feed
the various alexandria (including base and proposals) tools. Ultimately,
much of this data may not amount to much more than an href to an external
source, but this would be the cvs repository into which that href should be
placed.
The cvs update messages will be routed to this mailing list. Discussions
and votes on new members will also take place here. One established, an
announcement will be made on the jakarta and xml general mailing lists.
I'll also start to take a serious look at the dtd's that Jason has started,
my initial contribution to this effort will likely be to add comments.
Josh - as you are looking at ripping out castor and replacing it, consider
using, building upon, or suggesting modifications to this dtd.
Everybody please express your concurrence, comments, and/or objections in
the usual manner. As for me: +1.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
