Skip to content

Proposal to merge OSPS-LE-02.0* #399

@hyandell

Description

@hyandell

Merger Suggestion 1

OSPS-LE-02.01: While active, the license for the source code MUST meet the OSI Open Source Definition or the FSF Free Software Definition.
OSPS-LE-02.02: While active, the license for the released software assets MUST meet the OSI Open Source Definition or the FSF Free Software Definition.

I would caution against trying to get into the licensing of the dependency tree, which 02.02 starts to do so. Or even into elements within the project itself. For example, there are many bits of 90s C code that are 'open enough' but not covered by an OSI approved license. I would simplify and merge these into one item. Perhaps:

OSPS-LE-02.01: While active, the license for the project's content MUST meet the OSI Open Source Definition or the FSF Free Software Definition.

I'll note that this feels less like a Baseline, and more like a requirement of the Baseline's scope.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions