News for hackers. Stuff that matters.

A comment on Why your next project should be public domain. Parent comment

Re:Why your next project should be public domain by rmc on Thursday July 11, 2013 @01:35PM (#6027594)
Isn't the default "all rights reserved"?

(Note: GitHub ToS says if you put copyright code on it, then you are by default allowing others to fork & download it, so the default licence is looser than the legal default)

[ Parent | on HN ]
Re:Why your next project should be public domain by tjaerv on Thursday July 11, 2013 @01:40PM (#6027639)
Nice catch about GitHub's Terms of Service.

From https://help.github.com/articles/github-terms-of-service:

  > ...by setting your pages to be viewed publicly, you agree to allow
  > others to view your Content. By setting your repositories to be
  > viewed publicly, you agree to allow others to view and fork your
  > repositories.
[ Parent | on HN ]
Re:Why your next project should be public domain by zeckalpha on Thursday July 11, 2013 @07:09PM (#6029882)
Sure but I see many repositories (and gists) with interesting things, with comments and other indicators saying thanks for the code, but with no license. This means people are taking things anyway, which the authors seem okay with. This is not okay, safe, stable, or sustainable.
[ Parent | on HN ]