Skip to content

Create policy for 3rd party dependencies #1686

@markwilkie

Description

@markwilkie

For example, ASP does:

ASP.NET's policy about third-party dependencies are:

3rd party dependencies should be strong name signed
3rd party dependencies cannot be used in code that needs to build in source-build (unless that 3rd party dep is part of source-build, like Json.NET)
3rd party dependencies must comply with all the other Microsoft OSG requirements (see https://opensource.microsoft.com/resources). This covers a range of things, like lawyer stuff, licensing and IP separation, etc., as well as component registration https://docs.opensource.microsoft.com/tools/cg.html

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

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions