This website provides codes the public codes are MIT licensed, and MIT
license gives permission to sublicense means adding my own license to the
used codes,
but they say these:
1- what does this mean from the terms (Public Pens you build on CodePen are MIT
licensed <https://opensource.org/licenses/MIT>, meaning other people are
free to use it for whatever they like as long as that is also MIT licensed.)
2- what does this mean from the licensing (Anyone can use the code you put
on CodePen for whatever they wish – but if they do – that code also must
have this same license. This is to encourage open sharing of code.)
Terms page: https://blog.codepen.io/documentation/terms-of-service/
License page: https://blog.codepen.io/documentation/licensing/
If I use a public pen code in my project and modify it, they require that
the modified code also must be MIT licensed?
Hi all,
Just a quick heads-up: we've released the 0.12 branch of the REUSE
helper tool. It contains a few interesting new features and fixes.
Highlights contain more supported files names and types for the
`addheader` subcommand, and a broad preset of different styles for
copyright lines aside from the recommended "SPDX-FileCopyrightText".
Feel free to read the changelog for all details:
https://github.com/fsfe/reuse-tool/blob/master/CHANGELOG.md
You can get the tool from PyPI, download the Docker images, build it
from source, or get it via package managers [^1].
As always, issues and pull request are highly appreciated!
Best,
Max
[^1]: https://github.com/fsfe/reuse-tool#install
--
Max Mehl - Programme Manager - Free Software Foundation Europe
Contact and information: https://fsfe.org/about/mehl | @mxmehl
Become a supporter of software freedom: https://fsfe.org/join
Dear all,
I hope this email finds you well.
More and more communities and companies include the REUSE best practices
into their policies. Just with the REUSE API there are currently 336
projects registered as compliant [^1]. At the FSFE, we wanted to have a
closer look at how communities manage and experience the adoption
process.
Therefore, I am pleased to share an interview with Andreas Cord-Landwehr
with you that we've published today. He drove the process of making the
KDE frameworks REUSE compliant, with code that is partly older than some
of the project's contributors.
https://fsfe.org/news/2020/news-20201215-01.html
He also shares a few interesting ideas about how the REUSE ecosystem
could evolve. I would be thrilled to learn about your opinions on this,
and generally whether you can relate to Andreas' experiences.
Best,
Max
[^1]: https://api.reuse.software/projects
--
Max Mehl - Programme Manager - Free Software Foundation Europe
Contact and information: https://fsfe.org/about/mehl | @mxmehl
Become a supporter of software freedom: https://fsfe.org/join