Skip to content
This repository was archived by the owner on Nov 7, 2022. It is now read-only.
This repository was archived by the owner on Nov 7, 2022. It is now read-only.

Checklist for applying an Open Source License to Crown Copyright. #346

@CalvinRodo

Description

@CalvinRodo

I'm doing some work on getting approval to open source my work at ESDC, it would be nice to have a data-driven checklist/guideline for each Department to fill out and follow.

In my research it looks like while there are a lot of similarities in what needs to happen to apply a license there are differences.

For instance the authority to apply a license can sit at the Deputy Minister level in some departments it might be delegate down to a specific level such as the Director Level at ESDC. It might even be specific positions in other departments.

It'd be really handy to codify that for each department and possibly link to the documentation that states that (i.e. Policy, Legislation, Tweet, Whatever...).

I could see lots of other uses too like needed security controls per Department|Platform|Whatever, Stakeholders who need to sign off, anything really needed.

I think this would be pretty useful for supporting the Work in the open by default principle. As I found it pretty time consuming to figure this stuff out myself.

Work in the open by default
Share evidence, research and decision making openly. Make all non-sensitive data, information, and new code developed in delivery of services open to the outside world for sharing and reuse under an open licence.

I could contribute my work towards this, since I plan on doing this at ESDC anyway.

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