Ah man, look what I started! ;)

After reading the link about various ³hats², my preference is to use my
Apache identity going forward. I believe that using the @apache.org email
address brings a level of humility to the work we do on the project.

I agree that we should encourage it from the community perspective. As I
have learned from human nature, enforcement typically causes resistance.
Unless our employers have an open source contribution policy, this is
really a personal preference. Each of us will need to determine what is
the most appropriate for them.

Another learning experience with the ASF!

/jd



On 6/16/14, 1: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.
>
>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
>
>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.
>> 
>> Chris
>> 
>> --
>> Chris Custine
>> 
>> 
>> 
>> On Mon, Jun 16, 2014 at 9:33 AM, Everett Toews
>><everett.to...@rackspace.com>
>> wrote:
>> 
>> > The issue of whether or not to require an apache.org email address for
>> > committers came up in a pull request a few days ago [1]. A change was
>>made
>> > to the Committer¹s Guide [2] requiring committers to use their
>>apache.org
>> > email address.
>> >
>> > This change was premature as it did not get consensus from the
>>jclouds¹
>> > committers. The issue needs to be discussed before this change can be
>> > considered a requirement.
>> >
>> > Everett
>> >
>> > [1] https://github.com/jclouds/jclouds/pull/397#issuecomment-45972870
>> > [2] https://wiki.apache.org/jclouds/Committers%20Guide?action=diff
>
>-- 
>Andrew Gaul
>http://gaul.org/

Reply via email to