+1 for issues because I believe it would lower the barrier for entry. I'm +0 on discussions, they can work but would require more active curation / labeling as they cannot be closed so an "answered / unanswered" label would probably be needed.
> I think I already get e-mails from issues but > have them filtered out with the rest of other github messages, I'm not sure > if it is easy to split them out. Issues will absolutely be lost in the flood of notifications you would get from watching the arrow repo. However, you can do a custom watch that targets only issues. This may be an alternative for those that prefer an issue-like workflow. For me personally, I've monitored issues in the Zulip feed for Github. That being said I went ahead and turned on an issues-only watch to try that out. > I took a few minutes to browse the archives [1]. It seems to me that > the user@ list is working extremely well. People get answers quickly, > problems are converted into JIRA cases, and the discussion often > references existing information sources. I would add we have a pretty decent traffic rate for github issues today. We get a fair number of issues opened even though our issue template says "Please ask questions at u...@arrow.apache.org". On Wed, Sep 29, 2021 at 9:37 AM Julian Hyde <jh...@apache.org> wrote: > > I'm not for or against this proposal. > > I took a few minutes to browse the archives [1]. It seems to me that > the user@ list is working extremely well. People get answers quickly, > problems are converted into JIRA cases, and the discussion often > references existing information sources. > > I want to thank all of the community members who answer questions. No > doubt it takes considerable time and effort. > > Julian > > [1] https://lists.apache.org/list.html?u...@arrow.apache.org > > On Wed, Sep 29, 2021 at 2:14 PM Phillip Cloud <cpcl...@gmail.com> wrote: > > > > On Wed, Sep 29, 2021 at 3:08 PM Antoine Pitrou <anto...@python.org> wrote: > > > > > > > > Le 29/09/2021 à 20:51, Micah Kornfield a écrit : > > > >> > > > >> Cons: > > > >> - Github is a not a mailing-list and does not integrate well in a > > > >> normal > > > >> e-mail workflow. > > > > > > > > > > > > Would a mailing list mirror of the issues work for you (I guess it would > > > > require an extra click). I think I already get e-mails from issues but > > > > have them filtered out with the rest of other github messages, I'm not > > > sure > > > > if it is easy to split them out. > > > > > > If there's an e-mail notification to user@ (or another place) whenever a > > > new issue is created, containing the full issue text, I guess that would > > > work. > > > > > > > I was under the impression that you can reply to a GitHub issue directly > > from email, as long as you subscribe to issues for a repo. Is that not the > > case?
