I use my personal email address for commits unless I'm told to do so otherwise. I find this to be the best way to ensure that several years down the road, someone can contact me to discuss some change I made at one point.
My stance is that software does rot, and if I can be reached to maybe help someone resuscitate some project back into life, the easier I can make that possible, the better. Matt On Tue, Jun 17, 2014 at 11:57 AM, Everett Toews <everett.to...@rackspace.com > wrote: > On Jun 16, 2014, at 3:14 PM, Andrew Gaul <g...@apache.org> wrote: > > > I agree that we should have few requirements, e.g., we should not > > *require* contributors to be nice to each other. However, we should > > *encourage* certain behaviors, e.g., contributors should treat each > > other with respect. > > Honestly, this e.g. has taken me aback. Presumably you’re referring to my > 2nd email on this thread. > > I felt strongly about the issue and stated my opinion as such. Reading > back on it I can see that the tone is much too harsh. I apologize for that. > > Nice is relative but I promise you that I approached this issue the way I > did out of respect for you, AP, and the jclouds community. This discussion > didn’t belong in a PR so I moved it here for more visibility by the > community. > > My 2nd email (admittedly an overly harsh rant) could easily have been the > initial email. Instead, I tried to objectively state the facts to start the > discussion. I did this out of respect for the community. > > > I recommend using the Apache branding when representing the project. > > Tagging commits and emails emphasizes the project first and other > > affiliations second. When wearing my Apache hat[1], committers and > > users should expect me to act in the best interests of the project and > > not my or an employer's interests. Using apache.org livery reinforces > > these behaviors and perceptions. That being said, I do not plan to > > police every social interaction or inspect every commit email address. > > > > [1] http://www.apache.org/foundation/how-it-works.html#hats > > Thanks for the link, I hadn’t come across this before. It definitely gives > me a much better idea of the ASF perspective on the issue. > > Yes I act in the best interests of the project. I’m also fortunate to work > for an employer whose interests are also aligned with those of the project. > That’s why I feel comfortable using my Rackspace email. But this definitely > gives me something to think about and consider. > > The important part to me is that we don’t exclude some future committer > because their company policy requires that they use their corporate email > in commits. > > > On Mon, Jun 16, 2014 at 12:08:28PM -0600, Chris Custine wrote: > >> FWIW, In my 8 years as a committer, PMC member, chair, etc on 8+ Apache > >> projects, I don't recall ever having this discussion before. > Informally, I > >> have always encouraged people to use either their apache.org address > or at > >> least a personal gmail address where possible just to reduce the > >> "perception" of corporate sponsorship. However, I have seen people use > >> their corporate email addresses and I am not aware of any rule expressly > >> forbidding that. > > I’d say your 8+ years of experience is worth a lot. :) > > Thanks for your views on this. > > Regards, > Everett > >
