Scoop -- the swiss army chainsaw of content management
Front Page · Everything · News · Code · Help! · Wishlist · Project · Scoop Sites · Dev Notes · Latest CVS changes · Development Activities
An alternative to the edit queue? Feature Requests
By em , Section Wishlist []
Posted on Thu Jun 06, 2002 at 12:00:00 PM PST
I just had a look at the queue on Kuro5hin, and some other loser has again submitted a hopeless story into edit. Which led me to remember some thoughts I've had on edit queues.

I think there are two main problems with the edit queue as currently implemented:
  1. Submissions stick around for a while without being votable. This is greatly empowers the scourge of the web: crapflooders, spammers and trolls.
  2. The edit period is very short. It can't be made too long, because then stories can stick around on the queue forever. But the short period limits the amount of time for people to give comments that the author can incorporate. Also, it forces the author to stick around for two hours after submission, continuously reloading and reediting if she wants to benefit from edit.

    In addition, I've already gotten flamed by authors, along the lines of "it's your fault that such and such thing in my story is wrong, because you didn't point it out while it was on edit!" Yes, this is a really lame flame, but there is a point. The edit period is very short.

The alternative: author drafts

My proposal is that stories still under edit don't belong in the queue. Rather, each account can be associated with a draft area, accessible from the account info page. Essentially, the "Request editorial feedback before voting" button, instead of showing the story under the queue in edit mode, just makes it visible under the submitting account's draft area. The article sticks around in the draft area for editing, until the author decides to submit it to the queue.

Articles in draft area would be editable as drafts currently are, and only allow editorial comments. Further limitations can be imposed:

  1. The number of drafts per author can be limited. E.g., an author could be allowed to have just one draft at a time
  2. The amount of time an article can spend in draft can be limited too, for example, to 5 days. At the end of this period, a cron job could e.g. mail the text of the draft to the author and delete it from the site.
The idea is that the process should go as follows:
  1. Author submits draft.
  2. Author circulates draft for comments. This can be done through a diary entry, or there could be a "Current Drafts" page where people can go look at drafts.
  3. Author has a longer amount of time to incorporate comments (e.g. it can go up from 2 hours to 3 days). Likewise, others can have a longer time to comment.
  4. Finally, author submits draft to queue, where it is immediately voteable.
< Problem on OpenBSD 3.0 | Multidimensional Mojo >

Menu
· create account
· faq
· search
· report bugs
· Scoop Administrators Guide
· Scoop Box Exchange

Login
Make a new account
Username:
Password:

Related Links
· Kuro5hin
· More on Feature Requests
· Also by em

Story Views
  34 Scoop users have viewed this story.

Display: Sort:
An alternative to the edit queue? | 1 comment (1 topical, 0 hidden)
I think this is a wonderful idea (none / 0) (#1)
by theantix on Mon Jun 10, 2002 at 08:34:17 AM PST

I'm going to do some investigation in this area, but I don't think it would be too difficult to accomplish under the existing edit queue framework. Thanks for sharing this idea, I think it has a lot of potential.



An alternative to the edit queue? | 1 comment (1 topical, 0 hidden)
Display: Sort:

Hosted by ScoopHost.com Powered by Scoop
All trademarks and copyrights on this page are owned by their respective companies. Comments are owned by the Poster. The Rest © 1999 The Management

create account | faq | search