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

Review and fix sample projects licenses #14790

Open
l0rd opened this issue Oct 7, 2019 · 4 comments
Open

Review and fix sample projects licenses #14790

l0rd opened this issue Oct 7, 2019 · 4 comments
Labels
area/samples kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P1 Has a major impact to usage or development of the system.

Comments

@l0rd
Copy link
Contributor

l0rd commented Oct 7, 2019

Is your enhancement related to a problem?

From @amisevsk comment:

Many of the projects in devfiles currently do not contain a LICENSE file. Projects that do not have an license:

Anything in the che-samples repositories but notably

Describe the solution you'd like

  • Review the licenses for all the sample projects in the devfile registry
  • Add license for the projects we have created
  • Open issues to replace projects that have an incompatible license or do not have license at all
@l0rd l0rd added the kind/enhancement A feature request - must adhere to the feature request template. label Oct 7, 2019
@tolusha tolusha added severity/P1 Has a major impact to usage or development of the system. area/theia-samples labels Oct 7, 2019
@amisevsk
Copy link
Contributor

amisevsk commented Oct 7, 2019

While reviewing the che-samples projects, it's worth double checking for #13593 as well, as that issue has gone unaddressed thus far.

@amisevsk
Copy link
Contributor

amisevsk commented Nov 5, 2019

PR eclipse-che/che-devfile-registry#96 adds another gothinkster sample to the devfile registry.

@che-bot
Copy link
Contributor

che-bot commented May 12, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

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

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2020
@amisevsk
Copy link
Contributor

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2020
@skabashnyuk skabashnyuk added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label May 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/samples kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

5 participants