Hey Scott.
Here are some answers...
1. How does the project lead get email addresses for committers that appear to be inactive to confirm that that they no longer can continue to contribute to the project?
The EF cannot provide email addresses. To do so would violate the privacy policy. The practice that other project leads follow is to use the PMI to determine which committers are inactive and then post the names of inactive committers on the project's main communication channel (usually the dev list or an issue) with instructions for those individuals to respond if they feel that they should retain committer status. Set a reasonable deadline and retire everybody who does not respond when that date passes.
This technique has the benefit of being entirely transparent.
If the list of committers is so large that flipping through the PMI pages to determine who is active and who is not is especially cumbersome, then you can ask the EMO to run a query and generate a list for you.
Bear in mind that committer status is an important part of the IP workflows in the specification process and that it is normal to have inactive committers who represent member companies on specification projects.
2. Any advice on retiring committers that appear inactive but they may become active if no one else can do work?
Traditionally, we have deferred to project leads and the PMC to decide what makes sense for the project. More recently, however, the EMO and Security Team have started to be concerned that long-term inactive committers represent a potential security risk. This is a topic that I intend to bring up with the Eclipse Technical Advisory Council.
We tend to not put value on what somebody may do.
3. How long should the project lead wait for a response from an inactive committer before retiring them?
My thinking is that the sweet spot is four weeks, and never during the summer.
If you make a horrible, horrible mistake and retire somebody by accident, contact the EMO and we'll help you sort it out.
HTH,
Wayne