Dear sime,
I think that using your common sense and using common courtesy is all
that's needed. Maybe you have more access permissions than I do, but
when I'm editing a page, I can't even tell who the original author is.
So, for most of the doc editors, I think that notifying the original
author when rewriting a page is not a viable option. I think in
marginal cases open a forum topic or issue, or post to this list. For
obvious spam or unhelpful/badly written stuff, just kill it.
-Peter
On 9/3/06, sime <info@xxxxxxxxxx> wrote:
Hi Liza
I like the approach. Can I play devil's advocate?
blogdiva@xxxxxxxxxxxxxxxxxx wrote:
> In the interest of good developing good cooperation and
> communications practices :
>
> (1) more than two people should review queued documentation. Two
> heads work better than one.
This is a good idea, but do we have enough resources? Reading the
maintainer's page, I get the impression that I should rely on common
sense to keep things moving. (Excluding major rewrites of the handbook
of course.)
>
> (2) if the documentation is so-so, both will annotate and send it
> back with comments to the author, giving the author the option of
> --changing the documentation themselves OR
> --publishing it as a forum topic with a request for review by the
> community
I like this, but the best way is to use the author's contact form, which
is a bit clunky. I feel like the "edit and wait for the screams" option
is more efficient.
>
> (3) a notification alert should go out to all authors whose work has
> been published in the documentation section of drupal.org. Actually,
> I believe the same should be an option for all forum discussions.
> With comments alerts (notification module, btw) going immediately to
> the author, hopefully Drupal.org will be ensuring quick response to
> issues and/or maintenance of the site.
Just clarifying. This would require changes to the drupal.org installation?
>
> Best,
> liza sabater
--
Pending work: http://drupal.org/project/issues/documentation/
List archives: http://lists.drupal.org/pipermail/documentation/
--
Pending work: http://drupal.org/project/issues/documentation/
List archives: http://lists.drupal.org/pipermail/documentation/
|
