Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explicitly define the prison-api project's Open Source Contribution policy #915

Open
deduper opened this issue May 8, 2021 · 3 comments · Fixed by #917
Open

Explicitly define the prison-api project's Open Source Contribution policy #915

deduper opened this issue May 8, 2021 · 3 comments · Fixed by #917

Comments

@deduper
Copy link

deduper commented May 8, 2021

I'm on a non-ministryofjustice team. Our project will be consuming resources from the prison-api.

My job is to report to my team, answers to these questions:

  1. Is contributing to the prison-api project closed to non-ministryofjustice developers?
  2. If contributing to the prison-api project is not closed, what are the prerequisites for being allowed to contribute?
  3. Under what license are ministryofjustice projects in general (prison-api specifically) open sourced?
  4. In what sense of „open source" should ministryofjustice projects be thought of from a third-party project's perspective?

The Open Source Initiative mentions the word „license“ in nine of the ten numbered parts of its Open Source Definition:

  1. Free Redistribution
    The license shall not restrict any party...

  2. Source Code
    [not mentioned]

  3. Derived Works
    The license must allow modifications and derived works...

  4. Integrity of The Author's Source Code
    The license may restrict source-code from being distributed in modified form only if...

  5. No Discrimination Against Persons or Groups
    The license must not discriminate against any person or group of persons...

  6. No Discrimination Against Fields of Endeavor
    The license must not restrict anyone from making use of the program in a specific field...

  7. Distribution of License
    ...redistributed without the need for execution of an additional license...

  8. License Must Not Be Specific to a Product
    ...within the terms of the program's license...

  9. License Must Not Restrict Other Software
    The license must not place restrictions on other software...

  10. License Must Be Technology-Neutral
    No provision of the license may be predicated on any individual technology or style of interface...

However, the prison-api project doesn't have a license included or mentioned anywhere in it. My team and I are curious to understand what that means from a practical standpoint.

deduper added a commit to deduper/prison-api that referenced this issue May 9, 2021
@petergphillips
Copy link
Contributor

Good question, will need to find out and get back to you.

@petergphillips petergphillips linked a pull request May 10, 2021 that will close this issue
@deduper
Copy link
Author

deduper commented May 10, 2021

„...Good question...“

Thank you @petergphillips. I'm sure you noticed. So forgive me for being pedantic. There are four question-s :)

@petergphillips
Copy link
Contributor

We follow the technical guidance as specified in https://ministryofjustice.github.io/technical-guidance/#moj-technical-guidance. Unfortunately I can't find reference to an open source contribution policy there so will have to investigate further.

In the meantime it would be helpful to know what team you are working for, what you would like to contribute and what resources you are intending to consume.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants