You can then cycle back with something like a tack on survey to redhat employed contributors and try to develop aggregate information about how often people are doing off-the-clock versus on-the-clock work. Obviously it will differ from person to person, but you might be able to stand up the average to apply in aggregate to the subgroup as layered approach to pull your strict upper/lower boundary statement and make it a statistical statment with quantified average and stddev.

-jef

Relative importance is relative. To some folks, a set of TTF files is more valuable than all of LibreOffice. I’d rather not try to track that, either.

I’ll leave RPM Fusion up to someone else, for now.

Can’t you just look at the groups in FAS?

For example, for Red Hat employees contributing to Fedora there is:
https://admin.fedoraproject.org/accounts/group/view/cla_redhat

(there are equivalent groups for Dell, Intel,…)

That seems much less tedious, and much more future-proof (in case somebody gets hired for example).

Another hard to count factor is the package importance, since not all packages are equal, is different when one maintain a the *whole* LibreOffice and someone a set of TTF files (for example).

And yet another thing which can’t be aggregated into the official statistics are packages available elsewhere – and I am talking here about things like RPM Fusion, practically but not officially they *are* Fedora.

Exactly! I’m pretty sure we can do all sorts of automagic to help flag potential bottlenecks (or downright trouble), and it’s ultimately about giving us humans a chance to reach out to each other.

It’s not really like a system monitoring setup, humans aren’t like servers. But human interaction – especially creating free and open source software on the Internet globally – is a social network with a lot of programmatic interfaces. Now we’re starting to get to something we can monitor and analyze, a network with API calls flying across it.

I’m really excited by your effort here.

I would love to be able to mature methology and trending to the point were we can start to identify bottlenecks and some outreach goals.

I think the nuances you mention would matter statisitcally if I were trying to track how Red Hat spends payroll down to small percentages of a full-time person. That is something that really is between a manager, a team, and an individual. Even where you may have some Fedora duties as part of your job role, it can be very fluid how much time it takes, and you may get interested and pulled in to other parts of Fedora outside of that, again on a fluid basis. I think that overall flow is extremely important to the value and success of Red Hat in both producing free/open source software, and in making a business out of it.

Ultimately, my goal is to create something that people who take it on themselves to care about the health of their community – people like you and I – can have a dashboard-like view in to the kind of output of stats++ https://fedoraproject.org/wiki/User:Ianweller/statistics_plus_plus, with associated content to help analyze and act based on what the metrics show.