Re: [Moderator] Please hold off on iPhone SDK discussions until the rules are clarified later today
Re: [Moderator] Please hold off on iPhone SDK discussions until the rules are clarified later today
- Subject: Re: [Moderator] Please hold off on iPhone SDK discussions until the rules are clarified later today
- From: dreamcat7 <email@hidden>
- Date: Wed, 1 Oct 2008 18:38:57 +0100
Hmmm,
No iPhone - specific functionality to be discussed yet. But obviously
one important question to asking: How to partition the lists?
I hope that our existing CocoaDev moderater(s) will be given fully the
responsibility for such task and enough leeway to make their own
decision about it. Most people are under the assumption currently that
there will be simply (1) new discussion group added for the iPhone.
However there may actually a considerable overlap with people not
knowing which list to post to.
Actually i personally believe that this would be a good oppostunity
for the admins to consider entirely re-structuring the lists. For
example having a base list (for any such common frameworks), then
having an iPhone specific list. And then also having the Cocoa-Dev
list. As a side-effect that would make the existing Cocoa-Dev forum
more focussed on Cocoa development on the desktop computers. Do people
think this list should remain as general as it is, and is its size too
big or too small?
In many ways i believe the list very good as it is however many times
others have commented that the list is simply grown very big / much
bigger (and the time taken to read through means that a substantial
number of emails are missed / cannot be replied too). What are other
people's thought on this issue? And would the iPhone develpers benefit
or de at a disadvantage having figure out which of 2 lists to post to?
For me i believe that its no difficulty to use multiple lists (as i am
already subscribed to the Xcode list). I also believe that it would
the moderator's job easier to make each list smaller and fewer
guidelines would then be necessary on each list. Having fewer /
shorter guidlines is a good thing, because if the guidelines are too
long people simply dont read them. And a smaller list can self -
manage itself more effectively. However i also believe if you can have
a 'foundation list' then it might create a situation where more
experienced developers are on what is seen to become a more advanced
list and this could make it harder for newcomers to get as good
quality help and assistance from (those more talented Cocoa Developers).
But in either way - i know i shall be subscribing to all of the Cocoa-
related lists.
On 1 Oct 2008, at 17:49, CocoaDev Admins wrote:
That is one of the things I'm going to be clarifying.
for now, just wait to talk about anything on the list.
On 1-Oct-08, at 12:47 PM, James wrote:
Quick question, what do they mean by Released and Unreleased
software (just want the terminology correct).
Thanks,
james
On Oct 1, 2008, at 12:44 PM, CocoaDev Admins wrote:
For those of you who have seen
http://developer.apple.com/iphone/program
We have decided to drop the non-disclosure agreement (NDA) for
released iPhone software.
We put the NDA in place because the iPhone OS includes many Apple
inventions and innovations that we would like to protect, so that
others don’t steal our work. It has happened before. While we have
filed for hundreds of patents on iPhone technology, the NDA added
yet another level of protection. We put it in place as one more
way to help protect the iPhone from being ripped off by others.
However, the NDA has created too much of a burden on developers,
authors and others interested in helping further the iPhone’s
success, so we are dropping it for released software. Developers
will receive a new agreement without an NDA covering released
software within a week or so. Please note that unreleased software
and features will remain under NDA until they are released.
Thanks to everyone who provided us constructive feedback on this
matter.
-----
Please hold off on discussion of the SDK on this list until I can
verify how this is to be handled, and post another message.
Thanks
Scott
[Moderator]_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden