Gathering metrics for the Adoption programme

[Martijn Verburg]

Hi all,

**Important - please remember to sign-up to the
adoption-discuss at openjdk.java.net mailing list and reply to this thread
there please**

We'd like to measure & report to the OpenJDK governing board some
quantifiable metrics on the impact and effectiveness of the Adoption
programme. These metrics will also be useful to the group in terms of
helping us determine whether we are fulfilling our mission statement and
purpose.

Here's my proposal on the metrics, I'd love people's feedback on this:

Initial Onboarding:
=============

* Number of mailing list users
* Message volume on the mailing list
* Number of new developers successfully building OpenJDK / Downloads of
OpenJDK development virtual machine
* Number of unique visitors to Adoption page/wiki
** Perhaps measure impact on overall OpenJDK visits

Betterrev:
=======

Betterev is a proposed patch workflow & build farm system. It will act as
community clearing house for new contributors and as a prototype for
OpenJDK infrastructure.

* Number of patches submitted to Betterrev (a community clearing house for
new contributors)
** Number of patches subsequently committed to OpenJDK

QA:
===

* Number of FOSS projects involved in testing OpenJDK nightly builds
* Number of bugs/issues reviewed by adoption group for quality control
purposes.

Longterm Onboarding:
================

* Number of 'graduates' from Adoption programme into official OpenJDK
contributors, authors, committers and reviewers.

Cheers,
Martijn