Re: Wiki access warning?
От | Stefan Kaltenbrunner |
---|---|
Тема | Re: Wiki access warning? |
Дата | |
Msg-id | 568C30B2.20205@kaltenbrunner.cc обсуждение исходный текст |
Ответ на | Re: Wiki access warning? (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>) |
Ответы |
Re: Wiki access warning?
|
Список | pgsql-www |
On 01/04/2016 10:06 PM, Stefan Kaltenbrunner wrote: > On 01/04/2016 09:58 PM, Alvaro Herrera wrote: >> Stefan Kaltenbrunner wrote: >>> On 01/04/2016 09:52 PM, Stephen Frost wrote: >>>> Josh, >>>> >>>> * Josh Berkus (josh@agliodbs.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. > > yeah - but that is not nearly enough, the wiki really is for the wider > community and we need to find a more suitable approach... I have now added a big boilerplate warning to the entire wiki on the issue - it is certainly not the "best" solution but it at least should give people a hint on where to ask... Stefan
В списке pgsql-www по дате отправления: