Thank you Xuanwo, I agree with your broader point that using mailing lists for discussions makes it harder for many to participate (for example they need to already be subscribed to the mailing list to respond to a past comment / thread)
We actually do forward all github activity to a mailing list already[1] I admit to purposely sending messages like the one you mention[2] in order to generate spam /additional notifications and increase the chance of people seeing things I think are important. It is somewhat annoying for me to copy/paste the same message to a few places (slack/ discord and email) but I keeping the bar high means I do it only for the most important messages [1]: https://lists.apache.org/list.html?git...@datafusion.apache.org [2]: https://lists.apache.org/thread/nth58wnd61fngmtp7mfrmmskwpbvk75n On Sat, Mar 8, 2025 at 3:17 AM Piotr Findeisen <piotr.findei...@gmail.com> wrote: > Hi > > When amplifying notification loads we should be double cautious. > > If someone is subscribed to dev list and also participates in a github > discussion, how can they avoid having double notifications? > They can mute the dev list thread (if their mail client has such an > option), but this will also silence direct replies on the dev list, which > didn't come via github. > They can unsubscribe from github discussion, but they would need to > unsubscribe after every posting on the discussion. > > My perspective is that people will end up receiving double notifications, > which some can call spammy. > If we need to forward github to apache mail list, can this be a separate > mail list, just for github notifications, without expectation that DF > contributors are subscribed there? > > > Best > Piotr > > > > > > > On Sat, 8 Mar 2025 at 05:25, Denny Lee <denny.g....@gmail.com> wrote: > > > One of the nice things about using GitHub discussions (we've been doing > > this for awhile for MLflow, Delta Lake, and Unity Catalog for example) is > > that it's easier to organize and respond to issues with their own > threads. > > It's also easier from a SEO perspective where folks searching for a > > particular topic will often find it within a GitHub discussion. > > > > Saying this, some of my experiences with this experiment is that we > > actually do not want ML to GitHub because we still need to do votes and > > specific conversations that are easier by email. We've tried voting > > through GitHub discussions and honestly it's been a hit or miss at times. > > I'm sure others have had their experiences and perhaps they are different > > or better (or worse) than I have described. But I hope some of our > > experiences will help inform your decisions, eh?! > > > > > > On Fri, Mar 7, 2025 at 8:18 PM Xuanwo <xua...@apache.org> wrote: > > > > > Hi, everyone > > > > > > I'm starting this thread to discuss whether forwarding gitHub > discussions > > > to the dev list is a good idea. > > > > > > By enabling forwarding, we can treat GitHub discussions as a formal > > > channel since all messages will already be archived in the dev list. > This > > > means we can start discussions like [this one]( > > > https://lists.apache.org/thread/nth58wnd61fngmtp7mfrmmskwpbvk75n) > > > directly on GitHub. It also allows our PMC to manage releases directly > > > within GitHub discussions. Additionally, this could unlock the > potential > > to > > > automate release votes via GitHub Actions. > > > > > > This change would attract more contributors to join our discussions and > > > streamline our development workflow. The OpenDAL community has been > using > > > this approach for a while. Here’s how it looks: > > > > > > - Discussions: https://github.com/apache/opendal/discussions) > > > - Mailing list: > > https://lists.apache.org/list.html?d...@opendal.apache.org > > > > > > The setup is also easy, here is how opendal set it up: > > > > > > > > > > > > https://github.com/apache/opendal/blob/f9d90c0097f9bb4336418e1b0520658b630a8cbe/.asf.yaml#L39-L53 > > > > > > The only drawback is that we don't currently support forwarding ML to > > > GitHub, which means we still need to keep an eye on the mailing list as > > > well, and help forward that while needed. (I'm willing to help with > this) > > > > > > What do you think? > > > > > > Xuanwo > > > > > > https://xuanwo.io/ > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@datafusion.apache.org > > > For additional commands, e-mail: dev-h...@datafusion.apache.org > > > > > > > > >
