Hi, I did some research and figured out how it works. According to [1], we need the PMC chair or another Apache Member on the PMC to create new mailing lists on the ASF Self-Service Platform [2]. Then according to [3], we need add a .asf.yaml file to the master branch of the Github repository (e.g. parquet-mr) to set up notification rules. For example, [4] and [5] are the current settings of parquet-format and parquet-mr respectively.
[1] https://infra.apache.org/mailing-list-moderation.html#new-mailing-list [2] https://selfserve.apache.org/ [3] https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Notificationsettingsforrepositories [4] https://gitbox.apache.org/schemes.cgi?parquet-format [5] https://gitbox.apache.org/schemes.cgi?parquet-mr Best, Gang On Mon, Oct 2, 2023 at 2:30 AM Micah Kornfield <emkornfi...@gmail.com> wrote: > +1 I think we need a PMC member to make this change? > > On Tue, Aug 29, 2023 at 7:27 PM Gang Wu <ust...@gmail.com> wrote: > > > I think we can send a notification email to the dev@ so that > > people can know what is going on and subscribe to what they > > want after the split. We should also update the website to > > reflect the change in the mailing list. Due to the current activity > > in the community, I am not too worried if people will suddenly > > stop receiving notifications about commits and issues. > > > > Gang > > > > > > On Mon, Aug 28, 2023 at 1:23 AM Xinli shang <sha...@uber.com> wrote: > > > > > comm...@parquet.apache.org should have already existed but not > attached > > > to the github to send notification. We need just to create issues@. > But > > > the question is how to migrate current receivers of the commits and > > issues > > > (currently notifications are sent to dev@). If we redirect all the > > > notifications to the two empty mailing lists without auto migration, > then > > > suddenly everybody will stop receiving those notifications and people > > will > > > have to manually add themselves to the two mailing lists. I don't > find a > > > way to clone and rename. Does anybody have idea on how to solve this > > > problem? > > > > > > On Mon, Aug 21, 2023 at 11:55 PM Uwe L. Korn <uw...@xhochy.com> wrote: > > > > > >> +1 > > >> > > >> On Tue, Aug 22, 2023, at 5:29 AM, Gang Wu wrote: > > >> > +1 on this. > > >> > > > >> > We may create the following mailing lists: > > >> > - iss...@parquet.apache.org : notifications from JIRA issues. > > >> > - comm...@parquet.apache.org : notifications from Github PRs and > > >> comments. > > >> > > > >> > This is what the Apache ORC community currently does. Can one of the > > >> PMCs > > >> > do this? > > >> > Probably we need a formal vote before proceeding. > > >> > > > https://infra.apache.org/mailing-list-moderation.html#new-mailing-list > > >> > > > >> > Best, > > >> > Gang > > >> > > > >> > On Tue, Aug 22, 2023 at 8:49 AM Xinli shang <sha...@uber.com.invalid > > > > >> wrote: > > >> > > > >> >> It is a good idea. Thank Antonie for the proposal. > > >> >> > > >> >> On Tue, Aug 22, 2023 at 2:03 AM Julien Le Dem > > >> <jul...@astronomer.io.invalid > > >> >> > > > >> >> wrote: > > >> >> > > >> >> > +1 > > >> >> > > > >> >> > On Mon, Aug 21, 2023 at 10:16 AM Antoine Pitrou < > > anto...@python.org> > > >> >> > wrote: > > >> >> > > > >> >> > > > > >> >> > > Hello, > > >> >> > > > > >> >> > > I would like to request that automated notifications (from > > GitHub, > > >> >> > > Jira... whatever) be sent to a separate mailing-list and GMane > > >> mirror. > > >> >> > > Currently, the endless stream of automated notifications in > this > > >> >> > > mailing-list means that discussions between humans quickly get > > >> lost or > > >> >> > > even unnoticed by other people. > > >> >> > > > > >> >> > > For the record, we did this move in Apache Arrow and never came > > >> back. > > >> >> > > > > >> >> > > Thanks in advance > > >> >> > > > > >> >> > > Antoine. > > >> >> > > > > >> >> > > > > >> >> > > > > >> >> > > > >> >> > > >> >> > > >> >> -- > > >> >> Xinli Shang > > >> >> > > >> > > > > > > > > > -- > > > Xinli Shang > > > > > >
