• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Documentation frustrations
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Documentation frustrations


  • Subject: Re: Documentation frustrations
  • From: Scott Anguish <email@hidden>
  • Date: Sun, 10 Jul 2005 00:33:56 -0400


On Jul 9, 2005, at 10:16 PM, email@hidden wrote:

Also, I'd like to see less "issue a bug report" and more "yes, we understand". If Apple really have an internal process which requires a bug report before you're even allowed to listen to a problem, then we might as well all jump ship right now. This is bureaucracy people, and it's unnecessary.


Well, hang on. I know you have particular issues with this, but...

Nobody is ignoring what is said on the list. We listen closely. mmalc and I read and follow the lists for a number of reasons, none of which are really sanctioned as part of our day jobs. We read the list on our own time. We help people on our own time. We both care deeply about the community (that is, YOU GUYS), OS X and Cocoa development in particular. I know for a fact that mmalc and I often adjust our documentation based on our perception of what developers need from reading the lists. It makes our work better.

That said, it is much better if developers file bugs on _any_ issue rather than us attempting to determine the issues that are being had. If they're in the Radar system we can get time allotted to fixing these issue. We can track them through their various states of research. We can contact the developer again to ask for clarification, etc..

There are many, many times when I'd love to go all Harry Tuttle on a topic, but that typically isn't an option.


Recently we've made providing simple feedback on documentation much, much simpler by adding links at the bottom of every page that allows you to provide feedback without dealing with bugreporter. That has good and bad points, since it's a one-way communication. We can't ask questions to verify what exactly is meant (which is often required).


But, *but* *BUT*, I have said and will say again that I really like the way the docs are improving over time, given finite resources. Don't get miffed about the negative vibe from my emails and those of others - creative criticism is such by nature, but nonetheless well intended. Thank you for all that's been done so far.


Thanks. We're two of a larger group (Cocoa/Dev Tools), which is in turn part of a larger group (tech pubs) documenting all the APIs.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
References: 
 >Re: Documentation frustrations (From: email@hidden)

  • Prev by Date: Re: Documentation frustrations
  • Next by Date: Re: Documentation frustrations
  • Previous by thread: Re: Documentation frustrations
  • Next by thread: Re: Documentation frustrations
  • Index(es):
    • Date
    • Thread