Hi All, My 2 cents on the matter, we have an application (Apache Hop) that is mainly used by non developers so most of our questions are not of a technical nature but more general hand-holding and troubleshooting. Though it should be possible to do this via email you end up with a tread of 20 mails back and forth "have you tried pressing x, and what variables have you used,...." These types of conversations are best handled synchronously so we were looking at the ASF slack at first. Our feeling was that the threshold to enter the ASF slack was too high. You either need an invite which is a single channel user or you need to be a committer and we would be excluding Chinese users as slack is blocked there.
Therefore we set up our own Mattermost server which is an open source slack alternative with no user limitations when managing your own infrastructure. Though some development stuff is also discussed there we then point to the developers list or add a summary there for further discussion. Cheers, Hans On Fri, 18 Feb 2022 at 01:58, Liu Ted <tedl...@yahoo.com.invalid> wrote: > We do need a modernized and/or complimentary communication channel. On > many choices we have, I am also for GitHub Discussions for the benefits as > Matt Sicker described. > Another factor to consider is there is a Great Firewall (GFW) in China > blocking many chat apps like Slack, Discord, Telegram, etc. unless using > VPN whereas GitHub Discussions is accesible, no VPN needed, which allows > and welcomes more easy communications with the foundation when adoption of > the Apache Way and its projects are booming in China. > Best regards, > Ted LiuASF member > > 2022 年 2 月 18 日周五 0:58，Matt Sicker<boa...@gmail.com> 写道： I like chat > apps, though they're definitely more suited to real-time > discussion. Note that the ASF Slack is a paid tier which has full > archives, so any PMCs using their own Slack instances could > potentially migrate to the ASF one. There may be more suitable chat > apps for development use (e.g., that have useful search functionality, > threading, etc.), though they're probably less popular than Slack or > Discord. > > As for the idea on GitHub Discussions, that sounds fairly interesting, > though I've never used it before. I do like mailing lists for projects > I'm more active in since I always check my email (but am not on GitHub > every day), though I can totally understand why other people prefer > using websites or apps instead (commonly because they don't like using > email or have their own preferred workflows). GitHub's integration > with email for its various notification things (where you can reply > directly to the email to have your message posted back to GitHub) > makes the concept a bit more of a two-way street similar to the git > repositories themselves. > > On Wed, Feb 16, 2022 at 7:26 PM Gilles Sadowski <gillese...@gmail.com> > wrote: > > > > Le mer. 16 févr. 2022 à 18:55, Mark Thomas <ma...@apache.org> a écrit : > > > > > > To repeat what I have written elsewhere on this topic in the past: > > > > > > Project communication channels should be: > > > > > > - Public. The decision making process should be open and visible to > > > everyone. It should also be easy for people to find. > > > > > > - Searchable. So anyone can look-up past discussions. > > > > > > - Asynchronous. To enable participation from a globally distributed > > > community. > > > > > > - ASF owned archive. So we always have access to past discussions. > > > > > > - Low overhead. Community members may not have access to powerful PCs > > > or high-speed and/or reliable internet. The lower the overhead of a > > > communication channel, the greater the potential for participation. > > > > > > - Usable off-line. Helps those with poor / intermittent / expensive > > > internet access and those who are off-line for other reasons (e.g. > > > traveling) > > > > > > > > > I wonder if something like matrix[1] could be a way to enable people to > > > communicate via their platform of choice whilst retaining our archived > > > mailing lists as the canonical view. > > > > > > Mark > > > > > > > > > [1] https://matrix.org/ > > > > Is INFRA investigating? > > > > Gilles > > > > >> [...] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > >
