Permalink
Browse files

herocraft

  • Loading branch information...
1 parent 7382029 commit 200a95a3707825f1ad02fc034d6100e19a8db8f0 @tekkub tekkub committed Feb 9, 2012
Showing with 26 additions and 0 deletions.
  1. +26 −0 2012-02-08-herocraft.markdown
View
26 2012-02-08-herocraft.markdown
@@ -0,0 +1,26 @@
+1. <https://github.com/sct/HeroTitles> - was forked from a Project that was
+posted in error onto Github. The original work has been removed because it
+is copyright ALL RIGHTS RESERVED - HeroCraft Coding. unfortunately no
+License text accompanied the original product, regardless. Projects are
+considered All Rights Reserved unless otherwise stipulated regardless of
@rmsy
rmsy added a line comment Feb 20, 2012

This is total bullcrap, and was made up entirely. I can't believe GitHub took down this repository.

@SamB
SamB added a line comment Oct 24, 2014

@rmsy: Actually, the logic is sound; assuming they are the ones who own the copyright on the code that they say was published in error, and that they really did not provide any license terms, this is a totally legitimate takedown notice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
+where code has been posted.
+
+2. All forked material is infringing & project is infringing
+
+3. You may contact me at this e-mail address or under my Github Username [private]
+
+4. Person that has posted this material can be contacted @ [private]
+He has refused to take the work down himself.
+
+5. "I have a good faith belief that use of the copyrighted materials
+described above on the infringing web pages is not authorized by the
+copyright owner, or its agent, or the law."
+
+6. "I swear, under penalty of perjury, that the information in this
+notification is accurate and that I am the copyright owner, or am
+authorized to act on behalf of the owner, of an exclusive right that is
+allegedly infringed."
+
+7. Signed - [private]
+
+If you have anymore questions feel free to respond.

0 comments on commit 200a95a

Please sign in to comment.