You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We may want to think about licensing all content on the site under CC-BY-SA 3.0. Things like the wiki, canon, salad, and Nidaba would be nice to be open source.
All SO data that we use is licensed under CC-BY-SA 3.0. Eventually we may start showing SO data on sopython itself as part of Nidaba. Part of CC-BY-SA requires you to license anything that you use under the same licence and link to it.
Xavier pointed out this article by Jeff here. From this I've put together the below checklist of what we need to do to attribute properly:
Visually indicate that the content is from Stack Overflow or the Stack Exchange network in some way. It doesn't have to be obnoxious; a discreet text blurb is fine.(* I believe that this will be covered by a link in the footer.*)
Hyperlink directly to the original question on the source site.
Show the author names for every question and answer.
Hyperlink each author name directly back to their user profile page on the source site
If we go with CC-BY-SA for our content, we also need to properly attribute all our own editors. E.g. wiki articles need to list all their contributors. Ideally, we would combine this with version control and a history functionality.
The text was updated successfully, but these errors were encountered:
We may want to think about licensing all content on the site under CC-BY-SA 3.0. Things like the wiki, canon, salad, and Nidaba would be nice to be open source.
All SO data that we use is licensed under CC-BY-SA 3.0. Eventually we may start showing SO data on sopython itself as part of Nidaba. Part of CC-BY-SA requires you to license anything that you use under the same licence and link to it.
Xavier pointed out this article by Jeff here. From this I've put together the below checklist of what we need to do to attribute properly:
Note that this is different to licensing the code itself.
Also, as pointed out by @poke:
The text was updated successfully, but these errors were encountered: