Bug 5039 - Give wiki admin permissions to doc team leaders
Summary: Give wiki admin permissions to doc team leaders
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: wiki.mageia.org (show other bugs)
Version: trunk
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-21 09:44 CET by Oliver Burger
Modified: 2014-05-08 18:06 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Oliver Burger 2012-03-21 09:44:28 CET 
I'm currently trying to keep the wiki clean.
But all I can do is mark pages for deletion, so boklm can delete them because he is the only admin/bureaucrat in our wiki.

Would it be possible to promote the doc team leaders?

This would be
- marja
- obgr (the wiki didn't like the "_" in obgr_seneca
Oliver Burger 2012-03-21 09:45:38 CET

CC: (none) => marja11
Assignee: mageia-webteam => sysadmin-bugs

Comment 1 Marja Van Waes 2012-03-21 12:00:58 CET 
(In reply to comment #0)
> I'm currently trying to keep the wiki clean.
> But all I can do is mark pages for deletion, so boklm can delete them because
> he is the only admin/bureaucrat in our wiki.
> 
> Would it be possible to promote the doc team leaders?
> 
> This would be
> - marja
> - obgr (the wiki didn't like the "_" in obgr_seneca

Changing the summary, because this is about the wiki and not about the forum ;)

Summary: Give forum admin permissions to doc team leaders => Give wiki admin permissions to doc team leaders

Comment 2 Nicolas Vigier 2012-05-26 11:05:06 CEST 
Oops, I missed this bug. I added you (marja and obgr) to the Administrators group, so you should now be able to remove pages directly.

And I have done the same on german wiki for obgr account.

Status: NEW => RESOLVED
CC: (none) => boklm
Resolution: (none) => FIXED

Nicolas Vigier 2014-05-08 18:06:03 CEST

CC: boklm => (none)
Note You need to log in before you can comment on or make changes to this bug.