From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-www(at)postgresql(dot)org |
Subject: | Re: Wiki access warning? |
Date: | 2016-01-04 20:58:33 |
Message-ID: | 20160104205833.GA218428@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Stefan Kaltenbrunner wrote:
> On 01/04/2016 09:52 PM, Stephen Frost wrote:
> > Josh,
> >
> > * Josh Berkus (josh(at)agliodbs(dot)com) wrote:
> >> Apparently all wiki accounts have been set to read-only mode as an
> >> antispam measure. We should probably post a notice on the wiki home
> >> page, and maybe on pgsql-general/announce about this, so that people
> >> aren't surprised when they can't edit the wiki.
> >
> > Not all of them. Dave and Joe (as I recall) spent quite a bit of time
> > going through and setting up the right permissions for everyone who had
> > edited the wiki recently who weren't identified as spammers.
> >
> > Thus, the change should only impact those who haven't edited it recently
> > and who are now trying to. I agree that adding something to the
> > homepage letting people know that they need to be granted membership in
> > the Editor group to edit pages would be good.
>
> exactly - accounts that have recently edited the wiki have been granted
> the "editor" priviledge. We are still discussing on how to improve the
> situation but the mediawiki capabilities in terms of moderation are limited.
Simple idea: everyone invited to a developer meeting should get editor
privs automatically.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2016-01-04 21:00:11 | Re: Wiki access warning? |
Previous Message | Stefan Kaltenbrunner | 2016-01-04 20:55:09 | Re: Wiki access warning? |