You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Joe Bowser <bo...@gmail.com> on 2011/10/27 22:29:22 UTC
[Callback-Android] ASF Headers, Notices and Third Party Code
Hey
I'm currently working on CB-3 in JIRA, and I noticed that the Contacts
Class that we're using has the Android Apache 2.0 Licence notice on
it. Is this a derived work, and if so, how much code is left and do
we have to have this licence and copyright notice on it? Can someone
look into this?
Also, there is the old Crypto class that I threw in there back in the
old hack days that is from Android Snippets. While the site says that
we can use it for whatever we want without worrying about copyright, I
can't see their TOS and I would rather remove the Crypto classes from
Callback. I don't think that anyone is using them, since we didn't
document them, and they aren't very well thought out. Is it cool to
yank it out?
Joe
Re: [Callback-Android] ASF Headers, Notices and Third Party Code
Posted by Filip Maj <ma...@gmail.com>.
yeh punt it
On Fri, Oct 28, 2011 at 11:08 AM, Brian LeRoux <b...@brian.io> wrote:
> +1
>
> yank it!
>
>
>
> On Thu, Oct 27, 2011 at 2:18 PM, Simon MacDonald
> <si...@gmail.com> wrote:
>> The Android Apache 2.0 license can be removed from the contact code.
>> The original code for this came from an example off the Android site
>> that Fil had in his repo. Since them we've dropped support for older
>> Android versions and we've removed the code that needed the license. I
>> had a fork that removed it under phonegap-android but it never got
>> applied.
>>
>> I'd say to yank the Crypto stuff as well.
>>
>> Simon Mac Donald
>> http://hi.im/simonmacdonald
>>
>>
>>
>> On Thu, Oct 27, 2011 at 4:29 PM, Joe Bowser <bo...@gmail.com> wrote:
>>> Hey
>>>
>>> I'm currently working on CB-3 in JIRA, and I noticed that the Contacts
>>> Class that we're using has the Android Apache 2.0 Licence notice on
>>> it. Is this a derived work, and if so, how much code is left and do
>>> we have to have this licence and copyright notice on it? Can someone
>>> look into this?
>>>
>>> Also, there is the old Crypto class that I threw in there back in the
>>> old hack days that is from Android Snippets. While the site says that
>>> we can use it for whatever we want without worrying about copyright, I
>>> can't see their TOS and I would rather remove the Crypto classes from
>>> Callback. I don't think that anyone is using them, since we didn't
>>> document them, and they aren't very well thought out. Is it cool to
>>> yank it out?
>>>
>>> Joe
>>>
>>
>
Re: [Callback-Android] ASF Headers, Notices and Third Party Code
Posted by Brian LeRoux <b...@brian.io>.
+1
yank it!
On Thu, Oct 27, 2011 at 2:18 PM, Simon MacDonald
<si...@gmail.com> wrote:
> The Android Apache 2.0 license can be removed from the contact code.
> The original code for this came from an example off the Android site
> that Fil had in his repo. Since them we've dropped support for older
> Android versions and we've removed the code that needed the license. I
> had a fork that removed it under phonegap-android but it never got
> applied.
>
> I'd say to yank the Crypto stuff as well.
>
> Simon Mac Donald
> http://hi.im/simonmacdonald
>
>
>
> On Thu, Oct 27, 2011 at 4:29 PM, Joe Bowser <bo...@gmail.com> wrote:
>> Hey
>>
>> I'm currently working on CB-3 in JIRA, and I noticed that the Contacts
>> Class that we're using has the Android Apache 2.0 Licence notice on
>> it. Is this a derived work, and if so, how much code is left and do
>> we have to have this licence and copyright notice on it? Can someone
>> look into this?
>>
>> Also, there is the old Crypto class that I threw in there back in the
>> old hack days that is from Android Snippets. While the site says that
>> we can use it for whatever we want without worrying about copyright, I
>> can't see their TOS and I would rather remove the Crypto classes from
>> Callback. I don't think that anyone is using them, since we didn't
>> document them, and they aren't very well thought out. Is it cool to
>> yank it out?
>>
>> Joe
>>
>
Re: [Callback-Android] ASF Headers, Notices and Third Party Code
Posted by Simon MacDonald <si...@gmail.com>.
The Android Apache 2.0 license can be removed from the contact code.
The original code for this came from an example off the Android site
that Fil had in his repo. Since them we've dropped support for older
Android versions and we've removed the code that needed the license. I
had a fork that removed it under phonegap-android but it never got
applied.
I'd say to yank the Crypto stuff as well.
Simon Mac Donald
http://hi.im/simonmacdonald
On Thu, Oct 27, 2011 at 4:29 PM, Joe Bowser <bo...@gmail.com> wrote:
> Hey
>
> I'm currently working on CB-3 in JIRA, and I noticed that the Contacts
> Class that we're using has the Android Apache 2.0 Licence notice on
> it. Is this a derived work, and if so, how much code is left and do
> we have to have this licence and copyright notice on it? Can someone
> look into this?
>
> Also, there is the old Crypto class that I threw in there back in the
> old hack days that is from Android Snippets. While the site says that
> we can use it for whatever we want without worrying about copyright, I
> can't see their TOS and I would rather remove the Crypto classes from
> Callback. I don't think that anyone is using them, since we didn't
> document them, and they aren't very well thought out. Is it cool to
> yank it out?
>
> Joe
>