Skip to content

Consider dual-licensing under Apache 2.0? #190

@lilith

Description

@lilith

The MS-PL is incompatible with many free software licenses, as it imposes a unique restriction:

(D) If you distribute any portion of the software in source code form, you may do so only under this license by including a complete copy of this license with your distribution. [...]

Many OSI-approved copyleft licenses require that linking or interacting code must be licensed in a manner that does not further restrict user rights. This conflicts with the MS-PL as it specifically prohibits the right to re-license.

There are many GPL, LGPL, and AGPL-licensed libraries - yet we are forced to choose between using them - and using this library. We are also prevented from using any copyleft license in software which depends on RazorEngine.

Dual-licensing (or-relicensing) under Apache 2 would solve this. As GitHub notifies people who are mentioned, re-licensing would involve pasting the list of contributors into this thread and asking for a release of their copyright. Getting approval can take anywhere from a few days to several months, depending upon contributor awareness.

Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions