Context: A discussion in March (notes here) highlighted the need to have some basic guidelines (not a rigid framework) to define a 'spectrum of involvement' for events that Mozilla supports but doesn't ultimately control. These guidelines should be flexible, giving program leads the freedom to scale Mozilla support up or down, as appropriate for each event. These guidelines could include basic questions like:
does this event have a code of conduct?
is the style of the event participatory?
will outputs from the event be shared with open-source licensing?
will the event be an opportunity to use our tools or curriculum?
what will we be able to show for/report on our involvement?
@edrushka to write.
@thornet @Saallen @ldecoursy @jvallera @omnignorant to review.
Context: A discussion in March (notes here) highlighted the need to have some basic guidelines (not a rigid framework) to define a 'spectrum of involvement' for events that Mozilla supports but doesn't ultimately control. These guidelines should be flexible, giving program leads the freedom to scale Mozilla support up or down, as appropriate for each event. These guidelines could include basic questions like:
@edrushka to write. @thornet @Saallen @ldecoursy @jvallera @omnignorant to review.