Implement a committer badging programme
We're going to implement a committer badging programme. The basic idea is that we'll use an existing badging system to grant a "Committer" badge to our committers.
We'll keep this simple: anybody who has committer status on at least one Eclipse open source project is entitled to the badge.
- When somebody gets committer status (either by being elected to committer status on an existing project via committer election, or as an initial committer on a new project), we enter them into the badge system. When an individual who is a committer on an existing project, gets committer status on another project, they will be offered a committer badge only if they do not already have one.
- Existing committers will be given an opportunity to request a badge (e.g., we use the mailing list to tell committers to contact emo-records to request the badge).
- Legacy committers (that is, folks who have previously held committer status, but do not currently have an active committer role) will be treated as existing committer (except that they won't be necessarily be notified that the programme exists, and so will have to find us themselves).
Initially, we do this manually; after we get experience with the service provider, we'll explore automation options.
By way of background… we’d considered making this more complex, but the corner cases/grey area will kill us. We could, for example, make creating some number of commits be a requirement, but then we’d have to distinguish between commits made while establishing merit before becoming a committer and those created after getting status. This distinction is arbitrary and will undoubtedly be challenged. At some point, we should consider “activeness” badges, but let’s keep that as a separate consideration.
/cc @skilpatrick @karlafb