So, as Corbin and I.S. mention, there are two ways to submit bugs on documentation.

- bugreporter.apple.com
- the feedback button on documentation pages.

Both will get the bugs to the proper people. There are situations when one option is better than another.

Small bugs that qualify as typos (spelling errors, duplicated words, its vs it's, etc.) can easily be reported using the feedback method. In fact, I'd urge you to use that mechanism for those types of reports. Typos will get fixed faster this way.

But if you're asking for a significant clarification of something, it can be __very__ useful to actually submit a bug using bugreporter.aple.com. That allows the Developer Publications engineers (myself and my cohorts) to contact you if necessary for clarification. You'll also get a notification when the documentation gets fixed, so you can verify that it now covers what you thought it didn't.

So, both are valid. Feedback button is definitely one way. bugreporter has the ability to be two way (despite the naysayers)

Just one further note.

All the reference and conceptual documentation for the frameworks and technologies are written in house by Developer Publications engineers. We have access to the source for investigation and, even better, engineers like Corbin who know it inside and out to back us up.

On 24-Mar-09, at 6:54 PM, Corbin Dunn wrote:

Good question!

On Mar 24, 2009, at 3:46 PM, I. Savant wrote:

Corbin:

On Mar 24, 2009, at 6:40 PM, Corbin Dunn wrote:

I should mention that it is very beneficial to log bug requests at bugreporter.apple.com requesting clarification on any point with NSTableView/NSCell that is difficult to figure out from the existing documentation.

Is this the preferred documentation feedback method or is it better to use the feedback forms at the bottom of the documentation pages? Or do they both go to the same place?

I think you are correct that the best way is to use the feedback forms. I'm verifying that is correct, and if I hear otherwise I'll post back. Bugreports are definitely okay too, but the documentation feedback may get routed to the right place faster.

corbin



_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to