[License-discuss] OSL and AFL

[Bruce Perens]

> My problem: with this mix of OSL in the core and AFL for the modules and
themes, I don"t know what license this repository should use.

John brought up one of the issues. But you really should have some legal
advice. And it might be necessary for the person advising to know a little
more about your business.
If you actually have a lawyer, I would be happy to have a phone call with
your lawyer, gratis. Your lawyer would make the final call. If you don't
have a lawyer, I'd be afraid to give you advice because of the liability
issues.

    Thanks

    Bruce

On Mon, Jun 18, 2018 at 7:21 AM, Antoine Thomas <
antoine.thomas at prestashop.com> wrote:

> Hello,
>
> This is my first message to this mailing list and I hope I will do things
> well.
>
> I am Developer Advocate at PrestaShop. Our company and project is focused
> around our open source ecommerce solution. Thanks to the openness of the
> project, we have built a strong ecosystem of agencies, freelances,
> contributors, and of course, merchants.
>
> Currently, the project's core is distributed in OSL 3.0. And all the
> modules and themes are distributed in AFL 3.0. This a legacy choice, from
> the beginnings of the company 11 years ago.
>
> I joined the PrestaShop company recently, with the aim of growing the
> developers community. And recently, we discussed with a developer who wants
> to contribute an interesting piece of code to the project: a new basic
> theme, with a lot of improvements, in a separate repository. This is quite
> new for us, and we would like to use this case as an example for future big
> contributions like this one (governance rules, license, code review, ...)
>
> My problem: with this mix of OSL in the core and AFL for the modules and
> themes, I don"t know what license this repository should use.
>
> The code in this new repository will be based on a piece of code in OSL
> from the core project. However, this specific part of the core will be used
> to create themes. And, most people distribute their themes and plugins in
> AFL, as this is what we asked from the beginnings.
>
> So, I am looking for advice. If we want to be sure that the code in the
> new repository can be distributed in AFL, maybe we need to distribute a
> part of the core, or, the entire core, in double licence OSL + AFL ? Can we
> update the license of only a small part of the core project ? What do you
> think ?
>
> Or, more difficult, do you think that we should change the licence of the
> core and the module to one license ? But which one ? This is actually
> difficult to find resources about OSL and AFL: only a few projects are
> using it.
>
> Looking forward to hearing from you,
>
> Antoine
>
>
>
>
>
> [image: PrestaShop]
> <https://www.prestashop.com/?utm_source=signature&utm_medium=e-mail&utm_campaign=emails-signatures>
>
> Antoine Thomas aka ttoine
>
> Developer Advocate
>
> t: +33 (0)6 63 13 79 06
>
> antoine.thomas at prestashop.com
>
>
>
> _______________________________________________
> License-discuss mailing list
> License-discuss at lists.opensource.org
> http://lists.opensource.org/mailman/listinfo/license-
> discuss_lists.opensource.org
>
>


-- 
Bruce Perens K6BP - CEO, Legal Engineering
Standards committee chair, license committee member, co-founder, Open
Source Initiative
President, Open Research Institute
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20180618/8d26ffd1/attachment-0001.html>