You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by "William A. Rowe Jr." <wr...@rowe-clan.net> on 2012/04/03 19:43:01 UTC

Re: Is there an ASF license for Apple's "Apple Developer Program" ?

On 3/31/2012 8:43 AM, Rob Weir wrote:
> On Fri, Mar 30, 2012 at 7:20 AM, Ross Gardler <rg...@opendirective.com>wrote:
> 
>> There isn't (to my knowledge), I can imagine an increasing number of
>> projects wanting such a thing though. Unless someone tells me I'm
>> wrong and we already have one would you be interested in seeing if
>> Apple are open to such an arrangement?
>>
>>
> 
> I'd recommend first very careful review of the licensing terms first, on
> legal-discuss, to ensure that we're comfortable with any restrictions use
> of their SDK brings.  This would also help with other potential
> contributors who might have iOS apps they would like to contribute, but
> whose current analysis suggests that the Apple terms are incompatible.

nonsense

These are the very same SDK tools that these very same Apache Committers already
use on a daily basis.

The only modulo here is that some have access through work.  Some purchase their
own access.  Some have been comp'ed subscriptions individually or through other
organizations.

This simply makes the same tool for a committer free or discounted from what
they already paid.  For example, I was an MSDN subscriber through work for some
years, as a consultant for some years, took a break from my subscription on some
other years.  Now, I'm using a subscription donated for ASF committers.  Nothing
changed.

Sure, you can have a discussion about whether some WizBang API introduces new
licensing restrictions, platform lock-in, etc.  But we are NOT GOING TO BEGIN
auditing the Oracle Developer Suite, the Microsoft Developer Network, the Apple
Developer Network, the IBM HP VMware Google RedHat Citrix Adobe Amazon (OH GOD
MAKE IT STOP!!!) developer tool program for every possible future quirk.

There are real questions to be asked about specific tools and specific api's in
the open source and closed source world and the projects which are affected need
to do their homework and work with ASF legal to resolve ambiguity.  But any of
these examples includes hundreds of tools and api's and sdk's which have no
intersection with an ASF code base.

If Jim works out some connections for ASF <> Apple and you use Apple then enjoy
that perk, and otherwise, please EIGNORE?  Thanks :)


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Is there an ASF license for Apple's "Apple Developer Program" ?

Posted by dsh <da...@googlemail.com>.
+1

Cheers
Daniel

On Tue, Apr 3, 2012 at 7:43 PM, William A. Rowe Jr. <wr...@rowe-clan.net> wrote:
> On 3/31/2012 8:43 AM, Rob Weir wrote:
>> On Fri, Mar 30, 2012 at 7:20 AM, Ross Gardler <rg...@opendirective.com>wrote:
>>
>>> There isn't (to my knowledge), I can imagine an increasing number of
>>> projects wanting such a thing though. Unless someone tells me I'm
>>> wrong and we already have one would you be interested in seeing if
>>> Apple are open to such an arrangement?
>>>
>>>
>>
>> I'd recommend first very careful review of the licensing terms first, on
>> legal-discuss, to ensure that we're comfortable with any restrictions use
>> of their SDK brings.  This would also help with other potential
>> contributors who might have iOS apps they would like to contribute, but
>> whose current analysis suggests that the Apple terms are incompatible.
>
> nonsense
>
> These are the very same SDK tools that these very same Apache Committers already
> use on a daily basis.
>
> The only modulo here is that some have access through work.  Some purchase their
> own access.  Some have been comp'ed subscriptions individually or through other
> organizations.
>
> This simply makes the same tool for a committer free or discounted from what
> they already paid.  For example, I was an MSDN subscriber through work for some
> years, as a consultant for some years, took a break from my subscription on some
> other years.  Now, I'm using a subscription donated for ASF committers.  Nothing
> changed.
>
> Sure, you can have a discussion about whether some WizBang API introduces new
> licensing restrictions, platform lock-in, etc.  But we are NOT GOING TO BEGIN
> auditing the Oracle Developer Suite, the Microsoft Developer Network, the Apple
> Developer Network, the IBM HP VMware Google RedHat Citrix Adobe Amazon (OH GOD
> MAKE IT STOP!!!) developer tool program for every possible future quirk.
>
> There are real questions to be asked about specific tools and specific api's in
> the open source and closed source world and the projects which are affected need
> to do their homework and work with ASF legal to resolve ambiguity.  But any of
> these examples includes hundreds of tools and api's and sdk's which have no
> intersection with an ASF code base.
>
> If Jim works out some connections for ASF <> Apple and you use Apple then enjoy
> that perk, and otherwise, please EIGNORE?  Thanks :)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Is there an ASF license for Apple's "Apple Developer Program" ?

Posted by dsh <da...@googlemail.com>.
Rob,

I read your initial comment as such as you would have been worried
about the licensing terms of the developer program itself [1] and
probably the App Store usage guidelines [2].

Apple SDKs can be downloaded free-of charge without requiring a
developer account and as William pointed out they are already being
used anyway. Developer accounts are only necessary if you want to
download pre-releases of SDKs or operating systems offered by apple.
This is pretty handy for instance if you want to test your app before
a particular operating system gets released. Additionally you want to
have a developer account if you require your apps to be signed by
apple. Additionally you could get ISO images of past OSes from the
developer program including OSX server which can be used as a staging
server for iOS apps.

AFAIK similar, reasonable or unreasonable discussions exist around the
terms of the Android SDK [3] but then again if so it's a separate
discussion and unrelated to getting free of charge access to the Apple
developer program.

[1] http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&ved=0CEEQFjAC&url=http%3A%2F%2Fwww.scribd.com%2Fdoc%2F41213383%2FiOS-Developer-Program-License-Agreement&ei=kxZ_T8bwNouQ4gSbgN3ABw&usg=AFQjCNHgHwHiQHtiSVuawdUte0PiW4HXbA
[2] https://developer.apple.com/appstore/guidelines.html
[3] http://developer.android.com/sdk/terms.html

Cheers
Daniel

On Fri, Apr 6, 2012 at 5:17 PM, Rob Weir <ro...@apache.org> wrote:
> On Tue, Apr 3, 2012 at 1:43 PM, William A. Rowe Jr. <wr...@rowe-clan.net> wrote:
>> On 3/31/2012 8:43 AM, Rob Weir wrote:
>>> On Fri, Mar 30, 2012 at 7:20 AM, Ross Gardler <rg...@opendirective.com>wrote:
>>>
>>>> There isn't (to my knowledge), I can imagine an increasing number of
>>>> projects wanting such a thing though. Unless someone tells me I'm
>>>> wrong and we already have one would you be interested in seeing if
>>>> Apple are open to such an arrangement?
>>>>
>>>>
>>>
>>> I'd recommend first very careful review of the licensing terms first, on
>>> legal-discuss, to ensure that we're comfortable with any restrictions use
>>> of their SDK brings.  This would also help with other potential
>>> contributors who might have iOS apps they would like to contribute, but
>>> whose current analysis suggests that the Apple terms are incompatible.
>>
>> nonsense
>>
>> These are the very same SDK tools that these very same Apache Committers already
>> use on a daily basis.
>>
>
> The issue, of course, is not what you do with the Apple SDK in the
> privacy of your own bedroom.  The question is about creating
> dependencies for releases and the restrictions these bring to
> downstream consumers.    If you want to just say those are questions
> for the individual PMC's to resolve, then I'd agree, but I then note
> that the IPMC is the PMC for podlings, so my point is in order.
>
>> The only modulo here is that some have access through work.  Some purchase their
>> own access.  Some have been comp'ed subscriptions individually or through other
>> organizations.
>>
>> This simply makes the same tool for a committer free or discounted from what
>> they already paid.  For example, I was an MSDN subscriber through work for some
>> years, as a consultant for some years, took a break from my subscription on some
>> other years.  Now, I'm using a subscription donated for ASF committers.  Nothing
>> changed.
>>
>> Sure, you can have a discussion about whether some WizBang API introduces new
>> licensing restrictions, platform lock-in, etc.  But we are NOT GOING TO BEGIN
>> auditing the Oracle Developer Suite, the Microsoft Developer Network, the Apple
>> Developer Network, the IBM HP VMware Google RedHat Citrix Adobe Amazon (OH GOD
>> MAKE IT STOP!!!) developer tool program for every possible future quirk.
>>
>> There are real questions to be asked about specific tools and specific api's in
>> the open source and closed source world and the projects which are affected need
>> to do their homework and work with ASF legal to resolve ambiguity.  But any of
>> these examples includes hundreds of tools and api's and sdk's which have no
>> intersection with an ASF code base.
>>
>> If Jim works out some connections for ASF <> Apple and you use Apple then enjoy
>> that perk, and otherwise, please EIGNORE?  Thanks :)
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Is there an ASF license for Apple's "Apple Developer Program" ?

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 4/6/2012 10:17 AM, Rob Weir wrote:
> On Tue, Apr 3, 2012 at 1:43 PM, William A. Rowe Jr. <wr...@rowe-clan.net> wrote:
>> On 3/31/2012 8:43 AM, Rob Weir wrote:
>>> On Fri, Mar 30, 2012 at 7:20 AM, Ross Gardler <rg...@opendirective.com>wrote:
>>>
>>>> There isn't (to my knowledge), I can imagine an increasing number of
>>>> projects wanting such a thing though. Unless someone tells me I'm
>>>> wrong and we already have one would you be interested in seeing if
>>>> Apple are open to such an arrangement?
>>>>
>>>>
>>>
>>> I'd recommend first very careful review of the licensing terms first, on
>>> legal-discuss, to ensure that we're comfortable with any restrictions use
>>> of their SDK brings.  This would also help with other potential
>>> contributors who might have iOS apps they would like to contribute, but
>>> whose current analysis suggests that the Apple terms are incompatible.
>>
>> nonsense
>>
>> These are the very same SDK tools that these very same Apache Committers already
>> use on a daily basis.
>>
> 
> The issue, of course, is not what you do with the Apple SDK in the
> privacy of your own bedroom.  The question is about creating
> dependencies for releases and the restrictions these bring to
> downstream consumers.    If you want to just say those are questions
> for the individual PMC's to resolve, then I'd agree, but I then note
> that the IPMC is the PMC for podlings, so my point is in order.

But it's apropos of nothing, yet.  Who has their login to WWDC handy?  How
many entitlements appear in your list of SDK's and other Apple developer
features?  500?  5000?  At least 50 full frameworks, supported, deprecated
and historical, alone.

Name ONE SDK from WWDC which a podling has a specific desire to deploy,
and then, we can look at its license.  Name one from Novell, or Microsoft.
We've done this a number of times at APR and HTTP Server projects.  But
until you identify a particular SDK, this isn't actually a productive
discussion to even a single podling.  When you have identified a specific
SDK, have a reference to it's license and decided you can't work out if
it is class A, B or X relative to an AL ASF work, then file a jira ticket
with the legal team, point to the license, and they can help sort it.
So it still would be unlikely to be worth email traffic to discuss, since
the jira ticket is both deliberative and archival of the decision.


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Is there an ASF license for Apple's "Apple Developer Program" ?

Posted by Rob Weir <ro...@apache.org>.
On Tue, Apr 3, 2012 at 1:43 PM, William A. Rowe Jr. <wr...@rowe-clan.net> wrote:
> On 3/31/2012 8:43 AM, Rob Weir wrote:
>> On Fri, Mar 30, 2012 at 7:20 AM, Ross Gardler <rg...@opendirective.com>wrote:
>>
>>> There isn't (to my knowledge), I can imagine an increasing number of
>>> projects wanting such a thing though. Unless someone tells me I'm
>>> wrong and we already have one would you be interested in seeing if
>>> Apple are open to such an arrangement?
>>>
>>>
>>
>> I'd recommend first very careful review of the licensing terms first, on
>> legal-discuss, to ensure that we're comfortable with any restrictions use
>> of their SDK brings.  This would also help with other potential
>> contributors who might have iOS apps they would like to contribute, but
>> whose current analysis suggests that the Apple terms are incompatible.
>
> nonsense
>
> These are the very same SDK tools that these very same Apache Committers already
> use on a daily basis.
>

The issue, of course, is not what you do with the Apple SDK in the
privacy of your own bedroom.  The question is about creating
dependencies for releases and the restrictions these bring to
downstream consumers.    If you want to just say those are questions
for the individual PMC's to resolve, then I'd agree, but I then note
that the IPMC is the PMC for podlings, so my point is in order.

> The only modulo here is that some have access through work.  Some purchase their
> own access.  Some have been comp'ed subscriptions individually or through other
> organizations.
>
> This simply makes the same tool for a committer free or discounted from what
> they already paid.  For example, I was an MSDN subscriber through work for some
> years, as a consultant for some years, took a break from my subscription on some
> other years.  Now, I'm using a subscription donated for ASF committers.  Nothing
> changed.
>
> Sure, you can have a discussion about whether some WizBang API introduces new
> licensing restrictions, platform lock-in, etc.  But we are NOT GOING TO BEGIN
> auditing the Oracle Developer Suite, the Microsoft Developer Network, the Apple
> Developer Network, the IBM HP VMware Google RedHat Citrix Adobe Amazon (OH GOD
> MAKE IT STOP!!!) developer tool program for every possible future quirk.
>
> There are real questions to be asked about specific tools and specific api's in
> the open source and closed source world and the projects which are affected need
> to do their homework and work with ASF legal to resolve ambiguity.  But any of
> these examples includes hundreds of tools and api's and sdk's which have no
> intersection with an ASF code base.
>
> If Jim works out some connections for ASF <> Apple and you use Apple then enjoy
> that perk, and otherwise, please EIGNORE?  Thanks :)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org