Is there a legal issue if yajcache is both kept on jcs and sourceforge
?  Why do I need to remove the code from sourceforge ?  I thought both
hosts open source projects, but maybe I didn't read the fine-print.

So should I put the 1.5 code in a sandbox, or should I remove it from jcs ?  

If we go the sandbox path, which directory is the sandbox ?  Can I use
the @CopyRightApache annotation instead of copy-n-paste the copyright
info at the beginning of every class ?

H

On Thu, 20 Jan 2005 19:35:30 -0800 (PST), Aaron Smuts <[EMAIL PROTECTED]> wrote:
> I'd prefer that experimental ideas be put into an
> experimental directory.  We would do well to start
> playing around with what jdk 1.5 will do for us.
> Clearly this is nothing that we would release or jar.
> Other caches, such as jboss cache, which I heard a
> presentation on today (which is cool, but more like a
> database than a cache, and will probably never perform
> well), are using 1.4 features and are looking into 1.5
> features. . .
> 
> If there are any legal issues, we should take the test
> 1.5 cache out of the repository.  I wish it were not
> in the experimental build directory, had proper apache
> licenses, and was packaged appropriately.  If these
> things were done and it was removed from sourceforge,
> then it seems fine.
> 
> If Hanson would rather play on sourceforge with new
> ideas, then fine, but I don't want any problems if we
> decide to use something for a memory module.  I'd
> prefer that we have some kind of sandbox in jcs
> though.  I think log4j has something like this.  The
> admin servlet was in it for a while (and may still be
> there).  I'd like to see a new memory cache module
> come out of the 1.5 stuff he is working on.  We have
> 1.4 extensions, but no 1.5 . . .  I'd hope that this
> kind of work could happen within jcs.
> 
> I lost the template for a project proposal.  I'll just
> try to submit something that addresses all the
> concerns on the web site.  Should I post a draft on
> the mailing list first?
> 
> Aaron

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to