Skip to content

Dual licensing and commercialisation? #11

Description

@cronky

At what point do we dual license / look to reasonably cover costs from commercial entities leveraging DIST? Making the plans for this clear early might provide reassurance that the nature of the project won't fundamentally change (or if it will a little what that might look like).

Some notes from kick-off discussions:

  • True open-source method: the schema and taxonomy are free for anyone to use and always will be
  • Commercial layer sits on top: auditing, validation, consulting are paid services
  • "Allow" route → DIST free
  • "Commercial" route → free schema + paid audit/validation

Metadata

Metadata

Assignees

No one assigned

    Labels

    NEXT (v0.2)NEXT: things we want to work on soon but not immediately. Part of NOW, NEXT and LATER prioritisationquestionFurther information is requested
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions