I have opened a PR that will enable discussions: https://github.com/apache/arrow/pull/45811
Am So., 16. März 2025 um 15:22 Uhr schrieb Antoine Pitrou <anto...@python.org>: > > > We can start with users@ and, if the experience is subpar, switch to > something else. > > Regards > > Antoine. > > > Le 16/03/2025 à 15:04, Weston Pace a écrit : > > +1 > > > >> A possible reason for hesitation is that it provides us yet another > > stream that requires maintainer attention > > > > I had been lukewarm on discussions in the past partly because of this and > > partly because they cannot be "closed" and grow forever. However, I have > > since learned that the latter concern is more of a feature than a bug. > > Discussions are searchable and can become a wiki / FAQ for the project. > > > > If we can redirect discussions to the ML then I think that hopefully solves > > the attention problem. > > > >> So we could use users@ for that but that might be > >> confusing, so discussions@ or something might be better. > > > > Why would it be confusing to use users@? I think either approach is fine > > but it seems users@ might be simpler. > > > > On Sat, Mar 15, 2025 at 9:06 AM Jacob Wujciak <assignu...@apache.org> wrote: > > > >> +1 > >> > >> For me the main argument is that the discoverability is much better than > >> the ML. > >> > >> A point to note, enabling discussions requires setting a ML that they > >> are mirrored to. So we could use users@ for that but that might be > >> confusing, so discussions@ or something might be better. For rust we > >> used github@ for now. > >> > >> Am Sa., 15. März 2025 um 16:47 Uhr schrieb Bryce Mecum < > >> bryceme...@gmail.com>: > >>> > >>> I think this is a good idea. > >>> > >>> A possible reason for hesitation is that it provides us yet another > >>> stream that requires maintainer attention. But it also occurs to me > >>> that a new stream of information on GitHub may be significantly more > >>> accessible than a stream on a mailing list or third-party website (SO, > >>> Zulip) so it may be easier for non-maintainers to help. > >>> > >>> GitHub Discussions also offers categories and polls which may be > >> interesting. > >>> > >>> On Wed, Mar 12, 2025 at 8:07 PM Sutou Kouhei <k...@clear-code.com> wrote: > >>>> > >>>> Hi, > >>>> > >>>> It seems that we can enable GitHub Discussions by .asf.yaml: > >>>> > >>>> > >> https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#repository-features > >>>> > >>>> Do we want to enable GitHub Discussions for apache/arrow? > >>>> We can use GitHub Discussions for user support like > >>>> u...@arrow.apache.org. > >>>> > >>>> See also: > >>>> "[DISCUSS] Deprecate user@ in favor for github issues/discussions" > >>>> https://lists.apache.org/thread/1m2f7lzcxfplzgjhvsrv66k0d2b4ws87 > >>>> > >>>> FYI: apache/arrow-rs uses GitHub Discussions: > >>>> * https://github.com/apache/arrow-rs/discussions > >>>> * "[Rust] Enable GitHub discussions for Rust projects?" > >>>> https://lists.apache.org/thread/o8d50n8fv989knxcqvnhosbg4fnzdlf8 > >>>> > >>>> > >>>> Thanks, > >>>> -- > >>>> kou > >> > >
