Skip to content

The license of the bundle is unclear #729

Description

@AkihiroSuda

I checked this repo, the installer archive, https://cloud.redhat.com/openshift/install/crc/installer-provisioned , and https://code-ready.github.io/crc/ , but could not find the license of the bundle.

Activity

  1. gbraad commented on Oct 16, 2019

    @gbraad
    Contributor
    • CRC itself is released under Apache-2.0
      • The bundle generation code lives in github.com/code-ready/snc and is similarly licensed
    • OCP and RHEL CoreOS are licensed under their conrresponding licenses and Terms and Conditions (you accepted these when downloading the bundle).
  2. added and removed
    kind/bugSomething isn't working
    on Oct 16, 2019
  3. AkihiroSuda commented on Oct 16, 2019

    @AkihiroSuda
    Author

    you accepted these when downloading the bundle.

    Thanks for the answer, but is it shown only on the first download?

  4. gbraad commented on Oct 16, 2019

    @gbraad
    Contributor

    We will make sure this information is available, but at the moment we are still in pre-GA. This did not get our attention as they these concern projects and products we consume.

  5. praveenkumar commented on Oct 16, 2019

    @praveenkumar
    Member

    Thanks for the answer, but is it shown only on the first download?

    Yes terms and conditions are shown only first time when you login/register but if you check https://www.openshift.com/legal/terms/ have most of info around it but as @gbraad said we still need to put our attention around those concerns.

  6. gbraad commented on Oct 16, 2019

    @gbraad
    Contributor

    Note: for RHEL CoreOS not a single license applies, but each individual component is under their respective license as chosen by the upstream development team.

  7. stale commented on Feb 11, 2020

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  8. added
    status/staleIssue went stale; did not receive attention or no reply from the OP
    on Feb 11, 2020
  9. removed
    status/staleIssue went stale; did not receive attention or no reply from the OP
    on Feb 26, 2020
  10. stale commented on Apr 26, 2020

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  11. added
    status/staleIssue went stale; did not receive attention or no reply from the OP
    on Apr 26, 2020
  12. gbraad commented on May 10, 2020

    @gbraad
    Contributor
  13. removed
    status/staleIssue went stale; did not receive attention or no reply from the OP
    on May 13, 2020
  14. locked and limited conversation to collaborators on Jun 7, 2022
  15. converted this issue into a discussion #3207 on Jun 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/questionStart a discussionstatus/pinnedPrevents the stale bot from closing the issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions