> 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? ].
My perspective is that alerts from human contributors are things we really need an alert to… dependably alerts are basically noise, but remind us to look at dependencies… That was my thinking > 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? They could… however, there is a concerted drive to keep the Apache threads relevant. For real, I’ve had students who have asked me, “what’s a listserv”? I think it’s presently natural to keep communities close to the source code, which keeps them on platforms like GitHub. However, lists are important to Apache for a few reasons: 1) they are an auditable record of the community and its decisions; 2) lists foster discussion about community over code. So, IMHO I think we should work to bridge discussions on GItHub with dev -J > On Jun 6, 2023, at 1:34 AM, Austin Bennett <aus...@apache.org> wrote: > > 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 > <mailto: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: >> >> >> plc4x/.asf.yaml at e14a3d7dc8bae8ead824f019d5e87767c4460adc · apache/plc4x >> github.com >> >> <https://github.com/apache/plc4x/blob/e14a3d7dc8bae8ead824f019d5e87767c4460adc/.asf.yaml#L61>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> >> >> >> Thoughts? Commends?
