Confirmed users
6,361
edits
| Line 17: | Line 17: | ||
*** ''discussion'' - should have a vetting process for community members who want admin access. '''(marcia)''' and '''(tomcat)''' to work on a guide to demonstrate they are behaving properly. | *** ''discussion'' - should have a vetting process for community members who want admin access. '''(marcia)''' and '''(tomcat)''' to work on a guide to demonstrate they are behaving properly. | ||
''**** We have not yet created a policy document. We also need to figure out what to do with Product Community leads and whether or not they should have product specific badges?'' | ''**** We have not yet created a policy document. We also need to figure out what to do with Product Community leads and whether or not they should have product specific badges?'' | ||
**** '''(marcia, timr)''' to sit down and talk about how to draft this up before the workweek. | |||
*** ''discussion'' - for content issues, should we review what content is posted before allowing it on QMO? '''(marcia)''' and '''(tomcat)''' to work on a policy guide. | *** ''discussion'' - for content issues, should we review what content is posted before allowing it on QMO? '''(marcia)''' and '''(tomcat)''' to work on a policy guide. | ||
''**** Content Policy guide has been created and reviewed by Tomcat. Posted to QMO on Monday. Because there is no way to know daily what content has been added, as Owner of this area I feel more comfortable having a process where we can review content. This was done informally via email in one case with stephen and a community member. This is just formalizing that process.'' | ''**** Content Policy guide has been created and reviewed by Tomcat. Posted to QMO on Monday. Because there is no way to know daily what content has been added, as Owner of this area I feel more comfortable having a process where we can review content. This was done informally via email in one case with stephen and a community member. This is just formalizing that process.'' | ||