Licensing for package CODE vs documentation (text, tutorials)

[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.

[lwasser]

this is a good issue but we have'nt as a community made a decision on what license to recommend for docs /// we've only decided to use mit for code. i'm going to pull this from the project board until we figure this out so someone can work on it with specific guidance based upon a community decision!