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 >>> <rgard...@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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
