So we are voting on enabling GitHub discussions, its stated in the Apache Wiki that in order to enable GitHub discussions (for any project) one needs an INFRA ticket with a reference to a formal Apache vote (ergo this vote).
Regarding the archiving of GitHub discussions to the mailing list, I think the elephant in the room here is whether this is even intended from Apache. It might be that for Github discussions that it doesn’t need to be synced to a mailing list and is considered a source of truth? That would be quite a departure from how Apache historically handles things. To be clear, I am not implying that we shouldn’t sync it to a mailing list, just that if its not done as part of the process of the INFRA ticket then the implication is that its not necessary???? Maybe we should ask the Apache Airflow community (who uses GitHub discussions)? -- Matthew de Detrich Aiven Deutschland GmbH Immanuelkirchstraße 26, 10405 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen m: +491603708037 w: aiven.io e: matthew.dedetr...@aiven.io On 3. Nov 2022 at 09:52 +0100, Claude Warren, Jr <claude.war...@aiven.io.invalid>, wrote: > This is a vote and I still don't know what I am voting on. > > My understanding is this is to turn on github discussions. > > My questions are: > > 1. Will those discussions be forwarded to an email list or is there no > connection between the two? > 2. If there is a connection, will postings on the email list be > forwarded back to the discussions? > > > > On Thu, Nov 3, 2022 at 7:06 AM PJ Fanning <fannin...@gmail.com> wrote: > > > Github Projects feature is easy to enable. Github Discussions feature > > needs INFRA team to be involved, > > > > Github Projects can be enabled by modifying the .asf.yaml file in the > > git repository. > > > > On Thu, 3 Nov 2022 at 07:35, Matthew Benedict de Detrich > > <matthew.dedetr...@aiven.io.invalid> wrote: > > > > > > I believe we are on the same page here, to me GitHub discussions is > > basically replacing what Lightbend/Akka forums was used for in the original > > Akka. > > > > > > Regarding project management, Github does actually have > > https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects > > which I am curious in trying out. Not sure if Apache has any say on the > > matter. > > > > > > -- > > > Matthew de Detrich > > > Aiven Deutschland GmbH > > > Immanuelkirchstraße 26, 10405 Berlin > > > Amtsgericht Charlottenburg, HRB 209739 B > > > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > > m: +491603708037 > > > w: aiven.io e: matthew.dedetr...@aiven.io > > > On 2. Nov 2022 at 16:13 +0100, Alexandru Nedelcu <alexe...@apache.org>, > > wrote: > > > > Github Discussions are good for new users seeking help. Kind of like a > > StackOverflow. Or for fuzzy discussions, forum-style. Old-school mailing > > lists are hard to subscribe and use. > > > > > > > > I'm pretty sure that our discussions will happen more in GH Issues and > > PRs. Or on ASF's mailing lists. Personally I haven't participated in any > > project using GH Discussions for anything meaningful. Maybe it's because > > the feature is new. > > > > > > > > I would suggest a trial, to see how it feels. > > > > > > > > But I also suspect that Github's "Issues" is where dev discussions are > > more natural, as Issues represent either concrete enhancement proposals or > > bug reports, which can then be tied to PRs. > > > > > > > > I haven't paid attention, but I think the better question is whether > > project management (e.g., Issues) happens on Github. I hope it is. In which > > case, the discussions in those issues may need to be forwarded. But this > > may be another discussion (that may have happened already, sorry if it did). > > > > > > > > On Wed, Nov 2, 2022, at 16:48, Claude Warren, Jr wrote: > > > > > I am still not clear on what happens when the link is established. > > Do all > > > > > discussions get posted to dev? Do all Dev posts get posted to > > > > > discussions? What exactly are we enabling? Or is it just turning on > > the > > > > > discussions? > > > > > > > > > > On Wed, Nov 2, 2022 at 2:32 PM PJ Fanning <fannin...@gmail.com> > > wrote: > > > > > > > > > > > I guess that many Pekko project members expressed an interest in > > using > > > > > > the Github Discussions feature. If we find it too burdensome to get > > > > > > the discussions synched to the dev mailing list, we can review > > whether > > > > > > using the Github Discussions feature is a good idea. > > > > > > > > > > > > It may also suit users who are not Pekko committers and who may not > > > > > > want to join a mailing list to post a comment - but who have Github > > > > > > accounts - to raise questions or express an opinion on a discussion > > > > > > thread. > > > > > > > > > > > > On Tue, 1 Nov 2022 at 15:46, Claude Warren, Jr > > > > > > <claude.war...@aiven.io.invalid> wrote: > > > > > > > > > > > > > > What exactly does enabling the github discussion features do in > > terms of > > > > > > > the interaction between the github discussion and a mailing list? > > > > > > > > > > > > > > When this is enabled, what exactly will the difference be? > > > > > > > > > > > > > > Claude > > > > > > > > > > > > > > On Mon, Oct 31, 2022 at 2:00 PM PJ Fanning <fannin...@apache.org> > > wrote: > > > > > > > > > > > > > > > INFRA team requires that we discuss whether to enable Github > > > > > > Discussions > > > > > > > > before applying to enable it for the Pekko repos. > > > > > > > > > > > > > > > > We have discussed this topic (among other items) in > > > > > > > > > > https://lists.apache.org/thread/0hohnn9v0xhxn0qblb196p7mcq7jzz00 > > > > > > > > > > > > > > > > I will leave this vote open until end of day UTC on Nov 3. > > > > > > > > > > > > > > > > Votes are: > > > > > > > > +1 -- in favour > > > > > > > > 0 -- neutral (but maybe have an opinion to express) > > > > > > > > -1 -- against > > > > > > > > > > > > > > > > Vote carries if there are more +1s than -1s. > > > > > > > > > > > > > > > > Here is my +1. > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > > > > > > > > For additional commands, e-mail: dev-h...@pekko.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > > > > > > For additional commands, e-mail: dev-h...@pekko.apache.org > > > > > > > > > > > > > > > > > > > > -- > > > > Alexandru Nedelcu > > > > alexn.org > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > > > > For additional commands, e-mail: dev-h...@pekko.apache.org > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > > For additional commands, e-mail: dev-h...@pekko.apache.org > > > >
