[documentation] Needed: a system for improving the text in core

[O Govinda]

Let's start with a simple assumption:

The better the text in the Drupal interface and the core help text, the more
usable Drupal will be.

Ok. Now. . . 

What seems to be a problem is that when you post a fix or enhancement for
core text--whether as a message or a patch--your post lands in a pile of
issues attended to mainly be people whose expertise and interest lies in
code. Your post, therefore, is likely to get lost. 

Ideally, your post would be seen not by coders per se but by people with an
understanding of Drupal, strong skills in English and an interest in
documentation--that is, people who can actually evaluate the quality and
usefulness of your text. 

Assuming your text passes muster, someone trusted enough by the Drupal
maintainers should then give it a thumbs up, and the coding people should
check your patch for correct coding and commit it. 

Otherwise, your post is likely to languish till an RC-1 makes it too late to
commit--and then simply be forgotten. 

Perhaps this issue is part of what sepeck's post about DocBook is meant to
address. I don't really know. 

I do think, however, that the issue deserves some attention. Whatever the
workflow, a robust system for improving core text could help users a lot. 

Cordially, 
O Govinda
www.jswami.info
-- 
View this message in context: http://www.nabble.com/Needed%3A-a-system-for-improving-the-text-in-core-tf4274312.html#a12165903
Sent from the Drupal - Doc mailing list archive at Nabble.com.