Special:Badtitle/NS90:Oral histories need to be locked. (1): Difference between revisions

From ETHW
(New page: We do not need another namespace. I will give you sysop privileges. Then it is your responsibility to protect the pages that you feel need protecting. Use these privileges cautiously. Do n...)
 
(reesponse to John's comments)
Line 1: Line 1:
We do not need another namespace. I will give you sysop privileges. Then it is your responsibility to protect the pages that you feel need protecting. Use these privileges cautiously. Do not delete pages without thinking it over once, twice or even three times. Also excercise your privileges wher eyou have responsibility, archives, oral histories, etc.
We do not need another namespace. I will give you sysop privileges. Then it is your responsibility to protect the pages that you feel need protecting. Use these privileges cautiously. Do not delete pages without thinking it over once, twice or even three times. Also excercise your privileges wher eyou have responsibility, archives, oral histories, etc.
I wasn't suggesting another namespace, just moving the oral histories from the main name space to another existing namespace. But If I, as a sysop can lock a page, that works too. Can I assume a sysop can still edit a locked page if need be?

Revision as of 18:47, 27 August 2008

We do not need another namespace. I will give you sysop privileges. Then it is your responsibility to protect the pages that you feel need protecting. Use these privileges cautiously. Do not delete pages without thinking it over once, twice or even three times. Also excercise your privileges wher eyou have responsibility, archives, oral histories, etc.

I wasn't suggesting another namespace, just moving the oral histories from the main name space to another existing namespace. But If I, as a sysop can lock a page, that works too. Can I assume a sysop can still edit a locked page if need be?