I would prefer that discussions don't go to the dev@ list as they create much noise and I usually check things on Github using the notifications there.
We could send them to issues@ or create discussions@. I personally don't care as I see the list only for archival. For me discussions and issues on GH are somewhat related so having them on the issue list would be the easiest but a new list could be cleaner. Regards Niklas On July 6, 2023, Jesse <purplecabb...@gmail.com> wrote: > Since I have not heard anything here, I am assuming that the way > things are > is fine. > > Cheers, > Jesse > > On Wed, Jun 28, 2023 at 11:31 PM Jesse <purplecabb...@gmail.com> > wrote: > > > I have made the change to github.com/apache/cordova so that all > > discussion activity will be sent to our (dev) mailing list. There > has been > > some concern raised in slack#pmc that this will flood the dev list > which we > > use specifically for cordova development, and NOT for support. > > For years now, when anyone has sent a message to the dev list asking > a > > 'how to use cordova' question, we have flatly told them: > > | "This mailing list is for discussions regarding the development of > > Apache Cordova and not for support. For support and/or questions > about how > > to use Apache Cordova, please use GitHub Discussions ... " > > So it does seem a little weird if those discussions end up right > back here. > > > > A vote will follow shortly (tomorrow) proposing that we create a new > > mailing list disc...@cordova.apache.org and route all github > discussion > > activity there. > > > > Please use this thread to weigh alternatives, of which I see a few: > > - do nothing, set up your own filters if you are annoyed by the > extra > > email on dev > > - route this traffic to issues, which is already collecting all gh > issues, > > pull requests and comments > > - create a new list, but with some other name to avoid confusion > with > > [DISCUSS] threads > > > > Cheers, > > Jesse > >
