[Teammetrics-discuss] Video Notes.

[Sukhbir Singh]

Hi,

The video for our talk at DebConf is at:
http://meetings-archive.debian.net/pub/debian-meetings/2011/debconf11/low/712_Measuring_Team_Performance.ogv

Here are the important points for the meeting that we should
implement/ give a thought to:

--
07:22
What percentage of emails have actually been followed by someone else?

07:40
Attachments? People send attachments to mailing lists in the form of
patches and later on they are accepted into the team. But this metric
is _before_ they are a member of the team, so do we actually count
that?
(Your comment follows)

15:12
Enrico suggests that we measure the number of commits in a month,
which seems like a good idea. This can be easily done.

20:30
Another good point by Enrico in which he says that it's public data
but if someone is not interested, we should remove his/ her name from
it. I think this is a good idea. We should have a form or something
that people can fill if they want their name to be removed. I know
this is weird, given it's already there in other places, but well...
:)

22:10
dkg suggests that we don't mention names and just use it for team
comparison. This can be useful in some places but I don't think we
would like it globally.

27:30
Members of team who are vouched by DM/ DD. But how do we decide this 'vouching'?

28:05
Measuring Wiki page edits. This sounds good and I need to investigate this.
(Your question follows and a probable solution is provided)

30:10
(My favourite!)
A very good suggestion is made that we should ping inactive members of
a team using this data. I think this is the _best_ practical usage of
our project. A team has members who are just members and are not
contributing so that the team can know whether they still want to
contribute or not and whether their comments should be waited for.

32:00
dkg suggests that we should send a mail to debian-devel-announce or
something that we can present our metrics. We can highlight the teams
that are doing well. This will not only make our project more
practical but it is again an enhancement to the comments at 30:10.

35:40
Could this be used to identify orphaned packages? Yes. At least for
Git it is possible.
--

It was suggested by a friend after the video (and who was too shy to
speak during the recording!), that we measure balance within a team.
Like in the 'debian-med', you were the single committer. However,
there are many teams that have a balance of involvement and we need to
highlight that because that is what makes a team good -- every member
is contributing.

We will take up the points mentioned here one by one.