I strongly disagree with this. We have enough trouble attracting committers as it is. By making this a policy we're throwing up a barrier to contributors becoming committers.
I was at the Texas Linux Fest this weekend and I asked Karen Sandler, Lawyer and Executive Director of Software Freedom Conservancy (a FOSS foundation), about this. The answer (of course) was "It depends." Among other things, it depends on the company that is employing the committer. That company may have a very strong policy about what email address gets used on commits. Just because a committer may come from a company with such a policy, doesn't mean that we should automatically exclude them. We need to look into the future and consider the consequences of our actions before making preference a policy. This is not about Rackspace. Rackspace is very open source centric and very committed to upstream projects. Committers are able to use their discretion for what email addresses they use on commits. My personal preference is to use my Rackspace email address because they pay me to work on open source and I'm proud about that. This is not about intellectual property (AFAIK). The email address used in no way imparts any IP ownership. I've read nothing on [1] and [2] that requires a committer to use their @apache.org. If requiring an @apache.org email in commits is not mandated by the ASF, it should not be mandated by jclouds. This is not a conversation that belongs in a pull request. I'll email the our dev list to get more visibility on it. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/397#issuecomment-46192797
