Skip to content

feat: enhance discussion around licensing for package CODE vs documentation (text, tutorials) #39

Open
@lwasser

Description

@lwasser

from @tupui

#19 (comment)

About documentation. Some advice to use a different license than code. It's apparently advisable to use a CC one for the doc and something else like MIT/BSD for the code. e.g. in the GNU world they make this distinction: https://www.gnu.org/doc/doc.html
I don't recall any example in the Python sphere though.

Just adding this for completeness (at least what I know). I would not add that to your text which is good I think.

we might want to consider clarifying this a bit in our licensing page in the future so users have a better grasp of license issues. that page is it's own page. @sneakers-the-rat might also have some thoughts on expanding this page too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancement-featuresomething new to add to our guidehelp wantedWe welcome a contributor to work on this issue! thank you in advance!sprintable

    Type

    No type

    Projects

    Status

    Python Package Guide

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions