GitHub usernames in maintainers field

[Jeremy Huddleston Sequoia]

Do we have a mapping list somewhere, so we can just script this for known mappings?

Anyone interested in doing this for their ports might find this useful:

    for g in */ ; do
        sed -i '' '/maintainers/s/\([^{@]\)jeremyhu/\1{jeremyhu @jeremyhu}/g' $g/*/Portfile
    done

There certainly could be some false matches with that, so check `git diff` first.

--Jeremy

> On Feb 4, 2017, at 17:30, Mojca Miklavec <mojca at macports.org> wrote:
> 
> Hi,
> 
> On 4 February 2017 at 17:07, Clemens Lang wrote:
>> On Thu, Feb 02, 2017 at 03:12:27PM -0800, Eitan Adler wrote:
>>>> maintainers     {jmr @jmroot} openmaintainer
>>> 
>>> Why did we choose to do it this way instead of a central list of email
>>> -> github mapping? This method requires some level of replication.
>> 
>> Ports can exists outside of a port repository. External repositories
>> could have different assignments, Portfiles could even exist without a
>> mapping file at all.
> 
> What we need is:
> - ability to send emails to maintainers (that includes the buildbot)
> - ability to @mention them in GitHub PRs
> - ability to assign or CC people in Trac tickets
> 
> I would in fact prefer to see the official tickets to have a common
> "database of maintainers" with obfuscated email addresses together
> with GitHub usernames and then only see one entry for maintainers in
> the Portfile (but I'm not so strongly opposing having both in the
> Portfile; in particular not now that having both in the Portfile is
> supported and having a separate database is not).
> 
> I don't care that much what exactly is written in the Portfile, but I
> need the ability to get the email and @username with "port info" at
> least.
> 
> If maintainers simply start *replacing* their emails with their
> usernames in portfiles (which is what I already saw happening in some
> tickets/pull requests a while ago) then:
> 
> - we'll lose the ability to email them
> - we won't be able to send them auto-generated emails in case of
> buildbot failures
> - we won't quite know whether a maintainer is a committer or not
> 
> and we don't want that.
> 
> 
> In my opinion the initial addition of github usernames next to email
> addresses should happen with a script. Doing this manually is:
> - tedious, lots of work
> - error prone
> - destined to take forever (using the mapping between emails and
> github accounts from Trac wuould be mo reliable source of information
> that waiting for maintainers)
> 
> Maintainers that we'll most urgently want to reach won't answer the
> call to change their usernames; hack, I already managed to open a
> "port abandoned" ticket for a committer who still refuses (or at least
> doesn't bother) to replace his super ancient email address (that he
> never uses to communicate with other macporters) with his macports
> handle, so it wasn't obvious that it was the same person.
> 
> Mojca

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4465 bytes
Desc: not available
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20170211/4236c1cf/attachment.bin>