Dave, It is considered very bad form to mix public and private lists in an email. I have thus deleted the private@ list from my response.
I think your suggestion is a good one, but I might suggest that you ask for "non-Apache email contact address". Having the new committer set up the forwarding address themselves has the secondary purpose that they verify that they can log in to the id.apache.org site. A tertiary purpose is to emphasize that the new committer should take care of some things themselves and doing this on id.a.o helps them learn how this should happen. The real virtue of what you suggest is, in any case, that it eliminates a round-trip that is often impossible because of lack of information. In the worst case, the round-trip happens where it might not have done so before, in the best case the extra round trip is not needed at all. I think that your second suggestion has fewer moving parts and is thus a bit better. The first suggestion does have the benefit that we have a durable record of what was at least for a moment a valid address for the new committer. I still think that the second option is better, even so. On Wed, Oct 14, 2015 at 1:07 PM, Dave Birdsall <dave.birds...@esgyn.com> wrote: > Hi, > > > > I’m a committer/PMC member on the Trafodion podling. > > > > One thing I’m noticing about the new committer process // > community.apache.org/newcommitter.html#new-committer-process is that we > sometimes get hung up on the step, “Request creation of the committer > account”. > > > > The reason for the hang up often seems to be, the new committer has > expressed a desire for a particular apache ID, but has not specified where > e-mail for that ID should be forwarded to. > > > > Now, the iCLA form itself asks for the preferred apache ID. But that form > does not ask about forwarding e-mail ID. Too, the receipt of the iCLA is > forwarded to the podling’s private list, but not the iCLA itself. > > > > Also, the committer accept template makes no mention of providing a > forwarding e-mail address. > > > > So, the mentor has to ask. And the mentor often doesn’t have an e-mail > address for the new person. So that request has to be relayed through the > podling PMC private list, and someone there who knows the individual can > ask. > > > > I can think of a couple of ways to make this more efficient. > > > > 1. Change the iCLA to include forwarding e-mail address. And when the > iCLA is received, it is shared with the podling private list. > > 2. Alternatively, change the committer accept template in // > community.apache.org/newcommitter.html#new-committer-process to ask for a > forwarding e-mail ID along with asking for the preferred apache ID. > > > > Thoughts? > > > > Thanks, > > > > Dave >
