From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] pre-GLEP: Gentoo Developer status
Date: Tue, 24 Apr 2018 14:58:18 +1200 [thread overview]
Message-ID: <20180424145818.59fcb3c2@katipo2.lan> (raw)
In-Reply-To: <60d3f7a1-0e4f-1e08-1f8b-17001be255a1@iee.org>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On Mon, 23 Apr 2018 22:30:21 +0100
"M. J. Everitt" <m.j.everitt@iee.org> wrote:
> I'm inclined to support the idea that <something> is marginally better
> than <nothing> and could be used as some form of evidence should there
> be need to substantiate a claim either way, and make it much less
> subjective ...
>
> Not looking for a perfect solution here, that IS impossible, just
> something that would aid metrics...
Agreed. Its useful in one direction, to say "Look, they're active, proof!",
but can't be used to say "Look, they're INACTIVE".
Similar to how a Bloom Filter can be used to say:
"We definitely did not see this item before"
But can't be used to say
"We definitely saw this item before"
Subsequently, an automated "you're inactive, so drop your commit
rights" bot can't exist, as it can only determine if you're factually
active, not factually inactive.
It could at best aggregate these sources and produce a list of gentoo
devs that are /possibly/ inactive, but not /certainly/ inactive.
And humans can then scour that list and attempt to verify the activity
status.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-24 2:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 17:31 [gentoo-project] pre-GLEP: Gentoo Developer status Michał Górny
2018-04-13 21:28 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-13 21:57 ` Rich Freeman
2018-04-13 22:07 ` M. J. Everitt
2018-04-13 22:25 ` Rich Freeman
2018-04-13 22:29 ` M. J. Everitt
2018-04-13 22:41 ` Rich Freeman
2018-04-14 1:10 ` Alec Warner
2018-04-14 1:05 ` Raymond Jennings
2018-04-14 1:23 ` Rich Freeman
2018-04-14 1:33 ` Alec Warner
2018-04-14 5:59 ` Ulrich Mueller
2018-04-15 12:01 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-15 12:25 ` Ulrich Mueller
2018-04-14 7:24 ` Michał Górny
2018-04-15 11:44 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-15 12:03 ` Rich Freeman
2018-04-15 12:22 ` Michał Górny
2018-04-15 16:55 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-15 17:22 ` M. J. Everitt
2018-04-22 17:24 ` Kent Fredric
2018-04-23 20:01 ` Robin H. Johnson
2018-04-23 21:30 ` M. J. Everitt
2018-04-24 2:58 ` Kent Fredric [this message]
2018-04-15 17:58 ` Michał Górny
2018-04-21 17:21 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-14 6:57 ` Matthew Thode
2018-04-14 7:19 ` Michał Górny
2018-04-14 7:32 ` Matthew Thode
2018-04-14 20:58 ` Daniel Robbins
2018-04-14 21:16 ` Raymond Jennings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180424145818.59fcb3c2@katipo2.lan \
--to=kentnl@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox