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

MacPorts noreply at macports.org
Tue Nov 8 20:32:11 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 raimue):

 Replying to [comment:11 ryandesign]:
 > 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.

 The problem is not that I do not want to use the @macports.org address,
 just that we do not have the pusher/committer/author's @macports.org
 address, the payload in the WebHook event contains *some* email address
 and the GitHub username, if available.

 We do have the author/committer which should be the @macports.org address,
 but GitHub will always use the primary email address or a noreply-dummy
 for certain actions. Yes, this sucks, but we cannot change it.

 Proposal:

   1. When GitHub tells us the GitHub username of an
 pusher/author/committer, look up their email address in the Trac database.
      These addresses are already published on the web interface and in Cc
 field of ticket notification mails. This would have the side-effect that
 we consistently use the same email address across all notification mails.
 Project members should configure their @macports.org address in Trac.
   2. When the author/committer does not have a GitHub username, we use
 whatever is stored in the commit as author/committer.

 Based on this proposal, I would work on an updated trac-github-update with
 the following settings:

   * refchange mails (those with just a summary):
     {{{
     From: $pusher
     Reply-To: macports-dev@
     }}}
   * commit mails (those with inline patches):
     {{{
     From: $author
     Reply-To: $committer, macports-dev@
     }}}
   * combined mails (a single commit was pushed):[[BR]]
     (same as commit mails)

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



More information about the macports-tickets mailing list