Apache potential migration?

[GoogleCodeExporter]

Jetlang is really a smart library, congrats.
If it were possible, would you consider migrating the project as an Apache 
project? (may be under Apache Commons).
The benefits being a wider community/audience and more exposure that could 
trigger more usage and help.
What's your feeling about it?

Original issue reported on code.google.com by hbies...@gmail.com on 8 Dec 2010 at 3:20

[GoogleCodeExporter]

It could definitely use more exposure, but I've never considered moving it to 
apache. The project currently requires very little maintenance.

Are you associated with apache or just a user of the library?

Original comment by mike.ret...@gmail.com on 9 Dec 2010 at 3:26

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I'm a Jetlang library user and associated with Apache (Commons PMC);  I can 
sponsor the project - ie propose it to PMCs fellows and have you added as a 
committer/owner - & could do the initial (not so) heavy lifting if you're 
interested.
The project is already maven-ized which makes migrating to the Apache 
environment fairly easy; from what I can gather, the only effort would be a bit 
of syntactic sugar coating and assembling documentation from the various pieces 
which I could perform and let you review. 
IMO,  Jetlang would be a great addition to the Commons projects, small 
libraries that perform one thing really well.

Original comment by hbies...@gmail.com on 9 Dec 2010 at 1:35

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I've decided to keep jetlang right where it is.  The project is relatively 
mature and requires very little upkeep. Switching to apache might help promote 
the project, but at this time I don't think it is worth the time and effort.

Thanks for the consideration. 

Original comment by mike.ret...@gmail.com on 16 Jan 2011 at 2:13

• Changed state: Done
• Added labels: Type-Other
• Removed labels: Type-Defect