www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luciano Resende" <luckbr1...@gmail.com>
Subject Re: Google Services License
Date Thu, 05 Jun 2008 17:26:11 GMT
How do we get confirmation from Google on these items then ?

On Wed, Jun 4, 2008 at 12:58 PM, Henri Yandell <bayard@apache.org> wrote:
> It starts with:
>
> "By using Google's products, software, services or web sites ("Google
> services"), you agree to the following terms and conditions"
>
> At quick inspection, there is nothing in the GData API project to
> point you to these TOS, so the only concern I would have is if the TOS
> impose conditions on users that mean they're not as free to use the AL
> 2.0 code as they might be. I'm assuming that our developers would be
> (and probably already are for outside ASF reasons) signed up to use
> the services.
>
> Looking at that - the interesting text imo is in section 4.
>
> "You acknowledge and agree that Google services and any necessary
> software used in connection with Google services ("Software") contain
> proprietary and confidential information that is protected by
> applicable intellectual property and other laws and treaties. You
> further acknowledge and agree that Content contained in sponsor
> advertisements or presented to you through Google services is
> protected by copyrights, trademarks, service marks, patents or other
> proprietary rights and laws. Except as expressly authorized by Google
> or other proper third party rights holders, you agree not to modify,
> rent, lease, loan, sell, distribute or create derivative works based
> on Content, Google services or Software, in whole or in part except as
> specifically authorized in a separate written agreement."
>
> So the user agreement gives them none of the usual copyright rights to
> the software used, unless expressly authorized. So the big question
> there is: "Is AL 2.0 on a codebase in code.google.com expressly
> authorizing?".
>
> They also say:
>
> "You agree not to access Google services by any means other than
> through the interface that is provided by Google for use in accessing
> Google services except as specifically authorized in a separate
> written agreement. "
>
> If we have person P, service S, google-api G and apache-product A,
> it's obviously fine for:  P->G->S. Are users allowed to do P->A->G->S?
> While it doesn't stop us adding the dependency, it would be lame if
> the users wouldn't be able to use the feature in Tuscany. I imagine
> that's okay, that the important part is G->S and not P->G.
>
> So I'd want to get confirmation from Google on both of those topics.
> Any thoughts?
>
> Hen
>
> On Wed, Jun 4, 2008 at 10:14 AM, Davanum Srinivas <davanum@gmail.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> IANAL, i agree with Craig. Seems like the TOS
>> (http://code.google.com/tos.html) is applicable when you actually try to
>> use the service, not the code itself.
>>
>> thanks,
>> dims
>>
>> Craig L Russell wrote:
>> |
>> | On Jun 4, 2008, at 12:06 AM, Luciano Resende wrote:
>> |
>> |> We are having a discussion about usage of GData Java Client API that
>> |> is under Apache License 2.0, but then also have some additional  pile
>> |> of legal stuff which applies to any *use* of the code.
>> |
>> | The way I understand this is that the API code itself is licensed via
>> | ASLv2, which means anyone is free to modify, build, distribute,
>> | relicense, etc. and even change the API code to access any other
>> | services that they might want to.
>> |
>> | Once you use the API code to access some services, then you're outside
>> | the scope of the license for the API code and need to look at the
>> | license for the services you're accessing.
>> |
>> | Specific to the usage in Tuscany, I don't see an issue with either using
>> | the code as a binary dependency or changing it to suit your requirements
>> | (forking) although I expect that Google would probably appreciate
>> | feedback on any changes you might propose.
>> |
>> | Craig
>> |
>> |> The discussion
>> |> thread is at [1].
>> |>
>> |> Can we get some advice on this subject.
>> |>
>> |> Thanks
>> |>
>> |> [1] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg32169.html
>> |>
>> |> --
>> |> Luciano Resende
>> |> Apache Tuscany Committer
>> |> http://people.apache.org/~lresende
>> |> http://lresende.blogspot.com/
>> |>
>> |> ---------------------------------------------------------------------
>> |> DISCLAIMER: Discussions on this list are informational and educational
>> |> only.  Statements made on this list are not privileged, do not
>> |> constitute legal advice, and do not necessarily reflect the opinions
>> |> and policies of the ASF.  See <http://www.apache.org/licenses/> for
>> |> official ASF policies and documents.
>> |> ---------------------------------------------------------------------
>> |> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>> |> For additional commands, e-mail: legal-discuss-help@apache.org
>> |>
>> |
>> | Craig Russell
>> | Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>> | 408 276-5638 mailto:Craig.Russell@sun.com
>> | P.S. A good JDO? O, Gasp!
>> |
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.5 (Cygwin)
>>
>> iD8DBQFIRs11gNg6eWEDv1kRAtvFAKDSu/WRdp8o6sLuxgRnDZzKzqJF7QCfVUvX
>> wckg++Wzc1crWLXWche5N4U=
>> =XqIo
>> -----END PGP SIGNATURE-----
>>
>> ---------------------------------------------------------------------
>> DISCLAIMER: Discussions on this list are informational and educational
>> only.  Statements made on this list are not privileged, do not
>> constitute legal advice, and do not necessarily reflect the opinions
>> and policies of the ASF.  See <http://www.apache.org/licenses/> for
>> official ASF policies and documents.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>> For additional commands, e-mail: legal-discuss-help@apache.org
>>
>>
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only.  Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF.  See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>



-- 
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message