RE: OScheduler

Hani basically said everything I was planning on saying. :)

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf
Of Hani Suleiman
Sent: Sunday, January 11, 2004 4:03 PM
To: [email protected]
Subject: Re: [Opensymphony-developers] OScheduler

On Jan 11, 2004, at 6:38 PM, James House wrote:

*snip*

> work to go, since it is a serious refactoring.   Both the existing 
> (1.x) design and the 2.0 design support plugable persistence.  There 
> is currently RAM and JDBC-based persistence (a bit of an oxymoron with

> RAM).  Also there is a mechanism to use XML files to auto-populate 
> jobs in the RAM store during initialization.
>
Incidentally, last time I looked at it, there was far, far, far too 
many methods that a persistence store had to implement, hopefully this 
is a bit simplified in 2.0!

>
> If the OS community is willing to have Quartz, I'll first need to run 
> it by a few of the other people over on the Quartz project, who ought 
> to at least have a little say about it.  And frankly I've got just a 
> little bit of hesitancy still in me myself (perhaps I'm too proud, but

> it is kind of hard to go from something that's nearly 100% yours, to 
> it only being 50% or so yours).  However, I'm thinking that this is 
> probably the best way to go, as I could really use the additional 
> support (if there is some here).  As I said in my previous e-mail, I 
> was planning to approach Patrick (and OpenSymphony in general) about 
> this some time soon (when I made up my mind definitively), but seeing 
> this mail thread spurred me into it.
>
Well it definitely has my +1
>
> Some things I'd like to know:
>
> 1) Why would OpenSymphony want Quartz?  What does OpenSymphony have to

> offer Quartz? 1a)Are there any of you who are willing to be active 
> developers on core functionality?

Yep, myself ;)

> 1b)Are there any of you who are willing to be active developers on 
> making Quartz work well with (integrate with) other OpenSymphony 
> projects?

Definitely, osworkflow already uses quartz, and we have a few users who 
are quite pleased with this integration.

> 1c)Are there any of you who are willing to be forum supporters etc.? 
> 1d)Are there any of you who are willing to pat me on the back and say 
> "good job"?  ;-)
>
Hah, sure, as long as you accept that the pats on the back don't come 
for free, and you'd have to be put up with occasional punches ;)

> 2) How is Java.net working out?  Are you moving there completely?

We've moved all source code there, but mailing lists are still on 
sf.net. There's a vague plan to move those, but we don't really have a 
desperate and pressing need so it's been lagging a bit. I'm in favour 
of any new projects using java.net exclusively though.

> 2a) Where/how do you guys host your site?  (I've got a tomcat server 
> that I run the Quartz website and wiki (SnipSnap) on, as well as 
> ownership of the domain "quartzscheduler.org" (and ".com"), a 
> mail-server, and I happily use JIRA for issue tracking).

Atlassian hosts os.com, basically all our projects have an 'ant docs' 
target that dumps everything they want on the website in some dist/docs 
type dir, which is linked in to the website whenever (currently, Pat 
does this manually) someone updates the docs. The look and feel are 
separate from this and are controlled by sitemesh, hence the 
(hopefully) consistent look and feel across projects.

>  -- Thus Quartz is primarily using SourceForge for file distribution 
> and the forum (though the forum software really bites).  If Quartz is 
> going to be an OpenSymphony project, it ought to sit along side the 
> others (actually I'm not entirely sure how much the others are all 
> hosted the same place, in the same way, etc.) -- I guess my question 
> really is: Where will it be expected that Quartz is hosted (mail, 
> forum, CVS, documentation, "home page", wiki, etc.)   -- Also, I'm 
> willing to offer my server (on a T3 with 40GB available transfer per 
> month) for anything that's needed.

I think we're ok for now in terms of bandwidth, unless Atlassian want 
to hand over responsibility for hosting. Quartz would get its own wiki 
space and www.os.com/quartz.

One thing I'd like to clarify is that in terms of control, I think 
you'd still retain 100%. It's up to you to determine which of us to 
allow on as developers, and as the project owner, feel free to turf out 
any of us that misbehave. It's your project completely as long as 
you're the main contributor/maintainer. The nice thing about java.net's 
projects is that you can have fine grained control that way. What os 
will add to quartz is the increased exposure, brand name, and through 
that more users, contributors, and developers.



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Opensymphony-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensymphony-developers


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html