We had a lot of discussion about that and decided for now keep GPL. The
main reason is because we want to integrate ElasticInbox with some
products on the market which have GPLv2.
Maybe we will create another branch which will just use ASL2. In any
case, we are willing to make license less restrictive.
--
Rustam.
Just an update on the licensing issue. After some research we are now
leaning towards BSD.
The main reason for choosing BSD over ASL2, is BSD's compatibility with
GPLv2.
There are many open source communication products which are available
under GPLv2 and we want to ensure that they can integrate ElasticInbox
in their projects.
However, to update all work we will need to merge netty branch into
master. Currently master includes some GPL work (removed in netty).
Also we need permission from you to change license of your work ;) So
when can we expect james-protocols 1.6 final version?
--
Rustam.
On Tue Dec 20 07:01:42 2011, Norman Maurer wrote:
> Just be aware that moving from GPL to ASL2 is not that easy later as
> you need to get the permission from all contributers. If you not get
> it you will need to remove the code in question and rewrite it from
> scratch.
>
> Using an ASL2 license allows elasticinbox to be used with any othe
> license that I'm aware of.
>
> Bye,
> Norman
>
>
> 2011/12/19 Rustam Aliyev <rus...@code.az <mailto:rus...@code.az>>