On Jun 16, 2014, at 11:52 AM, Andrew Phillips <aphill...@qrmedia.com> wrote:
> I certainly agree with the aim of encouraging people to become committers as > much as possible, so if we feel that using an @apache.org address could be a > barrier here, we should reconsider that. > > Do we have any evidence that this particular requirement has been a barrier > to anyone involved with jclouds? Not to date. This is the kind of thing that would bite us badly in the process of making someone a committer. We would invite someone on as a committer, they accept, they start going through the whole process of getting the ICLA and/or CCLA signed off by their company's lawyers. It actually gets signed off. They make their first commit using their company email address because that’s their company policy and the way they’ve always done it. We say, oh no, you can’t do that. Talking to Karen from the Software Freedom Conservancy was very eye opening for me on this and why I feel so strongly about it. I would much rather address this now rather than it become a problem for someone who wants to become a committer in the future. > Also, there may have been a misunderstanding on my part: I was under the > impression that anyone with commit rights to the jclouds repos would need to > have an ASF ID simply to be able to commit, i.e. that committers would *have* > an @apache.org address by definition, and that the question is mainly about > whether to *use* it or not. This is my understanding as well. And that it’s up to the committer’s discretion whether to use it or not. Everett
