community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jan i <j...@apache.org>
Subject Re: Code of Conduct - links to why they are needed etc
Date Sat, 20 Dec 2014 20:14:30 GMT
On 20 December 2014 at 20:55, Louis Suárez-Potts <luispo@gmail.com> wrote:

> Hi,
> > On 20 Dec 2014, at 09:50, Jim Jagielski <jim@jagunet.com> wrote:
> >
> > 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.
> >
> > Thx to all for making it happen.
> >
> >> On Dec 20, 2014, at 6:33 AM, sebb <sebbaz@gmail.com> wrote:
> >>
> >> There are some useful links in the CoC blog:
> >>
> >>
> https://blogs.apache.org/foundation/entry/asf_publishes_long_overdue_code
> >>
> >> For example,
> >> Ashe Dryden's introductory resource for learning more about how Codes
> >> of Conduct can help
> >>
> >> Perhaps these should be added to the ASF CoC page at
> >>
> >> http://www.apache.org/foundation/policies/conduct.html
> >
>
> So, now that it is written down—great—does 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?
>

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".

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.

So in essence we should all be aware of what the intention is and that
includes podlings coming to apache.

rgds
jan i.


> Louis
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message