The apache licence is compatible to varying degrees to other licences. Some
are only allowed to be included when they've been obfuscated to prevent
easy tinkering. I can't find it at the moment but there is a page on the
apache website which explains it better.
If I can find it I'll let you know.
Thanks
Angus Turner
angusisf...@gmail.com


On Mon, Oct 22, 2012 at 1:38 PM, Ed - 0x1b, Inc. <w...@0x1b.com> wrote:

> I'm sorry, why is an open source project obfuscating anything?
>
> On Sun, Oct 21, 2012 at 1:06 PM, Michael MacFadden
> <michael.macfad...@gmail.com> wrote:
> > Angus,
> >
> > In regards to obfuscation.  You might take a look at ProGuard:
> >
> > http://proguard.sourceforge.net/index.html#
> >
> > It's an open source obfuscator.
> >
> > And yep.  I'll help with the final signing.
> >
> > ~Michael
> >
> > From:  Angus Turner <angusisf...@gmail.com>
> > Reply-To:  <wave-dev@incubator.apache.org>
> > Date:  Sunday, October 21, 2012 12:58 PM
> > To:  <wave-dev@incubator.apache.org>
> > Subject:  Re: Releasing...
> >
> > Sorry i'm the hold up. My script that I used to remove the copyright
> > headers changed all the comments to not being javadocs anymore. I've been
> > busy lately and haven't had time to fix it.
> >
> > The next step is working out how to obfuscate the jars in a couple of the
> > libraries to make them compatible with the apache licence. If anyone has
> > any experience in this any help would be greatly appreciated.
> >
> > After that it's a matter of getting all the release documentation sorted,
> > and then signing and packaging everything and I believe Micheal agreed to
> > be the one to finish off all the signing. We also need to create a
> release
> > page.
> > Thanks
> > Angus Turner
> > angusisf...@gmail.com
> >
> >
> > On Sun, Oct 21, 2012 at 7:43 PM, Upayavira <u...@odoko.co.uk> wrote:
> >
> >>  Where did we get to on preparing a tet release? Have we got licensing
> >>  headers in order? Does anything else stand in our way?
> >>
> >>  Thx,
> >>
> >>  Upayavira
> >>
> >
> >
> >
>

Reply via email to