Change Details

The current Code of Conduct draft includes a reference to a developer-relations{{@}}wikimedia.org email address. In addition to this, our team should be as approachable as possible, and offering an email address other than our personal ones might be a good idea anyway. Questions: * Is developer-relations good, or should we go for dev-rel, devrel? * Should this email be simply an alias redirecting to the email addresses of the DevRel team members, or should we get something more sophisticated, as an own inbox, a private group where emails are kept archived...?

The current [[ https://www.mediawiki.org/wiki/Code_of_conduct_for_technical_spaces/Draft | Code of Conduct for technical spaces draft ]] defines a process to report violations using an email address (two, if we count developer-relations{{@}}wikimedia.org). How would this work in practice? #OTRS is a good candidate to check, as it already handles confidential queues. Some questions considering the scenario defined in the current draft: * If we don't want to archive emails forever (i.e. because we don't want that new Committee members have access to all the history), then we need to find the right way to delete content. Would be possible to have a rule to delete automatically... emails of resolved tickets after i.e, 6 months? * If the Committee decides to delegate the resolution of a report to Developer Relations, could a ticket and related replies be copied or moved to the developer-relations queue? If the Committee or Developer Relations want a specific ticket and replies to be deleted, they could request to an OTRS admin, who would only need the ticket number to delete it, without accessing to its content. Anything else? (Questions in the initial task, before changing its scope:) * Is developer-relations good, or should we go for dev-rel, devrel? * Should this email be simply an alias redirecting to the email addresses of the DevRel team members, or should we get something more sophisticated, as an own inbox, a private group where emails are kept archived...?

The current Code of Conduct draft includes a reference to a developer-relations{{@}}wikimedia.org email address[[ https://www.mediawiki.org/wiki/Code_of_conduct_for_technical_spaces/Draft | Code of Conduct for technical spaces draft ]] defines a process to report violations using an email address (two, if we count developer-relations{{@}}wikimedia.org). In addition to this,How would this work in practice? our team should be as approachable as possible#OTRS is a good candidate to check, and offering an email address other than our personal ones might be a good idea anywayas it already handles confidential queues. Questions:Some questions considering the scenario defined in the current draft: * If we don't want to archive emails forever (i.e. because we don't want that new Committee members have access to all the history), then we need to find the right way to delete content. Would be possible to have a rule to delete automatically... emails of resolved tickets after i.e, 6 months? * If the Committee decides to delegate the resolution of a report to Developer Relations, could a ticket and related replies be copied or moved to the developer-relations queue? If the Committee or Developer Relations want a specific ticket and replies to be deleted, they could request to an OTRS admin, who would only need the ticket number to delete it, without accessing to its content. Anything else? (Questions in the initial task, before changing its scope:) * Is developer-relations good, or should we go for dev-rel, devrel? * Should this email be simply an alias redirecting to the email addresses of the DevRel team members, or should we get something more sophisticated, as an own inbox, a private group where emails are kept archived...?