> Ok, but why do we have to actually move the packages?
> Why can't Agora host an online catalog where it would list packages that
> products have designed for independent use?
So everyone can be able to work on it ( fix the bugs, enhance, etc. ) and
make sure all sides realize this. ( plus, reduce the feeling that a
component "belongs" to a project )
I think the Library can do that - the goal of Agora is to have projects
cooperate on the development of non-specific code, and this can't work if
the code remain in the original repository ( cvs access, rules, etc need
to be special ).
> The Jakarta committers would have instant access to the catalog, and
> whatever they post is listed instantly, without any prior review
> process. (Lazy consensus.)
Great for the library - for Agora we need commiters to be able to make
changes and commits to the components ( that's the goal ).
> This will make us all more aware of what is buried in other subprojects,
> and encourage more people to cross-commit, without making any
That's a great step forward in any case - but Agora should un-bury the
code.
Plus, moving code to agora should be an "active" decision, based on a vote
and the benefits it may add to the project - and then work will be
require to remove deps, etc.
Costin
