Policy document for curating user provided documentation wanted

Many thanks to jhodgdon for providing links that cleared up a lot of things for me.

First, there seems to exist a policy document that at least tells you who can edit what, and some guidelines for doing that. Great! This document is Commenting on community documentation pages and API pages. I think the title should be changed into in line with its true scope (for instance "Curating community documentation pages and API pages") - but the content is good.

It makes it clear that a community documentation page is a wiki, that anyone can edit, and that rolling comments into the page and then flagging the comment rolled in for deletion is the accepted procedure. I think this type of crowdsourcing for producing and maintaining documentation is good. So I've got no gripes here: Just leave this the way it is.

The policy page also tells you how to fix errors in the API documentation itself (file an issue to get it corrected at the source). Fine, this is the way it has to be. This is not something one would want to crowdsource.

However, the page fails to mention how to curate the user comments that come as part of the API documentation. And I think I know why: Since the API documentation pages is not a wiki, curating comments can not easily be crowdsourced, and core maintainers are too busy with more important tasks, so they're not going to do this.

However, having well curated API support documentation is critical for Drupal to be successful.

I also think that adopting the model already in place for curating community documentation comments, for API documentation comments, is possible, with just minor tweaks to the setup:

Two (alternative) suggestions:

1. For each API documentation page, create an auxillary API wiki page and link to it from the API documentation page. This page can start out as an empty page, but can be edited by anyone. The guidelines for curating it should be identical to the present guidelines for curating community documentation pages.
2. Enroll some users that are not trusted enough to be full webmasters, but in good standing in the community, and empower them to curate API documentation comments (i.e. make sure the example code snippets adhere to Drupal coding standards, delete comments that contains misleading information, merge similar examples, etc.)

The above suggestions of course imply that we want the documentation provided in the form of comments on the API pages to be curated. I strongly believe that we want this. The fact that a lot of people are turning to Drupal Answers @ Stackexchange (which is designed specifically for the purpose of crowdsourcing curation of documentation) indicates that Drupal.org need to become better at crowdsourcing curation of documentation to remain on the horizon as a good source of information for developers looking for information about Drupal.