GitHub usernames as maintainers [Was: Re: [macports-ports] branch master updated: berkeleygw: Remove svn $Id$ line.]

Rainer Müller raimue at macports.org
Tue Nov 1 12:28:00 PDT 2016


On 2016-11-01 19:57, Clemens Lang wrote:
> On Tue, Nov 01, 2016 at 07:42:23PM +0100, Mojca Miklavec wrote:
>> At some point (rather sooner than later) we'll have to start adding
>> GitHub usernames to Portfiles (we might have to extend the base to
>> properly support that).
> 
> I agree, especially because the GitHub username is now also valid in
> Trac. At the moment, you'd get new tickets sent to your email address,
> not your Trac account (unless a user notices the equivalence in the
> auto-completion box).

Should we get Trac to automatically replace email addresses with the
corresponding username in the Owner and CC fields?

>> And quite honestly I would also be in favour of asking committers to
>> use the same MacPorts handle as their GitHub account name (and only
>> keep the old ones as aliases).
> 
> I like my handle, but I can see how it could lead to confusion. On the
> other hand, the maintainer handles are bound to become less important in
> the future anyway. If you want to reach a committer, there usually are
> contact methods on their GitHub profile.

Using GitHub usernames in the maintainer field has the downside that you
can no longer reach port maintainers outside of GitHub or Trac. There is
no requirement to have a public email address on the GitHub profile.

We could add a mapping of GitHub username to MacPorts handle to the
ports tree, but that would also only solve the problem for the
developers team, not outside collaborators.

Rainer


More information about the macports-dev mailing list