Hi Jarek, Le dim. 27 févr. 2022 à 23:11, Jarek Potiuk <ja...@potiuk.com> a écrit : > ...I use slack for async communication a lot. Including > underrepresented in IT Outreachy (https://www.outreachy.org/) interns that > I am mentoring - from India, Peru and Nigeria that I am interacting with > them over the last 3 months of their internship Most of that is > asynchronous because I live in Poland which is about 12 hours apart from > both India and Peru. And we have different holidays schedules...
I think what you're describing is 1:1 async communications, or "1 to very small group". This is much easier to manage on any channel than "talking to the group" which is IMO required for Apache-style development. What I mean is: -Everybody sees the topics of all conversations fly by -It's easy to ignore specific or most conversations -It's easy to catch up after N days of absence while the rest of the team has been active, by quickly skimming the thread's subject lines -It's easy to use Precise Quoting in replies to enable deep conversations To me, the lack of first-class discussion threads, including a subject line, in most chat-style channels makes it hard to support that style. -Bertrand --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
