[MacPorts] #52826: commit notification emails don't allow replies to the committer

MacPorts noreply at macports.org
Tue Nov 8 17:42:35 CET 2016


#52826: commit notification emails don't allow replies to the committer
-----------------------------+---------------------
  Reporter:  ryandesign      |      Owner:  admin@…
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+---------------------

Comment (by neverpanic):

 Replying to [comment:11 ryandesign]:
 > If the problem is that we don't ask the user's permission to store their
 GitHub email address for other purposes when they log in to Trac, then
 let's ask for that permission.
 >
 > It should come as no surprise to any MacPorts committer that when we
 issue them an @macports.org email address, we will use that email address
 to communicate with them, and that since we're an open source project and
 conduct our communications on public mailing lists, that email address
 will become public knowledge. I don't know of any committer who's
 complained about that before.

 That's absolutely true for MacPorts commiters (and reading through the
 ticket it seems you're only interested in the committer of a patch, not
 necessarily the author?). It's a different story for the occasional
 contributor that sends a PR on GitHub and then sees one of their email
 addresses, possibly one marked private on GitHub, appear on our mailing
 list.


 > If the commit already contains the email address of the author and the
 committer, let's use that. Our policy is already that that should be the
 @macports.org email address. I very much want to be able to reply to the
 email and reach both the committer and the author. Previously, I've often
 had to go to the ticket to find the author's email address and manually
 add it to the email.

 I agree. That data is already public with the commit and should be fine to
 use in virtually all cases.


 > If GitHub won't use the @macports.org email address when clicking the
 merge button on the web site, then that sucks and I don't know what to do
 about it.

 We should take to GitHub support.

--
Ticket URL: <https://trac.macports.org/ticket/52826#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS



More information about the macports-tickets mailing list