This page describes the proposed metrics to be used for tracking individuals' contributions to MeeGo. This is related to, but separate from, the project metrics discussed in Metrics.
The initial goal is to define a set of metrics which reflect a user's participation in various parts of the MeeGo community (for example, platform development, application development, documentation, tutorials, QA, translation, user assistance, bug reporting). These metrics are called "reputation metrics".
The initial goals do not include trying to combine these metrics into a single "karma" measure.
There are several desirable attributes for the reputation metrics:
Not all these attributes will be achievable for each metric.
Reputation metrics should be tracked for everyone who has a meego.com account. Some systems do not require a meego.com account (e.g. mailing lists): in these cases, non meego.com account holders will mot have metrics. For each reputation area, the mechanism of relating users to meego.com accounts needs to be worked out (especially if it is not just as simple as "log in with a meego.com account").
The remainder of this page is divided up into a section for each separate reputation area.
Each area is proposed, along with a proposal for how the metric should be calculated. Other information may include how a similar metric is calculated in Maemo or any other project and/or what data is available from the software which handles that area. How users are identified should also be described here unless it is obvious.
Metric is dependent on number of votes received.
Metric: Sum of ( number of votes received / number of months since posting )
In Maemo, the equivalent karma contribution is 1-10, depending on the number of votes.
Measuring the value of applications. Note that the intent is that each author/maintainer, as well as the packager gets credit for the app (it is not divided between them).
Metric: Sum of ( number of stars received )
In Maemo, the equivalent karma contribution is 7 * (1 + stars per application).
As it stands, this metric does not degrade over time. If we wish to encourage regular updates then "months since last update" can be a divisor. However, it is assumed that applications which need updates but do not receive them will gradually get marked down and that applications which do one thing well, and do not need further updates, should not be penalised.
Contributions to discussions on meego mailing lists (which are primarily focused on development topics).
Metric: Number of posts
In Maemo, the equivalent karma contribution is 2 * sqrt(# posts).
As it stands, this does not degrade over time. An alternative metric would be: (yesterday's metric * 0.99) + today's posts.
Reporting or commenting on bugs.
Metric: (6 * Number of bug reports opened over last 12 months) + Number of bug comments written over last 12 months
In Maemo, the equivalent karma contributions are: 6 * sqrt(# bugs reported), sqrt(# bug comments)
Contributing to discussions on the forum, which are typically community or application development related.
Metric: (8 * Number of thanks for posts written over last 6 months) + (Number of posts over last 6 months)
In Maemo, the equivalent karma contributions are: 8 * sqrt(# thanks), sqrt(# posts)
Contributing to Wiki pages. It is hard to measure the value of each contribution, so the metric is kept simple.
Metric: Number of edits over last 12 months
In Maemo, the equivalent karma contribution is: 6 * sqrt(# edits)
These areas may be relevant in the future (they are mostly things which exist in the Maemo karma system). However, they are not proposed for the initial set of metrics.
Commenting on or voting for news items.
Metric: (4 * Number of comments) + Number of thumbs (up or down)
In Maemo, the equivalent karma contributions are: 2 * sqrt(# comments) and 0.25 * sqrt(# thumbs)
Testing community applications.
Metric: Number of thumbs
In Maemo, the equivalent karma contribution is: 0.5 * # thumbs
If a brainstorm process is adopted then some variant on the Maemo karma metric might be used. The maemo karma contribution is 5 for idea under vote or in development, 10 for implemented idea, 2 for solution under vote or in development, 10 for implemented solution.