I believe it is a technical issue. Otherwise, I could disable GitHub notifications for anything in the Apache org and rely entirely on emails sent to either dev@ or commits@ or whichever list a project uses for notifications. While you can reply to a commit email from gitbox and have it go straight to dev@, the equivalent functionality for GitHub notifications isn't there.
On Thu, Mar 3, 2022 at 8:32 AM Gilles Sadowski <gillese...@gmail.com> wrote: > > Le jeu. 3 mars 2022 à 14:46, Jarek Potiuk <ja...@potiuk.com> a écrit : > > > > Yep. > > > > The Apache Git Service emails have no chances to work. You have to > > subscribe to the project notification by creating an account in GitHub > > This is what several people in this thread said (IIUC) would be > unacceptable for participation in the ASF (although, as I mentioned in > my reply earlier today, this fence is already in place in some projects). > > > and > > providing the email address where you will receive notifications. It > > would not be possible otherwise by GitHub to know who you are (you receive > > an individually generated reply-to address) > > Isn't this a technical issue that could in principle be solved with a > bridge between the ASF login, passing on an authentication token > (as many sites do through one's Google account)? > > Regards, > Gilles > > > > > On Thu, Mar 3, 2022 at 2:27 PM Gilles Sadowski <gillese...@gmail.com> wrote: > > > > > Hi. > > > > > > >>> [...] > > > > > > > > > * Point 2. But even if I missed it - for Github Discussions it is > > > enough to > > > > > > reply to the email you get - with your personal email. You must have > > > missed > > > > > > the point as well. It's full interaction, you "reply-to" and your > > > entry is > > > > > > part of the discussion. Does it qualify as interaction ? > > > > > > > > > Next time I wish to intervene in GH discussion, I'll try it. ;-) > > > > > > > > > > > > > Feel free [...] > > > > > > So I did try, FTR: > > > I got this notification from the "issues@commons.a.o" ML: > > > https://markmail.org/message/iiiszn4g5ul35edr > > > to which I replied: > > > https://markmail.org/message/ws43ryyvztnrcgb5 > > > This latter email does *not* become part of the GH discussion: > > > > > > https://github.com/apache/commons-collections/pull/281#discussion_r818409462 > > > > > > Actually it's no surprise (that it does not work the way you > > > implied above), since mails (from "issues@") have this footer: > > > ---CUT--- > > > This is an automated message from the Apache Git Service. > > > To respond to the message, please log on to GitHub and use the > > > URL above to go to the specific comment. > > > ---CUT--- > > > > > > Hence, unless they log in into GH, an ASF contributor cannot > > > comment on changes to an ASF code. > > > [For all purpose, I'm shut out from GH-initiated discussions because > > > my (ML) reply will likely be missed by people who have (some time > > > ago already, and without consensus) started to consider that the > > > authoritative forum is GH.] > > > > > > Regards, > > > Gilles > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
