+1 for GitHub discussions as well. But I am also little concerned about multiple places for discussions. As Danny said, if we have a good plan on how to move forward on how/when to archive the current mailing list, that would be great.
Thanks, Anand On Sat, Jul 1, 2023, 3:21 AM Damon Douglas <douglas.da...@gmail.com> wrote: > I'm very strong +1 for replacing the use of Email with GitHub Discussions. > Thank you for bringing this up. > > On Fri, Jun 30, 2023 at 7:38 AM Danny McCormick via dev < > dev@beam.apache.org> wrote: > >> Thanks for starting this discussion! >> >> I'm a weak -1 for this proposal. While I think that GH Discussions can be >> a good forum, I think most of the things that Discussions do are covered by >> some combination of the dev/user lists and GitHub issues, and the net >> outcome of this will be creating one more forum to pay attention to. I know >> in the past we've had a hard time keeping up with Stack overflow questions >> for a similar reason. With that said, I'm not opposed to trying it out and >> experimenting as long as we have (a) clear criteria for understanding if >> the change is effective or not (can be subjective), (b) a clear idea of >> when we'd revisit the discussion, and (c) a clear path to rollback the >> decision without it being *too *much work (this might mean something >> like disabling future discussions and keeping the history or somehow moving >> the history to the dev or user list). If we do this, I also think we should >> update https://beam.apache.org/community/contact-us/ with a clear >> taxonomy of what goes where (this is what I'm unsure of today). >> >> FWIW, if we were proposing cutting either the user list or both the user >> and dev list in favor of discussions, I would be +1. I do think the >> advantages of discussions over email are real (threaded, easy to convert >> to/from issues, markdown, one place for all things Beam). >> >> Thanks, >> Danny >> >> On Fri, Jun 30, 2023 at 10:23 AM Svetak Sundhar via dev < >> dev@beam.apache.org> wrote: >> >>> Hi all, >>> >>> I wanted to start a discussion to gauge interest on enabling Github >>> Discussions <https://docs.github.com/en/discussions/quickstart> in >>> Apache Beam. >>> >>> >>> Pros: >>> >>> + GH Discussions allows for folks to get unblocked on small/medium >>> implementation blocker (Google employees can often get this help by >>> scheduling a call with teammates whereas there is a larger barrier for >>> non-Google employees to get this help). >>> >>> + On the above point, more visibility into the development blockers that >>> others have previously faced. >>> >>> + GH Discussions is more discoverable and approachable for new users and >>> contributors. >>> >>> + A centralized place to have discussions. Long term, it makes sense to >>> eventually fully migrate to GH Discussions. >>> >>> >>> Cons: >>> >>> - For a period of time when we use both the dev list and GH Discussions, >>> context can be confusing. >>> >>> - Anything else? >>> >>> >>> To be clear, I’m not advocating that we move off the dev list >>> immediately. I propose that over time we slowly start moving discussions >>> over to GH discussions, utilizing things such as the poll feature. >>> >>> >>> I am aware that the Airflow project [1] uses both GH Discussions today >>> and a dev@ list [2] today. >>> >>> >>> [1] https://github.com/apache/airflow/discussions >>> >>> [2] https://lists.apache.org/list.html?d...@airflow.apache.org >>> >>> Thanks, >>> >>> >>> Svetak Sundhar >>> >>> Data Engineer >>> s <nellywil...@google.com>vetaksund...@google.com >>> >>>
