Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
Received-SPF: pass (nike.apache.org: domain of luispo@gmail.com designates
 209.85.223.196 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2064\))
Subject: Re: Code of Conduct - links to why they are needed etc
From: =?utf-8?Q?Louis_Su=C3=A1rez-Potts?= <luispo@gmail.com>
In-Reply-To: 
 <CAK2iWdRfQf741hRJLQYzJdd_gcS8qBEk=vV46+VS=PUnxaHzpA@mail.gmail.com>
Date: Sun, 21 Dec 2014 17:06:13 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <761D7FAC-8686-45A2-8E36-AD88BFE0F3D2@gmail.com>
References: 
 <CAOGo0VZx_sHD4pYMwKNjE-sJizoySeFf1UkLTvEeCYZfLXHb8Q@mail.gmail.com>
 <46083F55-9184-4866-B0A9-AB0C985ECD6D@jaguNET.com>
 <9AEE4665-D7C9-49E1-81BA-8945B10E5CB2@gmail.com>
 <CAK2iWdRfQf741hRJLQYzJdd_gcS8qBEk=vV46+VS=PUnxaHzpA@mail.gmail.com>
To: dev@community.apache.org

Hi

this is a whimsical post. (also a top post)
But here=E2=80=99s a cute code of conduct video.

http://goo.gl/UZF7CW


> On 20 Dec 2014, at 15:14, jan i <jani@apache.org> wrote:
>=20
> On 20 December 2014 at 20:55, Louis Su=C3=A1rez-Potts =
<luispo@gmail.com> wrote:
>=20
>> Hi,
>>> On 20 Dec 2014, at 09:50, Jim Jagielski <jim@jagunet.com> wrote:
>>>=20
>>> This is great and, as noted, long overdue. Although the code
>>> itself "simply" codifies what had been the tribal knowledge
>>> of the ASF, and how we'd expected people to behave, NOT having
>>> it written down was pretty sad.
>>>=20
>>> Thx to all for making it happen.
>>>=20
>>>> On Dec 20, 2014, at 6:33 AM, sebb <sebbaz@gmail.com> wrote:
>>>>=20
>>>> There are some useful links in the CoC blog:
>>>>=20
>>>>=20
>> =
https://blogs.apache.org/foundation/entry/asf_publishes_long_overdue_code
>>>>=20
>>>> For example,
>>>> Ashe Dryden's introductory resource for learning more about how =
Codes
>>>> of Conduct can help
>>>>=20
>>>> Perhaps these should be added to the ASF CoC page at
>>>>=20
>>>> http://www.apache.org/foundation/policies/conduct.html
>>>=20
>>=20
>> So, now that it is written down=E2=80=94great=E2=80=94does this mean =
then that we will be
>> asking all new projects (and podlings and everything else) to =
obligatorily
>> review it? As part of the Apache Way? That is, what is the =
relationship
>> between this CoC and the Apache Way from the perspective of the new =
member
>> to Apache?
>>=20
>=20
> maybe I see it wrong, but to me a "code of conduct" is more a =
guideline
> than an actual rulebook. It is a description of how we would like to
> interact with other, and therefore not something that should be used =
as
> "you did not follow the code of conduct, so now I take action".
>=20
> I think it is important to see both the "apache way" and "code of =
conduct"
> as guidelines, not something formulated by lawyers to stand up in =
court.
>=20
> So in essence we should all be aware of what the intention is and that
> includes podlings coming to apache.
>=20
> rgds
> jan i.
>=20
>=20
>> Louis