public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "James Le Cuirot" <chewi@aura-online.co.uk>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/java:master commit in: licenses/
Date: Sun,  1 Sep 2013 16:08:36 +0000 (UTC)	[thread overview]
Message-ID: <1378049165.672179f55d0d61f1dde018ee7a7423bd49d0ac60.chewi@gentoo> (raw)

commit:     672179f55d0d61f1dde018ee7a7423bd49d0ac60
Author:     James Le Cuirot <chewi <AT> aura-online <DOT> co <DOT> uk>
AuthorDate: Sun Sep  1 15:26:05 2013 +0000
Commit:     James Le Cuirot <chewi <AT> aura-online <DOT> co <DOT> uk>
CommitDate: Sun Sep  1 15:26:05 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/java.git;a=commit;h=672179f5

Minecraft license.

---
 licenses/Minecraft | 79 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 79 insertions(+)

diff --git a/licenses/Minecraft b/licenses/Minecraft
new file mode 100644
index 0000000..038ce8d
--- /dev/null
+++ b/licenses/Minecraft
@@ -0,0 +1,79 @@
+Terms of Use 
+
+What You Get For Purchasing 
+
+When you purchase Minecraft you do so as is, be it in the early stages of 
+development or already fully released. Subsequent updates are only an added 
+bonus and not a guarantee, as icing on a cake. Purchases during the development 
+of the game are discounted and include the full game upon release. 
+
+As we at Mojang strive towards releasing updates for our projects we cannot 
+guarantee that any project will ever be completed and/or provided support for. 
+There's always the risk of a project being discontinued at any time. 
+
+The One Major Rule 
+
+Do not distribute anything we've made. This includes, but not limited to, the 
+client or the server software for the game. This also includes modified versions 
+of anything we've made. Also, you may not resell any gift codes or licence keys 
+- but of course you can give gift codes as gifts. This is necessary so that we 
+can help stop piracy and fraud - and especially users buying keys that have been 
+fraudulently obtained. 
+
+In order to ensure integrity of the game, we need all game downloads to come 
+from a single central source: us. We hope you understand. It's also important 
+for us that 3rd party tools/services don't seem "too official" as we can't 
+guarantee their quality. Make sure to read through our brand guidelines. If you 
+wish to make something pertaining to anything we've made we're humbled, but 
+please make sure that it can't be interpreted as being official. Do not make 
+commercial use of anything we've made unless specifically authorized by us in 
+our brand and assets usage guidelines (which you should read as each of these 
+policies form part of these Terms of Use). 
+
+What You Can Do 
+
+If you've bought the game, you may play around with it and modify it. We'd 
+appreciate it if you didn't use this for griefing, though, and remember not to 
+distribute the changed versions of our software. Basically, mods (or plugins, or 
+tools) are cool (you can distribute those), hacked versions of the Minecraft 
+client or server are not (you can't distribute those). 
+
+Any tools you write for the game from scratch belongs to you. Other than 
+commercial use (unless specifically authorized by us in our brand and assets 
+usage guidelines - for instance you are allowed to put ads on your YouTube 
+videos containing Minecraft footage), you're free to do whatever you want with 
+screenshots and videos of the game, but don't just rip art resources and pass 
+them around, that's no fun. Plugins for the game also belong to you and you can 
+do whatever you want with them, as long as you don't sell them for money. We 
+reserve the final say regarding what constitutes a tool/plugin and what doesn't. 
+
+Other 
+
+We reserve the right to change this agreement at any time with or without notice, 
+with immediate and/or retroactive effect. 
+
+Any suggestions made are assumed to be offered for free unless otherwise agreed 
+before the suggestion was made. We're not going to put up a huge EULA. We're 
+trying to be open and honest, and we hope people treat us the same way back. 
+
+If there's anything legal you're wondering about that isn't answered from this 
+page, don't do it and ask us about it. Basically, don't be ridiculous and we won't. 
+
+/ Markus Persson and friends 
+
+Privacy Policy 
+
+When you purchase a game from us, you fill in your personal/company details. You 
+agree that we store and use your information in our organization to complete the 
+agreement towards you. You have the right, according to the law 
+Personuppgiftslagen (PUL) in Sweden to know about the information registered 
+about you. If it is wrong, insufficient or irrelevant you have the right to make 
+sure that it gets corrected or removed. 
+
+Company Information 
+
+Mojang AB
+Maria Skolgata 83
+118 53, Stockholm
+Sweden
+Organization number: 556819-2388 


             reply	other threads:[~2013-09-01 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-01 16:08 James Le Cuirot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-08-05 22:03 [gentoo-commits] proj/java:master commit in: licenses/ James Le Cuirot
2015-03-13 15:59 James Le Cuirot
2013-09-01 14:44 James Le Cuirot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1378049165.672179f55d0d61f1dde018ee7a7423bd49d0ac60.chewi@gentoo \
    --to=chewi@aura-online.co.uk \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox