Further to Peter's point, I think this betrays a misuse of Slack, IRC and other synchronous communication platforms. We have staff and volunteers distributed across the world, and we can expect neither to be active 24 hours a day. Trawling through past conversations isn't a productive use of anyone's time.
One discussions have been had, and decisions made, they should be summarised on the appropriate asynchronous platform (be that Discourse, Bugzilla, GitHub, etc.) Leo On 16/08/18 21:44, Peter Saint-Andre via governance wrote: > On 8/16/18 3:52 AM, Dão Gottwald via governance wrote: >> The use of Slack at Mozilla has bothered me for a while. So far I managed >> to pretty much ignore Slack. I feel left out sometimes but it hasn't been a >> big deal, as far as I can tell. (Of course, since I don't have an account, >> I don't know how much exactly I've been missing.) >> >> Now this issue came up again in >> https://bugzilla.mozilla.org/show_bug.cgi?id=1460248#c18 when a user asked >> a question about a UX design that I implemented. These kind of discussions >> in closed bugs usually don't go anywhere, so I asked the user to take it to >> a mailing list or IRC. The user posted to #ux and never got a response. >> This can happen in channels with low usage, but Timvde let me know that >> this IRC channel has effectively been dead since the team has moved to >> Slack. > Aside from the question of Slack vs. IRC (or other), we might want to > address the multiple points of failure in this scenario (do a better job > of monitoring conversations in closed bugs, shut down dead channels, > update our documentation about communication venues, etc.). > > Peter > > > > > _______________________________________________ > governance mailing list > governance@lists.mozilla.org > https://lists.mozilla.org/listinfo/governance _______________________________________________ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
