Dual License documentation

[Jan200101]

Currently the documentation is also licensed under MIT however it requires that the copyright notice remain intact for any derivative use.

Dual Licensing the documentation under a public domain license such as CC0-1.0 would let people use the resources as they need or want.

Note

You can use the 👍 reaction to increase the issue's priority for developers.

Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.

[huly-for-github]

Connected to Huly®: V_0.6-26227

[JalonSolov]

What would be the benefits to the V project of adding the dual license?

[Jan200101]

To be clear, I am talking only about the documentation not the main repo.

The documentation would benefit from a second license that does not require attribution so that code snippets and various bits of information can be used regardless of their significance and without the need to keep attribution.

Right now the docs are either under MIT or Proprietary depending on how you want to interpret things or in which repo you look, neither is really benefitial for documentation, adding CC0-1.0 as an additional license would only clarify that the documentation can be freely used.

[Xyndra]

I also think you this would be beneficial. I did not check the current licensing state, but it would certainly make sense for the documentation not to require attribution. This is even more true since most people copy and paste code from the documentation into their codebase and probably also don't attribute it, leading to them breaking the license without thinking about it

[jorgeluismireles]

I wonder what exactly documentation is, because we both programmers and AI copy-paste code from whatever we could find: examples folder, *_test.v files, github issues/PR/discussion sections... https://modules.vlang.io/ itself comes from v files comments. Maybe pointing somewhere in your site or your book where you are going to show people how to program in V the link of V project where LICENSE file is located should be enough.