Re: Quartz and OpenSymphony

Excellent! I'm thrilled you decided to move on over ;)

Ok, down to business...

One other issue to go with is naming, do you want to stick with the 
quartz name, or go with something like OSScheduler (or something else 
entirely)? The choice is entirely yours. Once that's decided, I'll 
register the new name as a subproject of opensymphony.com, you get set 
up as project owner, etc etc

> My Proposal:
> =======================================================
> 1) Quartz 1.x codebase remains on sourceforge, under the existing 
> Quartz project CVS repository.  There will be at least a 1.3.1 release 
> (in about a week) and a 1.4.0 release (which will be in about 4-6 
> weeks, probably with one or two 1.4.x bug-fix releases following it 
> up).
>
> 2) Quartz 2.0 development will start on the Java.net CVS tree that 
> will be set up for Quartz as a subproject of OpenSymphony.  A 
> development collaboration of Quartz 2.0 will be done via the 
> "opensymphony-developers" mailing list, and the opensymphony snipsnap.
>
> 3) When Quartz 2.0 comes out, should the java.net forums be used for 
> the user community?

Yes, all these sound good.

> 1) Where do the 1.3.x and 1.4.x releases get supported (forums, mail 
> lists etc.) ? will this remain on sourceforge, under the existing 
> Quartz project?
>
I think that having two different forums to monitor will be annoying 
and confusing for users. The hope is that most 1.x users will 
eventually want to move to 2.0. So I think once 2.0 is a reality, then 
all the users can be moved to java.net forums/lists. In the interim, 
once the 2.0 project is setup, the existing user list is told about it, 
and informed that it's a dev-only type list at the moment, and that in 
time the current lists will be removed and the member list migrated 
over.

> 2) What happens to the existing Quartz website? - when does pointing a 
> browser to "quartzscheduler.org" begin to cause a redirection to the 
> opensymphony site? As soon as we set up space for Quartz on the OS 
> site, or do we wait until Quartz 2.0 starts having releases?  What is 
> the long-term destiny of the "quartzscheduler.org" domain?
>
Keep it. Once there are some docs/codebase for 2.0, we migrate the 
website format to the os layout. At some point I think 
quartzscheduler.org should just redirect to os.com/quartz/

>
> -- I guess this all comes down to, when do we want the shift to be 
> visible to the average user?  I'm rather indifferent on this, other 
> than wanting to minimize confusion.  Moving the 1.x branch over (not 
> just source, but also releases) seems like it would create 
> licensing/branding issues, etc...   Since the 2.0 effort will be 
> significant re-writes (or at least significant refatorings) of all 
> code, this seems like a good time to attach new copyright notices, and 
> distribute under a new license.  
> Definitely open to suggestions + instructions on all of this!
>
Yeah, I'd say that moving the 1.x branch would be confusing, and losing 
the cvs history is also a painful hit to have to cope with.

> My java.net user name is "jhouse", can someone add me to the project, 
> and give me rights to create/do the things I need to do to set up the 
> quartz sub-project.  Also, I'll be needing instructions about how to 
> get content onto the OpenSymphony website when the time is right.
>
> Anyway, I'm excited for the move, and I'm excited to get busy on 
> Quartz 2.0.   My current crunch-mode at work should end next week - as 
> we're currently loading what is hopefully the last iteration of code 
> onto the staging servers in just 2 days...    I'm trying to locate a 
> copy of my latest work on the Quartz 2.0 model, which was on a laptop 
> that died a horrible death, but I had (I hope ;-) a couple back-ups of 
> it.   I'll start making some postings regarding design some time next 
> week or the week after.
>
Sounds good, we can keep the discussion on here until the new project 
is set up.

Welcome on board!

Hani



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn