Dependabot opens PRs, why treat that differently than other PRs? So, I'm at least a +1 on both 1 and 2 [ but suggest they be the same list? ].
For 4 --> Any reason people can't just subscribe themselves to notifications [ via 'watch' ]? https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications ... why opt all subscribers of dev list to get that traffic, when there is another way to get that info for anyone that wants? On Mon, Jun 5, 2023 at 9:18 PM Joshua Poore <poor...@apache.org> wrote: > Hi Folks, > > I wanted to raise that we’ve been (slowly) looking to address a sensible > way to manage the “rage” that GitHub adds to our lists. We don’t want an > inundation of GitHub comms on the lists to dissuade usage of the lists. > > Here’s my proposal: > > 1) to open a ‘maintenance’ list for flagon and pipe dependabot alerts > there suppress from dev > 2) to open a ‘PR’ list for flagon and pipe PR notifications through > there. > 3) commits will stay on the ‘commits’ thread. > 4) pipe GitHub discussions and Issue mods through to ‘dev’ > > Frees up dev for actual discussion and helps better integrate our dev list > with GitHub, where most of our comms about dev actually end up… > > Big thanks to Chris Dutz @ Apache who informed us of some cool stuff > they’re doing with lists and Steampipes. Great example here: > > [image: plc4x.png] > > plc4x/.asf.yaml at e14a3d7dc8bae8ead824f019d5e87767c4460adc · apache/plc4x > <https://github.com/apache/plc4x/blob/e14a3d7dc8bae8ead824f019d5e87767c4460adc/.asf.yaml#L61> > github.com > <https://github.com/apache/plc4x/blob/e14a3d7dc8bae8ead824f019d5e87767c4460adc/.asf.yaml#L61> > > <https://github.com/apache/plc4x/blob/e14a3d7dc8bae8ead824f019d5e87767c4460adc/.asf.yaml#L61> > > > Thoughts? Commends? >
