public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* [gentoo-dev] [RFC] Requiring gentoo.git committers to use their @gentoo.org address
@ 2018-07-09  8:40 99% Michał Górny
  0 siblings, 0 replies; 1+ results
From: Michał Górny @ 2018-07-09  8:40 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]

Hi,

We currently don't enforce any particular standard for e-mail addresses
for developers committing to gentoo.git.  FWICS, the majority of
developers is using their @gentoo.org e-mail addresses.  However, a few
developers are using some other addresses.

Using non-@gentoo.org e-mail addresses generally causes problems
in accounting for commits.  For example, our retirement scripts can't
detect commits made using non-Gentoo e-mail address.  My dev-timeline
scripts [1] account for all emails in LDAP (which doesn't cover all
addresses developers use).  FWIK gkeys accounts for all addresses
in the OpenPGP key UIDs.  In my opinion, that's a lot of hoops to jump
through to workaround bad practice.

Therefore, I'd like to start enforcing (at the level of the hook
verifying signatures) that all commits made to gentoo.git (and other
repositories requiring dev signatures) are made using @gentoo.org e-mail 
address (for committer field).

Is anyone opposed to that?  Does anyone know of a valid reason to use
non-@gentoo.org address when committing?

[1]:https://dev.gentoo.org/~mgorny/dev-timeline.html

-- 
Best regards,
Michał Górny

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2018-07-09  8:40 99% [gentoo-dev] [RFC] Requiring gentoo.git committers to use their @gentoo.org address Michał Górny

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox