dual license discussion forums

[Vlad Stanimir]

As long as you don't add proprietary only extensions to your code you can
use the same source repository, and make it publicaly accessible. Remember
your not selling the code your selling licenses, or more correctly the tight
to use the code under proprietary license.

On Mon, Nov 2, 2009 at 3:12 AM, Dave Tenny <dave.tenny at gmail.com> wrote:

> I'm looking at dual-license scenarios.
>
> I realize this isn't quite the correct discussion forum, but maybe someone
> can give me a pointer
> to the correct discussion forum, since I've been unable to locate one via
> IRC or newsgroups.
>
> I'm looking for a place I might get some advice on the process of
> branching/supporting
> dual-license software and communities that use or support it.  I understand
> some of the basic
> models and things like commit relicensing, but am trying to figure out the
> day to day execution of code changes being rolled
> into corporate and AGPL'd products for best community synergy and change
> utilization.
>
> I'm looking at AGPL + Proprietary licenses for a body of code entirely
> written by my company.
>
> Any pointers appreciated, thanks.
>
> - Dave
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20091103/1e96ab44/attachment.html>