I might be biased, but I think Discourse (https://discourse.mozilla-community.org) seems to check all the boxes. It's more forum-style but also works as a fancy mailing list.
On 09/10/15 23:48, Rob MacDonald wrote: > Hi everyone... > > We’re trying something new here and learning as we go. So we’re > definitely open to ideas on how we can improve our process and encourage > transparency. > > We chose Slack because it works well for team collaboration across time > zones and allows us to organize topics and documents based on focus > areas. We also had success in working with it previously. If there are > other suggestions, we’re definitely open to it. > > An additional focus next week will be updating the Alopex wiki to share > status and direction to date. We’ll send a message to this list as soon > as those updates are available. > > Thanks! > Rob > > On Fri, Oct 9, 2015 at 2:45 PM, Etienne Segonzac <[email protected] > <mailto:[email protected]>> wrote: > > > On Fri, Oct 9, 2015 at 10:49 PM, Fabrice Desré <[email protected] > <mailto:[email protected]>> wrote: > > On 10/09/2015 01:37 PM, Etienne Segonzac wrote: > > > > On Fri, Oct 9, 2015 at 8:44 PM, Fabrice Desré <[email protected] > <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>>> wrote: > > > > Whoa. So people complained about using a dedicated IRC channel > and the > > answer is a private slack instead? > > > > > > Maybe complaining isn't the most efficient form of feedback after > all then. > > The point was that existing channels were good enough. Isn't > that true? > > > I don't really have an opinion. > The point is: we want designs to be shared and discussed earlier in > the process. > > They could be tweeted by a @Horse_B2G account and it would *still* > be progress! > > I'm perfectly fine with posting on a mailing list if the big > attachments aren't getting constantly dropped. > But the feedback should not be focused on what *not* to do. > > > > > And by the way, > > > > On Fri, Dec 12, 2014 at 11:06 PM, Fabrice Desré > <[email protected] <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>>> > wrote: > > I don't know why we chose slack, and I was initially not really > on board > > either (irc's good enough, right?). But after using it since > last week I > > like it. It's actually pretty efficient at keeping track of > proposals > > and getting people feedback. Way better than gdocs and etherpads > > scattered around, or unmaintained wiki pages, or semi-private > email > > thread. > > > > > > * * * > > Nice out of context quote. That was during v3 ideation which was not > open to external contribution. > > As an internal tool it's not bad, but > it's terrible if we want to encourage community contribution. > Even read > access is impossible. > > > Apparently you need to request an invite, that's not "impossible". > That's friction. > (And way less friction than attending a vidyo meeting BTW., but > sadly nobody is arguing against those ;) ) > Maybe removing that friction is not our priority right now, maybe > it's premature optimization. > > How are we going to make a community-driven product if we can't even > collaborate between teams? > > Whether you want it or not we're lead by example, Fabrice, and > sharing and shipping should be facilitated and celebrated! > "You're doing it wrong"-type comments are not the way to go. > It doesn't cost much to remember that everybody is trying to do > things right, and that a little encouragement in the right direction > goes a long way. > > _______________________________________________ > dev-fxos mailing list > [email protected] <mailto:[email protected]> > https://lists.mozilla.org/listinfo/dev-fxos > > > > > -- > ------ > Sr. UX Designer > Firefox OS > > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos > _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
