On 1/24/07, Christopher Schultz <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Nathan,
Thanks for the quick response.
Nathan Bubna wrote:
> Code contributions are best through JIRA anyway, as that allows you to
> mark it explicitly as contributed for use under the Apache License.
Well, I decided to start here because of the library dependencies. I'm
happy to tun everything through JIRA once there's an agreement.
> Yeah, we're open source, so installing a binary-only [of your] library
probably
> won't work.
Certainly. In fact, I /want/ to give this thing away. I've just been
unable to get much guidance for the best way to do it.
> However, it's not really that difficult to start your
> own open source project for this at Google Code
> (http://code.google.com/hosting/createProject) or SourceForge
> (http://sourceforge.net/register/). Once it is set up there, that
> makes it much easier for people to try it out or check out the code,
> which in turn makes it much, much easier to find a better home for it
> or else build a dev community around it there.
I was operating based upon a rumor that the ASF doesn't like to use libs
and stuff that are either non-ASF or that operate under certain types of
licenses. I wanted to make sure that whatever I did wasn't a deal-breaker.
The official doctrine is that ASF projects are encouraged (but
definitely not required) to use other ASF projects wherever possible.
However, ASF projects regularly and happily use non-ASF software
(assuming the license allows) for needs which cannot be served by
another ASF project. So, for instance, VelocityStruts happily makes
use of the SSL-Ext project, which is hosted by sourceforge.
Certain types of licenses can definitely be problematic. I'm no
expert in this field, but if you are interested in a non-Apache
license, then let me know which one and i'll help you find out if and
how we can use it as an Apache project.
> In fact, depending on what license you put it under (i recommend ASL
> 2.0 :), once you set it up and release a version, we would then be
> able to integrate it into the VelocityTools tests and increase it's
> exposure for you.
I was kinda hoping that Jakarta Commons would express interest, but it's
kind of unclear how to donate something like this.
Donating needn't be that difficult. You could just find a project
which looks like it could use your code, create a new JIRA issue,
attach your code, and mark it as a contribution under the ASL. But of
course, that's no guarantee anything will be done with it.
It's getting an existing ASF project to *adopt* code that is tricky.
The PMC (Project Management Committee) for the adopting project has to
want the code first. Even once they do, some large code donations
must be brought through the incubator, though i'm not fully versed in
all the situations where that is or isn't required. The most
important thing is getting a PMC to want the code. Once you have the
interest, the rest is usually just procedure, and members of that PMC
should help you through it.
If it is an independent project that will not be fully
absorbed/integrated into an existing project, then it is much easier
to get interest if people are free to try the code out (i.e. there is
a release they can download) and can check out the source for it from
some public repository.
If it is just a small set of classes/patches, then posting the code as
JIRA attachments may be sufficient for people to see it and try it
out.
> If you're willing to take the time to set it up and release it as an
> independent project, then that is the path i would recommend.
It's all set up and ready to go, actually. Just looking for a good home
and for me to choose a license (ASF is just fine with me).
Well, then i think you ought to create a project for it on Google Code
or Sourceforge and do a release soon. Then i think we can look at
getting the release uploaded into a maven repository and using it as a
dependency of VelocityTools tests.
Thanks again,
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFt/dZ9CaO5/Lv0PARAhTCAJ9OHzOlAhro1gaQD+gpfZ1sEelOrQCdEBhb
ddOsdqLN5/3IODZwdQAibiA=
=bvqN
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
