[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#963630: Aparapi license has changed to a more liberal license



Glad to hear it. If you have any questions at all reach out to me anytime. I've been the package maintainer for some time. While I am not the founder I handle most of the day to day coding and project management and am in close contact with the original founder who is still a contributor and active participant but not as active as myself these days. So I try to handle any of the day to day issues that come up. Always happy to answer any questions if you need anything.

On Wed, Sep 23, 2020 at 3:38 PM Andreas Tille <tille@debian.org> wrote:
Dear Jeffrey,

thanks a lot for the good news.  We will package from the new location
for Debian then.

Kind regards

    Andreas.

On Wed, Sep 23, 2020 at 12:03:12PM -0400, Jeffrey Freeman wrote:
> Hi I noticed you had a conversation sometime back here:
> https://github.com/aparapi/aparapi/issues/50
>
> I wanted to mention that Aparapi is no longer maintained at the address you
> specified and all developers, including the founder, have moved onto the
> new repository which is now active and well funded here:
> https://git.qoto.org/aparapi/aparapi
>
> During that port back in 2016 the license was reviewed by a paid lawyer
> hired by the new foundation and the license was legally changed. As our
> lawyer had assured us the original additional verbiage in the license for
> the original release of Aparapi did not functionally change the license in
> any way, it simply allowed AMD to protect themselves against any liability
> should the software be misused. The original added verbiage basically
> amounted to "You can not break the law when you exercise your rights under
> this license", which is already implied with an MIT license but not
> explicitly stated.
>
> As such we were able to legally and effectively relicense the software
> under the apache license and the new software is licensed wholly under the
> Apache license with no additional restrictions of any kind. You are free to
> repackage and redistribute the license exactly as you would under the
> Apache license.
>
> Let me know if you have any questions.

--
http://fam-tille.de

Reply to: