Confirmed users
3,816
edits
No edit summary |
|||
| Line 20: | Line 20: | ||
''**** 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.'' | ||
*** Opinion: Defining guidelines and expecting contributors to follow those guidelines is a good idea. However, throwing up road blocks to the community is a terrible idea. This isn't software code that requires a review process to protect an application. Just deal with inappropriate content as it shows up. Has it been an overwhelming problem so far? (Tracy) | *** Opinion: Defining guidelines and expecting contributors to follow those guidelines is a good idea. However, throwing up road blocks to the community is a terrible idea. This isn't software code that requires a review process to protect an application. Just deal with inappropriate content as it shows up. Has it been an overwhelming problem so far? (Tracy) | ||
*** Opinion: I'm with Tracy. I think that setting an expectation (by example, through the QMO blog etc of what is and isn't appropriate content is a far more useful and inclusive way to go about achieving the goal of "no inappropriate content" than putting up road blocks to contribution by design. Ideally we want self-policing community here. Not one more thing we'd have to manage. (ctalbert) | |||
* QA for rtl locales (henrik) | * QA for rtl locales (henrik) | ||
** 3 offical locales in the tree (Hebrew, Arabic, and Persian) and Afghanistan in beta state | ** 3 offical locales in the tree (Hebrew, Arabic, and Persian) and Afghanistan in beta state | ||