Send GitBox notifications to separate list

[ctubbsii]

This change redirects GitBox issue/pull request activity to a separate mailing list to avoid spamming the dev@ list. The new notifications@ list must be created by the ComDev PMC before accepting/merging this PR.

The justification for this change is:

1. These automated notices are redundant if somebody is already watching the relevant notices for the repo on GitHub. So, sending these to another list allows users more flexibility in receiving them or not, and whether they prefer to receive them as an email or as a notice directly from watching the repo in GitHub.
2. These automated notices spam the dev@ list which many more people follow for the human discussions here on community development across the ASF. Sending them to another list ensures the dev@ list is reserved for human-to-human conversations, and keeps people from unsubscribing and connected to the community due to frustration with spam.

[bessbd]

+1 (non-binding)

[dave2wave]

issues have not been enabled so that setting is irrelevant.

[ctubbsii]

issues have not been enabled so that setting is irrelevant.

As far as I can tell, the "issues" type is used for all "issue_comment" events, regardless of whether they occur on an "issue" or a "pull request". It should be noted that a "pull request" is just a type of "issue" on GitHub that also has a special git ref associated with it under refs/pull (see git ls-remote). So, it's necessary to set an address for "issues" if you want to get notifications for comments on pull requests, even if you're not using "issues".

[sebbASF]

I agree it would be good to redirect these messages, but notifications@ does not exist (yet)

[ShaneCurcuru]

Given the new energy around updating the ComDev website, this should be revisited, along with the work to move GSOC issues to a separate JIRA/separate mailing list. I.e. what overall mailing lists with these automated notifications do we want? Just notifications@ for both GSOC and COMDEV jiras and GitBox emails? Or is GSOC separate and deserves it's own gsoc-something@ lists?

[sebbASF]

I think GSOC should have its own list. I suggest:

general@ for community discussion tools@ for projects/reporter etc gsoc@ for all things GSOC issues@ for COMDEV Jiras

I think it would be best to drop dev@ in the long term.

[ctubbsii]

As long as automated notices are separated out from human discussions, I think most people would be happy. I don't know that it makes a lot of sense to go overboard on multiple lists for automated notices, or multiple lists for human conversation. So long as those two are separated, it should be enough for most.

[mtrackeros]

Ta zmiana przekierowuje działania GitBox issue/pull request na osobną listę mailingową, aby uniknąć spamowania listy dev@. Nowa lista notifications@ musi zostać utworzona przez ComDev PMC przed zaakceptowaniem/scaleniem tego PR.

Uzasadnienie tej zmiany jest następujące:

1. Te automatyczne powiadomienia są zbędne, jeśli ktoś już obserwuje odpowiednie powiadomienia dla repozytorium w usłudze GitHub.These automated notices are redundantne if someone is already watching the relevant notices for the repo on GitHub. Tak więc wysyłanie ich do innej listy pozwala użytkownikom na większą elastyczność w ich otrzymywaniu, czy nie, i niezależnie od tego, czy wolą otrzymywać je jako wiadomość e-mail, czy jako powiadomienie bezpośrednio z oglądania repozytorium w GitHub.
2. Te automatyczne powiadomienia spamują listę dev@, którą śledzi o wiele więcej osób w ludzkich dyskusjach na temat rozwoju społeczności w ASF. Wysłanie ich na inną listę gwarantuje, że lista dev@ jest zarezerwowana dla rozmów międzyludzkich i uniemożliwia użytkownikom anulowanie subskrypcji i łączenie się ze społecznością z powodu frustracji związanej ze spamem.

30083e792d2d2aadc74a6f6543df91696ae1b060

[ctubbsii]

I don't know what's going on with the spam on this PR, but I rebased it on the current main branch, resolving conflicts, in hopes that this will get some attention again, and will get merged, so I can get a slightly less amount of spam while following comdev's mailing list.

[sebbASF]

The list needs to be created first

[ctubbsii]

The list needs to be created first

Yes, but I am not a PMC member. The ComDev PMC needs to first decide they want to do this, then create the list, then merge the PR.

[elyn6748]

packages/create-vite/tests/cli.spec.ts