Skip to content

Relicensing Draupnir contributions under Apache-2.0 #1087

@Gnuxie

Description

@Gnuxie

Following on from discussion in #1076. We want to simplify Draupnir’s licensing and use something people are more familiar with. Draupnir currently uses AFL-3.0 for a majority of the code base. And it was specifically chosen to in an attempt to address attribution/whitelabelling, but as discussed in #1076, the license is as ineffective at doing that as any OSI approved license. And the AFL-3.0, has made reuse and maintenance more complicated. If you are unfamiliar with the discussion or have concerns, please raise them in #1076 or in our support room here: https://matrix.to/#/#draupnir:matrix.org

I am asking Draupnir code contributors to confirm whether they agree to license their contributions to this repository under the Apache License Version 2.0.

This would apply to both past contributions already made to this repository and future contributions made while this relicensing work is ongoing (since the work will likely be asynchronous).

If you agree, please review Draupnir's DCO and reply in this issue with:

I agree to license my past and future contributions to the Draupnir repository under the Apache License Version 2.0. I confirm that I have the right to grant this permission for my contributions.

Major contribution authors:

Minor contribution authors (Typos and documentation, that we are asking for out of an abundance of caution)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions