For background on this issue/decision, see http://lists.drupal.org/pipermail/documentation/2008-November/006351.html.

We will create a new book on d.o that will be used as a default location for all new handbook pages created by regular auth users that don't have elevated rights. Basically this should be a matter of adding a check for role and, if not elevated, take over the book parent selector and set it to the holding book. We should probably also do a set message to tell people it was created and put in the holding book until it is reviewed by the doc team.

It would be nice if we could grab the original parent before we switch it and tack that on to the node somewhere so reviewers know at least where someone intended it to go, but I'm not really pressed about that right now.

Comments

add1sun’s picture

add1sun commented
Project: Drupal.org customizations » Documentation
Component: Code » Other documentation issues

I know that this was "decided" but I am going to move it back for discussion in light of larger changes, redesign, etc. and the best way to implement "moderation." Before we actually do this I want to make sure we can't come up with a smoother solution in the redesign.

leehunter’s picture

leehunter commented

Is the purpose to check and place each page or is it just to weed out spam and tests?

If it's the latter, I'm wondering if it would make sense to just do this for the first posting or maybe have some easy way of freeing the person from moderation if it's obvious the contributor knows what they're doing.

add1sun’s picture

add1sun commented
Issue tags: +planning sprint

Well, it is to accomplish both: checking for spam/tests, but also making sure things are placed properly in the book. The idea being that for new pages we would exert more editorial control. I would like to see a more sophisticated solution than the original one proposed which is why I moved it "down" from a code request.

Adding the planning tag to discuss next weekend.

MGParisi’s picture

MGParisi commented
Version: » 6.x-1.x-dev

Obviously this isn't implemented

Which is good. Why does adding a new document and modifying a current document pose different risks to spam and poor content? I say that bad documentation is better then no Documentation, and as a Doc member that is going through 200+ posts in the Queue, I don't want every decision I make to have to be approved by a higher authority! And after editing over 150 posts so far, I doubt anyone wants to monitor all of mine!

MGParisi’s picture

MGParisi commented
Version: 6.x-1.x-dev »
Status: Active » Closed (won't fix)

I think this issue has been debated to death, here and on IRC... and though we would love to have the ability to approve changes, the task to do this is monumental, and no one can maintain this. Lets face it, its hard enough for people to respond to the Documentation queue or make new documents...

In addition I have heard that Dries himself has specifically closed this topic, and untill Dries himself and a member of the Docteam that has no life but to go through these documents stands up. Great idea, but lets face it... never going to happen...

I am going to act as Document Czar (since no one else has stood up) and close this discussion with a "won't fix"...