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 > >
