Delay edit/create perms for new users

Is time really the answer, or is it simple education. Gradually revealing features makes a lot of sense. Perhaps it should be triggered on other activities like browsing a certain number of pages, or commenting without getting your comments unpublished.

I like the thinking.

Kieran

+1

+1

+1 with the option to override the delay period. For example: new documentation authors at a sprint shouldn't need to wait especially if they have in-person coaching.

This makes sense to me - ideally we'd want a new role which everyone gets put into after a certain amount of time or activity. This would also allow for demoting people from the role rather than outright blocking their account in specific situations (can't think of any off-hand, but you never know).

I did a bit of this while working at Achieve Internet, and we had decided that if a module were to assign someone a certain role based on their accomplishments such as posting 8 times in the forums + browsing 20 handbook pages, it wouldn't preclude the site admins from un-assigning that role at a later time. The only gotcha is that the module has to remember that it's assigned a role to a user one time, and it shouldn't do it again. You wouldn't want the module to accidentally re-assign the role to a user who'd been "cut off" by an admin.

Oh, and because the module is assigning an rid to a uid, there's no reason that an admin can't instantly 'promote' a brand new user account to superstar status. The module will come along and re-assign that same role after a certain period of time, sure, but that doesn't hurt anything because its just like updating the database table to set integer to 1 WHERE integer equals 1.

+1

I don't see how people who are brand new at Drupal.org can be expected to make quality contributions to reference books. After we acquire some background, then turn us loose.

Without data on how big the bad-docs/edits-by-new-users phenomenon is, and also some detail on what kind of bad (is it spam? or bad quality content?) -- then I vote -1 on this.

If it is spam... isn't Mollom a better solution?

If it is poor quality content, I'm not sure an automated system based on a delay of privileges is the best way to deal with it. Seems like the need has to be very high in order to add a module to Drupal.org.

But in short, I think the response should follow the data of what's going on... which I'd love to see.

p.s. I wouldn't put it past Dries B., within 5 years, to have Mollom actually find the poor quality content as well as the spam :) ... what smart people can do these days...

Shai

Thanks for the page reference to the new docs stats.

(I just posted an issue to webmasters suggesting to add a timestamp to that page for when the week ending was for the data we are looking at. Otherwise the "last revised" timestamp makes the page look broken or outdated. Do you think Mollom would pick up the spam? The "test pages"?)

Regarding the new experiment, is there data being collected on page edits in addition to page creation?

Shai

Oops, I saw you posted on the home page article the URL to track new updates. Thanks.

Shai

@add1sun as I have already nod on this, I can add that it's a good Idea limiting to build new page to its own section.
I mean this will a bit discourage occasional vandalism. Just thought about the fact that every member have it's preference and it may possible to have something like book-access.module that may allow to choose between Handbook preferences? It's just an Idea in connection with the concept that New-Member may choice their preferred field and this will give them automatically the right access for editing new page in their chosen preference. Anyway this are some consideration.

Cheers

I do believe that this is fixed (and has been.)