Draft hypothesis:
If we investigate the viability of Discord on the PII front and set up a public Discord server, bridge it to select Slack and IRC channels, and invite staff and community to test it, we’ll know whether Discord is a viable solution for incident response and understand the associated costs.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T382158 Towards a unified chat solution for essential operational processes and emergent incidents | |||
| Open | None | T382160 Test Discord | |||
| Open | BBlack | T382162 Investigate the viability of Discord with regards to handling PII and sensitive information |
Event Timeline
Comment Actions
https://foundation.wikimedia.org/wiki/Resolution:Wikimedia_Foundation_Guiding_Principles
As an organization, we strive to use open source tools over proprietary ones, although we use proprietary or closed tools (such as software, operating systems, etc.) where there is currently no open-source tool that will effectively meet our needs.
Comment Actions
Hi @Dzahn and @Aklapper. I would like to keep the focus of this task on the testing of Discord. I see your note about our open source guiding principle and the dislike token for this task. I will reach out to to you separately to provide other pathways for engaging with the logic behind introducing this task.
Comment Actions
Thanks! :) I likely won't have time to engage in private fragmented conversations about non-secret topics; I'd be very happy to read a public wiki page to learn about the underlying problem though to educate myself and reconsider initial feelings.
Comment Actions
I am merely pointing out the guiding principles. Of course those could be updated if they don't seem to be adequate anymore or for this case.
I am also not making a judgement call if in this case there is" currently no open-source tool that will effectively meet our needs" or not.
My intention is only to point out the potential for conflict here. There is no need to convince me as an individual for or against a specific path.
Comment Actions
@Aklapper we will update the parent task when the link to public documentation is available. In the meantime, as staff you can have access to internal thinking and deliberations given that this work was part of the previous annual plan for the organization.
@Dzahn ok. thanks. I confirm that we have the WMF guiding principles in mind and heart as we work on this task (if prioritized) and the parent task. It is my understanding that testing Discord (the scope of this task) does not have a conflict with the guiding principle "freedom and open source".