James House wrote:
> I also agree with the poster on this thread who said that libraries/products
> should not be tied to a framework, but rather the framework should
> incorporate them. I'm positive that if the Job Scheduler is tied to Avalon
> or Turbine or XXXX framework, many people (including myself) will not be
> very happy about using it within a product that already has it's own (and
> very different) framework.
This sums up what the Commons is suppose to be, and why we started it.
Jakarta isn't SourceForge, and it can be hard to get a new subproject
approved without an existing codebase. If you were already a Committer
to
another Jakarta subproject, then you could set something up in the new
Commons sandbox, and start community building there.
Unfortunately, we still don't have any type of incubator for new
subprojects proposed by new developers.
My best advice really is to open a project or two on SourceForge, and
keep
us posted as to your progress. The people who were interested here can
join you there, and when you're ready, you can propose it to Jakarta, if
that's what you still want.
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 737-3463.
-- http://www.husted.com/about/struts/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
