Firefox/Projects/Personas Uplift Exploration/Legal Meeting 10.13.09: Difference between revisions
Jump to navigation
Jump to search
(Created page with ''''Problem Trying to Solve: ''' 1. Current process (see diagram below) does not Scale Well 2. Ensure compliance with DMCA [[Image:Current_process_flow.png|650x150px|cur…') |
No edit summary |
||
| Line 1: | Line 1: | ||
'''Problem | '''Problem to Solve: ''' | ||
1. Current process (see diagram below) does not | 1. Current process (see diagram below) does not scale well; ancipated approval demand for 3.6 will exacerbate | ||
2. Ensure compliance with DMCA | 2. Ensure compliance with DMCA | ||
[[Image: | [[Image:Current process flow.png|650x150px|current process for approval]]<br> | ||
'''<br>''' | '''<br>''' | ||
'''Discussion''' | '''Discussion''' | ||
*how can we source community to scale demands of 3.6? | *how can we source community to scale demands of 3.6? | ||
*implement flagging system so that community members can flag inappropriate content | *implement flagging system so that community members can flag inappropriate content | ||
*open questions: | *open questions: | ||
#how to avoid maliciousness (flagging just to screw with other users), | #how to avoid maliciousness (flagging just to screw with other users), | ||
| Line 20: | Line 20: | ||
*Potential Wire for Flagging: | *Potential Wire for Flagging: | ||
[[Image:Overview of flagging other infringing model.png|576x159px]]<br> | |||
<br> | |||
'''Next Steps''' | |||
<u>Catherine</u> will draft the following and send to group in advance of meeting: | |||
*refined, clearer language for upload flow | |||
*refined, clearer language for upload flow | |||
*representation language and approach | *representation language and approach | ||
*repeat offenders policy and approach | *repeat offenders policy and approach | ||
Suneel will draft the following and send to group in advance of meeting: | <u>Suneel</u> will draft the following and send to group in advance of meeting: | ||
*flagging rules | *flagging rules | ||
*maliciousness | *maliciousness | ||
*how many before review is needed | *how many before review is needed | ||
*super users | *super users | ||
*verification flag | *verification flag | ||
*education on verified content<br> | *education on verified content<br> | ||
<br> | |||
Update since meeting: Legal is auditing current process and may have recommendations that shift this process in different direction. Meeting with legal on 10/20 for their recommendations. | Update since meeting: Legal is auditing current process and may have recommendations that shift this process in different direction. Meeting with legal on 10/20 for their recommendations. | ||
Latest revision as of 20:48, 20 October 2009
Problem to Solve:
1. Current process (see diagram below) does not scale well; ancipated approval demand for 3.6 will exacerbate
2. Ensure compliance with DMCA
Discussion
- how can we source community to scale demands of 3.6?
- implement flagging system so that community members can flag inappropriate content
- open questions:
- how to avoid maliciousness (flagging just to screw with other users),
- what rules will apply (strike system vs. one time and you're out)
- Potential Wire for Flagging:
Next Steps
Catherine will draft the following and send to group in advance of meeting:
- refined, clearer language for upload flow
- representation language and approach
- repeat offenders policy and approach
Suneel will draft the following and send to group in advance of meeting:
- flagging rules
- maliciousness
- how many before review is needed
- super users
- verification flag
- education on verified content
Update since meeting: Legal is auditing current process and may have recommendations that shift this process in different direction. Meeting with legal on 10/20 for their recommendations.