public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "M. J. Everitt" <m.j.everitt@iee.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] The problem of defunct and undermanned projects in Gentoo
Date: Tue, 18 Jul 2017 22:12:45 +0100	[thread overview]
Message-ID: <b05b12f8-a525-efd9-2581-ffaf5579f0a1@iee.org> (raw)
In-Reply-To: <20170719075622.293bff90@katipo2.lan>


[-- Attachment #1.1: Type: text/plain, Size: 1444 bytes --]

On 18/07/17 20:56, Kent Fredric wrote:
> On Sun, 16 Jul 2017 23:12:42 +0200
> Michał Górny <mgorny@gentoo.org> wrote:
>
>> What do you think? Would you mind getting that amount of mail once?
>> Any other ideas?
> From the mail I got, ( which I didn't mind ), I felt there was one
> distinguisher that was missing:
>
> "active" vs "passive" membership.
>
> Like, I get the impression ( with perl for instance ) that although
> many of its members are "around", and they occasionally "do something",
> I'm not sure they can all count as "There" in terms of staff-power
> metrics.
>
> If you make one commit every 6 months, are you really still "active"?
>
> Its useful to keep them all on the list, because they're people who
> have knowledge and can do the work if it comes there way, so I don't
> think *removing* them is the right thing to do.
>
> But for keeping tabs on "do we need more staff or not", it just serves
> as a confusing source of data.
>
There seem to be a lot of devs who are 'on the list' but I never see in
commit logs, etc. Sure they're devs alright, but they're not devaway,
and yet they don't appear to be providing any meaningful contribution.

I think mgorny was doing some general commit stats, and I have yet to
compile my own, but it would be very interesting to see how many
'active' team members there were in any given project. I suspect the
results could be very telling ...


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 862 bytes --]

  reply	other threads:[~2017-07-18 21:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-16 21:12 [gentoo-project] The problem of defunct and undermanned projects in Gentoo Michał Górny
2017-07-16 21:39 ` Daniel Campbell
2017-07-17 23:32 ` Matt Turner
2017-07-18 19:56 ` Kent Fredric
2017-07-18 21:12   ` M. J. Everitt [this message]
2017-07-18 21:23     ` Kent Fredric
2017-07-18 21:35       ` M. J. Everitt
2017-07-18 21:40         ` Michał Górny
2017-07-18 21:44           ` M. J. Everitt
2017-07-19 17:25           ` Alec Warner
2017-07-19 20:11             ` James Le Cuirot
2017-07-19 17:34           ` Ian Stakenvicius
2017-07-19 18:22             ` Rich Freeman
2017-07-19 18:48               ` M. J. Everitt
2017-07-19 18:53               ` Mart Raudsepp
2017-07-20  2:15             ` Aaron Bauman

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=b05b12f8-a525-efd9-2581-ffaf5579f0a1@iee.org \
    --to=m.j.everitt@iee.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