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

Add Apache 2.0 License #20

Merged
merged 1 commit into from Jan 16, 2021
Merged

Conversation

csrwng
Copy link
Contributor

@csrwng csrwng commented Aug 18, 2020

Adds LICENSE file to this repository

Copy link
Member

@LalatenduMohanty LalatenduMohanty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci-robot
Copy link
Contributor

@LalatenduMohanty: changing LGTM is restricted to collaborators

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@wking
Copy link
Member

wking commented Aug 18, 2020

Do we want README.md and/or CONTRIBUTING.md wording to make the grant explicit? Vs. relying on the presence of a LICENSE file to implicitly grant access under the license's terms. I'm also fine punting this point to follow-up discussion.

And I explicitly release all of my previous contributions to this repository under the Apache License, Version 2.0, if any of them were significant enough to be copyrightable in the first place ;).

@LalatenduMohanty
Copy link
Member

LalatenduMohanty commented Aug 18, 2020

Do we want README.md and/or CONTRIBUTING.md wording to make the grant explicit? Vs. relying on the presence of a LICENSE file to implicitly grant access under the license's terms. I'm also fine punting this point to follow-up discussion.

This came to my mind when I was reviewing the PR as well. Cross checked couple of other repositories and I did not see the license explicitly mentioned in the readme. So I think this PR as it is , should be fine.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 16, 2020
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 16, 2020
@csrwng
Copy link
Contributor Author

csrwng commented Jan 4, 2021

/remove-lifecycle rotten

@openshift-ci-robot openshift-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jan 4, 2021
@crawford
Copy link
Contributor

/lgtm
/approve
/override ci/prow/okd-e2e-aws
/override ci/prow/okd-e2e-aws-upgrade
/override ci/prow/e2e-aws
/override ci/prow/e2e-aws-upgrade

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 15, 2021
@openshift-ci-robot
Copy link
Contributor

@crawford: Overrode contexts on behalf of crawford: ci/prow/e2e-aws, ci/prow/e2e-aws-upgrade, ci/prow/okd-e2e-aws, ci/prow/okd-e2e-aws-upgrade

In response to this:

/lgtm
/approve
/override ci/prow/okd-e2e-aws
/override ci/prow/okd-e2e-aws-upgrade
/override ci/prow/e2e-aws
/override ci/prow/e2e-aws-upgrade

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: crawford, csrwng, LalatenduMohanty

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 15, 2021
@crawford crawford added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Jan 15, 2021
@openshift-merge-robot openshift-merge-robot merged commit b9f4530 into openshift:master Jan 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants