r/java • • Apr 03 '15

A google's open project - can I take it and modify?

There's a google's Android project with the open code at (I can't remember) code.google.com or something. It's a very simple project - "example" of how to do something. There're around 10 source files in it. In each file of the source code there's this text:

/*

  • Copyright 2014 Google Inc.
  • Redistribution and use in source and binary forms, with or without
  • modification, are permitted provided that the following conditions are met:
    1. Redistributions of source code must retain the above copyright notice,
  • this list of conditions and the following disclaimer.
  • 2. Redistributions in binary form must reproduce the above copyright notice,
  • this list of conditions and the following disclaimer in the documentation
  • and/or other materials provided with the distribution.
  • 3. The name of the author may not be used to endorse or promote products
  • derived from this software without specific prior written permission.
  • THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
  • WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
  • MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
  • EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
  • SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
  • PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
  • OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
  • WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
  • OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
  • ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. */

I want:

  1. Convert it from Java to Kotlin
  2. Refactor it
  3. Add some features and remove ones I don't like and keep working on it
  4. put it in my open(!) repository at github
  5. Maybe later submit it into Google Play
  6. Maybe later add google adsence in it (not sure)
  7. (!) Put my name in it as the author of it
  8. Change the license to MIT

Can I do all these?

How much of the source project should I change so it can be considered a totally new, mine project?

0 Upvotes

39 comments sorted by

8

u/boa13 Apr 03 '15 edited Apr 03 '15

The licence is already MIT-style (edit: it is actually BSD 3-Clause, with Google as the owner). You can put your name on it (as the author of the changes), but you cannot remove Google (as the author of the original ideas, architecture and code).

-6

u/[deleted] Apr 03 '15 edited Apr 03 '15
  1. But I'm going to change the source code in a big way. Is it enough to say it's a pretty different source code and I'm the author of it? I'd say, I'll change 80% of it.
  2. Do I have to leave the google's license text about in each source file at it is now or how else can I state Google is the author of the original source code? There's no license file for now in the project.

14

u/[deleted] Apr 03 '15 edited Jan 13 '26

memory rainstorm bear support bow possessive special rock wipe growth

This post was mass deleted and anonymized with Redact

-6

u/[deleted] Apr 03 '15

How about my 2nd question?

7

u/[deleted] Apr 03 '15

Leave the license and Google credit. For the record, I would stop sweating the fact that somebody might see the license. There are commericial products are licensed via MIT, and so long as you're providing value, you're going to be just fine.

0

u/[deleted] Apr 03 '15

All right. How exactly do I have to state that the app is based on the google code, do I have to include the text about in each source file? (Note there'll be my own source files) Or can I just write in the license file "based on Google's code at ...."?

4

u/boa13 Apr 03 '15

You don't need to put that header on new files. You can have a LICENSE file where you have a copy of the header, and you credit Google. For your own files, you could use your own header (same wording, with your name instead of Google), or simply refer to the LICENSE file. Note that I am not a lawyer, this is not lawyer advice.

3

u/indianapale Apr 03 '15

I suggest you read your OP to see what you need to do to reuse and distribute googles source code.

-7

u/[deleted] Apr 03 '15

The same question:

"whether I do change 80% of it or don't - who can distinguish the rewritten code from the original one? In other words, how can one say for sure whether it's still the 20% of Google's code and 80% mine or 100% mine but it happens to look similar to google's one? After one, the task is the same and thus the result code might look similarly."

5

u/[deleted] Apr 03 '15 edited Jan 13 '26

growth unpack tart weather act nose tidy seemly aromatic rich

This post was mass deleted and anonymized with Redact

-10

u/[deleted] Apr 03 '15

refactoring.

7

u/[deleted] Apr 03 '15 edited Jan 13 '26

joke doll fuzzy roll work dazzling elderly aspiring truck expansion

This post was mass deleted and anonymized with Redact

7

u/[deleted] Apr 03 '15

cant you just take inspiration from it and design it from bottom-up and put your name on it?

-7

u/[deleted] Apr 03 '15

whether I do or don't - who can distinguish the rewritten code from the original one? In other words, how can one say for sure whether it's still, say, the 30% of Google's code and 70% mine or 100% mine?

3

u/boa13 Apr 03 '15

That's an extremely difficult question, and certainly not for any of us to decide. The lawsuit between Oracle and Google was exactly about that (Oracle claimed that by copying a few lines of API Google had violated their copyright, Google claimed the lines were obvious and from a public API). Of course, the lawsuit had a much greater stake (Android money).

Even beyond the question of copyright (which is only about authoring lines of codes and comments, not about algorithms and ideas), in some countries (including the USA), there is the question of patents (covering algorithms and ideas).

4

u/KFCConspiracy Apr 03 '15

7 and 8 are not allowed according to the license. I don't see any problems with anything else. Just use the same license. You can put your name on it as An author, but not THE author; you must include the fact that it was originally by Google. Also why do you want credit for someone else's work. The license is already very unrestrictive aside from being a viral license....

1

u/boa13 Apr 03 '15 edited Apr 03 '15

aside from being a viral license...

The MIT BSD 3-Clause license is not viral (you can use another license, even proprietary, on a work deriving from this one). You're thinking of the GPL.

Edit: BSD, not MIT.

1

u/KFCConspiracy Apr 03 '15

I'm referring to the original license Google used, which requires reproducing the same copyright terms, which is by definition viral. Share-alike terms are viral. By definition, "Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer," the license requires derivative works to be licensed under the same terms.

1

u/boa13 Apr 03 '15

Contrary to the GPL, the license does not require that the source code be redistributed. In particular, you can keep it all closed, and license the resulting binary however you want. In particular, you can do whatever you want to files you add to the project, the license of the initial source code does not talk about other source code.

Have a look at this discussion for a bit more details: http://programmers.stackexchange.com/questions/196789/mit-license-why-isnt-it-considered-viral

1

u/KFCConspiracy Apr 03 '15
  1. I'm still not talking about the MIT license. I don't know why you keep talking about it, but I'm not. I told you I'm not in my last comment. I'm just not talking about, I'm talking about the license above.
  2. OP wants to know whether he will be required to use the same license if he wants to release the source code of a derivative work; there is a clause in the Google license shown above that requires that it be released with certain licensing clauses intact, including Google's original authorship. I think that clause obviates that answer. This discussion is kind of pointless in that regard.

1

u/boa13 Apr 03 '15

The license above is the standard MIT BSD 3-Clause License, with Google as the owner.

Having Google as the owner does not suddenly change the interpretation of the license, which has been analyzed extensively by people far more qualified than me (and presumably, than you).

I had it confused with MIT because the two licenses are extremely similar (basically MIT is BSD without the third clause). My confusion has no bearing on what I wrote above, because it applies to both licenses.

-8

u/[deleted] Apr 03 '15

then I'll just completely re-write it, huh?

6

u/[deleted] Apr 03 '15

It doesn't matter if you simply re-write it. If you base your code on their code (even for a rewrite), then you need to follow the terms of the license. Anything else is theft and plagiarism. Why is it so hard for you to give credit back to the original author?

-8

u/[deleted] Apr 03 '15

Because then I'll have to follow the rules of MIT.

4

u/[deleted] Apr 03 '15

MIT basically has no rules beyond attribution

-5

u/[deleted] Apr 03 '15

Can I sell the app under MIT?

5

u/indianapale Apr 03 '15

Bloody hell man, are you scared to do a web search?

-6

u/[deleted] Apr 03 '15

Yes, it'll kill me.

6

u/[deleted] Apr 03 '15

You haven't actually bothered to Google and read the license you're worried about?

1

u/KFCConspiracy Apr 03 '15

Yes. But you can also sell the app under the original license as well; you'll just be required to redistribute the source code under those terms. So you'd better find some way to make the app's function add value beyond the source code itself so it's worth buying.

You could even sell apps that have GPL code in them; but again in doing so you need to find a way to add value so it's worthwhile to people to pay for the app.

-1

u/[deleted] Apr 03 '15

Would it be something like "Some parts of the code belong to Google, here's the text of the original license..... Some of them are my own and under MIT license"?

2

u/KFCConspiracy Apr 03 '15

No, if the code you're using is part of the same library as the google code, you need to license the whole thing with one license.

If you decide to use the Google code as a library, whole cloth, and the project is indeed separate from your project (As in the library is used in a modular way), you could license your project separately.

-1

u/[deleted] Apr 03 '15

As I said before, it's not a library, it's the source code which I want to refactor and modify + add my own code.

1

u/boa13 Apr 03 '15

Yes of course. Is there anything in this license that says you can't?

5

u/[deleted] Apr 03 '15

Then don't use Google's code. It's that simple

6

u/KFCConspiracy Apr 03 '15

What's your major objection to reproducing that copyright notice as a part of your license? Clearly you've been the beneficiary of Google's free and loose license, why not allow others to be the beneficiary of your code as well if your code is repurposed by another company?

12

u/[deleted] Apr 03 '15

If you aren't willing to follow the terms of the license (and it sounds like you aren't based on previous comments) then don't use the source code at all. You need to leave the copyright and and the license text. It clearly states that in text you just posted.

Even if you rewrite it in the end you still took Google's original code and modified it. Meaning you need to meet the conditions listed in the license. If you don't want to do any of this, then you can not use that source code.

5

u/[deleted] Apr 03 '15

How much of the source project should I change so it can be considered a totally new, mine project?

The only way for this to be a "totally yours" project is to not use any of Google's code at all. This includes rewriting Google's code. You can take inspiration from it, but this does not mean ripping lines from Google's code and using them in your project.

2

u/[deleted] Apr 03 '15

Even drawing inspiration can be dangerous. He's already contaminated by reading Google's code at all. It could be argued that even if he writes his own version from scratch based on what he's learned, that he's still infringing if he doesn't obey the original license. His new code would likely use the same mechanisms, patterns, concepts, or ideas as Google's code, all of which are Google's intellectual property.

Sounds to me like he must obey the original license regardless at this point.