+1 from me too. More and more developers seem to be accustomed to using GitHub Issues to ask for help, and redirecting them to a mailing list adds a barrier to participation.
Neal On Wed, Sep 29, 2021 at 2:32 PM Phillip Cloud <cpcl...@gmail.com> wrote: > I am +1 on steering users towards GitHub issues for support questions. I > think there's a lot of value in someone being able to use a search engine > to potentially find an answer to their problem. > > On Wed, Sep 29, 2021 at 2:16 PM Micah Kornfield <emkornfi...@gmail.com> > wrote: > > > We discussed briefly on the sync this morning, but I was wondering what > > people thought about removing the user@ mailing list in favor of either > > Github issues or discussions. We can try to mirror issues to an > > appropriate mailing list if archiving for posterity. > > > > Off the top of my head here are some pros/cons to approaches: > > > > Pros: > > - Github focuses on SEO which makes answers to one-off questions easier > to > > find. > > - Github issues seem to have roughly the same traffic as the user@ > > mailing. It would likely have more if we didn't steer people to user@. > > > > Cons: > > - This decentralizes user issues across the Arrow repos. > > > > > > - This is NOT a proposal to use github issues in place of JIRA (for the > > languages that are currently using JIRA). > > - This is NOT a proposal to make any modification to the dev@ mailing > list > > (I think centralization here is important). > > > > Thoughts? > > > > Thanks, > > Micah > > >
