Am 06.06.2015 um 16:09 schrieb alls...@gmail.com:
> Hi,
>
> Crossbar is licensed under AGPL. Does it means I cannot redistribute it
> in a close source product. And even cannot use it in a close source
> online service ...
Correct.
If you modify Crossbar.io code under the AGPL, then you must publish
your changes under the AGPL.
If you want to license Crossbar.io under non-AGPL, we (Tavendo) offer
commercial licenses for embedding that does not come with AGPL requirements.
>
>
> Thanks
> Mike
>
> --
> You received this message because you are subscribed to the Google
> Groups "Crossbar" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to crossbario+...@googlegroups.com
> <mailto:crossbario+unsub...@googlegroups.com>.
We firmly believe that connecting components to Crossbar.io does not link them to Crossbar.io in a way which requires them to be licensed under an AGLPL-compatible license. (see http://crossbar.io/docs/Crossbar-License/).
When packaging Crossbar.io with your software, be careful not to introduce any dependencies/links with your code beyond the WAMP connections. For details of when this might happen see the FSF FAQ at http://www.gnu.org/licenses/gpl-faq.html.
Regards,
Alex
If you want to license Crossbar.io under non-AGPL, we (Tavendo) offer
commercial licenses for embedding that does not come with AGPL requirements.
With configuration files, there will usually be only one way to express a particular configuration. Copyright does (generally) not protect ideas but the creativity in a particular expression of an idea. Applied to configuration files, this means that there should be no copyright in them.