Hi, > Would the experiment be removing the guidance to use > user@?
How about "you can use here or users@" or something? > What do you think the success metrics would be? The number of reported questions and the number of resolved them? I think that people who vote +1 have better ideas. It seems that they have their success stories with GitHub issues/discussions. Thanks, -- kou In <cak7z5t-htlgcifrgaqmwy5qnvtt26g6jn5kgs3-wuyjw7cd...@mail.gmail.com> "Re: [DISCUSS] Deprecate user@ in favor for github issues/discussions" on Thu, 7 Oct 2021 20:06:34 -0700, Micah Kornfield <emkornfi...@gmail.com> wrote: > Yeah, I think we can keep the both active. Would the experiment be > removing the guidance to use user@? What do you think the success metrics > would be? > > On Tue, Oct 5, 2021 at 8:14 AM Aldrin <akmon...@ucsc.edu.invalid> wrote: > >> > >> > How about trying GitHub issues and/or discussion in a >> > specified period without deprecating user@? e.g. between >> > 6.0.0 release and 7.0.0 release. >> >> >> Oooh, I like this idea. >> >> >> Aldrin Montana >> Computer Science PhD Student >> UC Santa Cruz >> >> >> On Mon, Oct 4, 2021 at 7:11 PM Sutou Kouhei <k...@clear-code.com> wrote: >> >> > Hi, >> > >> > How about trying GitHub issues and/or discussion in a >> > specified period without deprecating user@? e.g. between >> > 6.0.0 release and 7.0.0 release. >> > >> > If we can see significant improvements in the period, we can >> > discuss this again. >> > >> > In my opinion, I want to disable GitHub issues entirely by >> > .asf.yaml. It's confusing to have multiple issue tracking >> > systems within the same project. >> > >> > >> > Thanks, >> > -- >> > kou >> > >> > In <CAK7Z5T-CX8LYSaxy7H-At9QRq=kgwafevtqzxn5yfgjf02y...@mail.gmail.com> >> > "[DISCUSS] Deprecate user@ in favor for github issues/discussions" on >> > Wed, 29 Sep 2021 11:16:07 -0700, >> > 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 >> > >>
