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.

Sign up for GitHub

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

Jump to bottom

Write an explanatory "License thoughts" document #29

Open
quaid opened this issue Jun 7, 2021 · 6 comments
Open

Write an explanatory "License thoughts" document #29

quaid opened this issue Jun 7, 2021 · 6 comments
Labels
area/community Indicates an issue/PR is related to the overall community. kind/governance Indicates an issue/PR is related to governance. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@quaid
Copy link
Member

quaid commented Jun 7, 2021

The idea for this document is to be a set of thoughts about the project's licensing. This is intended to establish some ground to quell concerns about projects bringing non-GPL licensed code to in, on, or around operate-first.cloud.

Questions that have or will come up:

  • How does this apply to projects that are connected via an Operator?
  • How does Operate First interact with permissively licensed code within its own codebase?
  • Is the GPL an appropriate license for content? Wouldn't it be better to use a CC license to make it easier/possible to merge in outside CC content and to have our CC content reused by the many other CC-licensed content projects?
@quaid quaid added area/community Indicates an issue/PR is related to the overall community. kind/governance Indicates an issue/PR is related to governance. labels Aug 1, 2021
@sesheta
Copy link
Member

sesheta commented Oct 30, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 30, 2021
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 16, 2021
@sesheta
Copy link
Member

sesheta commented Feb 15, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 15, 2022
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 11, 2022
@sesheta
Copy link
Member

sesheta commented Jun 10, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 10, 2022
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 25, 2022
@sesheta
Copy link
Member

sesheta commented Sep 24, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 24, 2022
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 7, 2022
@sesheta
Copy link
Member

sesheta commented Jan 5, 2023

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 5, 2023
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 26, 2023
@sesheta
Copy link
Member

sesheta commented Apr 26, 2023

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/community Indicates an issue/PR is related to the overall community. kind/governance Indicates an issue/PR is related to governance. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@quaid @sesheta