Skip to content

Missing License #10

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

Open
3 tasks done
aaron-bray opened this issue Jun 13, 2023 · 3 comments
Open
3 tasks done

Missing License #10

aaron-bray opened this issue Jun 13, 2023 · 3 comments

Comments

@aaron-bray
Copy link

aaron-bray commented Jun 13, 2023

It is great to see all the work you have done so far 💯

That said the project seems to be missing a license file. 😱

No worry, I suggest you follow these few steps:

  • 1️⃣ Choose a license. We suggest you use a permissive license that includes patent and contribution clauses. This will help protect developers and ensure the code remains freely available. We suggest you the Apache 2.0. Read here to learn more about licenses.

  • 2️⃣ Add the the license file to your project. This guide may be helpful.

  • 3️⃣ Add a section like the following at the end of your project's README.md file:

    ⚠️ Make sure to update the abcdefghi and YYYY-MM-DD placeholders respectively with the short commit SHA and the commit date corresponding to step 2 above

    ## License
    
    This software is licensed under the terms of the [Apache Licence Version 2.0](LICENSE).
    
    The license file was added at revision [abcdefghi](https://github.com/Slicer/slicer_download/commit/abcdefghi) on YYYY-MM-DD, but you may consider that the license applies to all prior revisions as well.
    

Background

Without a license file, interpreting the licensing terms becomes complex. In a nutshell, code hosted on GitHub without a license is likely made available through section D. 5. License Grant to Other Users of the GitHub terms of service.

Reading issue No license does not allow commercial or private use is also informative.

Links

Description Link
Which open source license is appropriate for my project? https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project
Adding a license to a repository https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository
All About Open Source Licenses https://fossa.com/blog/what-do-open-source-licenses-even-mean/
Choose an open source license https://choosealicense.com/
No License [https://choosealicense.com/no-permission/](https://choosealicense.com/no-permission/%5D(https://choosealicense.com/no-permission/))

Disclaimers

I am not a lawyer. As such, my suggestions can not serve as legal advice.


This comment was adapted from my GitHub saved replies, it is licensed under a Creative Commons Attribution 4.0 International License and you are welcome to reuse it. Creative Commons License

@Vital-Volkov
Copy link
Owner

Hi!
Thanks aaron-bray I'll choose the license later when I finish main tasks and make descriptions.

@resistcorp
Copy link

Hi @Vital-Volkov, I would like to know if you had time to choose a license. What kind of license were you thinking of adopting for this project (and the dependency RenderPlugin.dll) ?
With your help, we have confirmed that your approach works on power walls which are our target. Now remains the legal question of whether we can use this project or not, and we won't without a license, of course.

We would absolutely consider making a donation if you choose to publish this project and the plugin under a FOSS license.

@Vital-Volkov
Copy link
Owner

Hi @resistcorp, OK I added an MIT license and now finishing and testing a big update. Thanks.

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

No branches or pull requests

3 participants