docs: Update license notice

[Panquesito7]

Related Issue

#6.

Describe the changes you've made

• Update license notice.

Type of change

What sort of change have you made:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, local variables)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update.
• This change requires a documentation update

How Has This Been Tested?

I don't think this applies here.

Checklist

• My code follows the guidelines of this project.
• I have performed a self-review of my own code.
• I have commented on my code, particularly wherever it was hard to understand.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• Any dependent changes have been merged and published in downstream modules.

Screenshots (if applicable)

Original	Updated
original screenshot	updated screenshot

Code of Conduct

• I agree to follow this project's Code of Conduct

[gptkrsh]

1: This is not a Markdown file for a # heading
2: I think we just need to add the image as per the website docs
3: I think noncommercial-no derivatives is a good license.

[Panquesito7]

1: This is not a Markdown file for a # heading 2: I think we just need to add the image as per the website docs 3: I think noncommercial-no derivatives is a good license.

1. Forgot to update the file's format.
2. What do you mean by "image"?
3. Why do you think that? I don't think it won't harm if others use it for commercial use and modify it?

We can discuss this further on Discord as well. @vinzvinci, thoughts?

[gptkrsh]

2. What do you mean by "image"?

The CC rectangle? The docs just ask you to add that or a link to the license in the text. Also adding a license there would also disable the github formatting on the sidebar

3. Why do you think that? I don't think it won't harm if others use it for commercial use and modify it?

All rights of the article submitted shall be to the author, people can use it but with permission from the author 🙂

[Panquesito7]

3. Why do you think that? I don't think it won't harm if others use it for commercial use and modify it?

All rights of the article submitted shall be to the author, people can use it but with permission from the author 🙂

That would break the CC BY-NC-ND 4.0 guidelines as well, AFAIK.

https://creativecommons.org/licenses/by-nc-nd/4.0/ here it specifically says that you can't modify it, regardless you have permission from the author or not.

What do you mean by "image"?

The CC rectangle? The docs just ask you to add that or a link to the license in the text. Also adding a license there would also disable the github formatting on the sidebar

The GitHub formatting on the sidebar doesn't matter much, IMO. People can check the license easily.
For the CC image, we can add that in this PR if you want. 🙂

[gptkrsh]

3. Why do you think that? I don't think it won't harm if others use it for commercial use and modify it?

All rights of the article submitted shall be to the author, people can use it but with permission from the author 🙂

That would break the CC BY-NC-ND 4.0 guidelines as well, AFAIK.

https://creativecommons.org/licenses/by-nc-nd/4.0/ here it specifically says that you can't modify it, regardless you have permission from the author or not.

What do you mean by "image"?

The CC rectangle? The docs just ask you to add that or a link to the license in the text. Also adding a license there would also disable the github formatting on the sidebar

The GitHub formatting on the sidebar doesn't matter much, IMO. People can check the license easily. For the CC image, we can add that in this PR if you want. 🙂

The license can't overthrow the person who applied the license, it is the person who decides the fate of their content. Plus, I think we don't need that text in the license. We can discuss with @vinzvinci