>>I'm interested in starting an open source project or two, and would like
>>them to fall under an Apache style license.
>>
>>I'd also be happy for them to fall under the Jakarta umbrella, and am
>>curious what I'd need to do to have them do so
>>(otherwise I'll slap them up on sourceforge or somewhere).
>
>see end of jakarta.apache.org/site/management.html
>
>Basically the conditions in simplified form are;
>1. must be done with the "Apache spirit"
>2. must have some guarentee that it will be successful
>
>For (2) I was originally led to believe that the projects must be ready
>established but recent actions indicates that this is not so. It seems that
>projects with enough support internal to Apache may be created but I assume
>they are not allowed to be advertised as Apache projects until they mature.
Thanks for the pointer. How do I get a "PMC" to recommend the project?
As far as #2 goes (a guarantee of success) - my employer is offering to let
me work on this "on the clock" since just such a product is needed for a
current project... So I think we could bang out an initial version in just a
few weeks! -- this only applies to the scheduler - we'll have to see if I
can work on the process automator during work hours...
>>Project 1: an Enterprise Job Scheduler
>>=====================================
>>Description:
>>
>>A job scheduling system that can handle the scheduling of thousands
>>(hopefully millions) of jobs, and cause them to be processed via a variety
>>of J2SE and J2EE mechanisms.
>
>Hey !!!
>A few months a company got me to build one of these. I retain some of the
>copyright on product and for the remainder I plan to reimplement it. A lot
>of the parts are already in Avalon CVS. (Namely the priority queue
>interface + binary heap implementation + cron time trigger/scheduler +
>delayed/periodic scheduler).
Cool... I just looked at the scheduler in Avalon - I hadn't noticed it
before. This too looks like a starting point. Would something as robust
as I have in mind really fit under Avalon though? -- frankly I'm confused
about the role of Avalon - especially now that "commons" is in the works.
I like the idea of the ANT format for describing jobs in XML... sounds
like a good idea... We should look at it close and see how well it
fits requirements for what we want to build.
>My goals were all of the above. I also had the goal that jobs had to be
>executed with a particular set of permissions. ie you may execute job foo
>with Principle Fred (under jdk1.2) or under Subject Barney (jdk1.3+jaas).
Also great ideas.
>>In case you're not sure what I'm referring to, here's a product of BEA's
>>that is similar to what I'm envisioning:
>>http://www.bea.com/products/weblogic/integrator/datasheet.shtml
>
>I don't follow this but Berin from Avalon / Cocoon was talking about this a
>lot (I had no idea what he was nattering on about though). So you may want
>to ask him ;)
What don't you follow? (How am I being unclear? - or are you just not sure
what this type of product is?)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
