Re: [WG: Code of conduct] Proposal

ubscribe by sending email to dev-unsubscr...@community.apache.org <mailto:dev-unsubscr...@community.apache.org> > > From: Rich Bowen > Sent: Saturday, June 15, 2024 8:57:25 AM > To: ASF ComDev > Subject: Re: [WG: Code of conduct] Proposal

Re: [WG: Code of conduct] Proposal

I don't understand why I'm seeing these emails. Get Outlook for Android<https://aka.ms/AAb9ysg> From: Rich Bowen Sent: Saturday, June 15, 2024 8:57:25 AM To: ASF ComDev Subject: Re: [WG: Code of conduct] Proposal On Wed, Jun 12, 2024, 22:12 Just

Re: [WG: Code of conduct] Proposal

On Wed, Jun 12, 2024, 22:12 Justin Mclean wrote: > Hi, > > Can you give us some idea of what you have already changed in the CoC > text, I expected a little more from the version control history. > I changed "community leaders" to PMC members a few places. I believe that's the only chance I made

Re: [WG: Code of conduct] Proposal

Hi, Can you give us some idea of what you have already changed in the CoC text, I expected a little more from the version control history. Kind Regards, Justin - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For a

Re: [WG: Code of conduct] Proposal

Cool. Started here: https://github.com/apache/comdev-working-groups/tree/main/wg-code-of-conduct Let’s discuss specific changes to the text here, with a [WG: Code of conduct] tag in email subjects. Thanks. — Rich Bowen rbo...@rcbowen.com

Re: [WG: Code of conduct] Proposal

Hi, I can also help out here. Kind Regards, Justin - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org

Re: [WG: Code of conduct] Proposal

>>>> wrote: >>>> >>>> Hi, >>>> >>>> On Mon, Jun 10, 2024 at 3:33 PM Rich Bowen wrote: >>>>> ...Many ASF projects do not have a code of conduct, and push this up to >>>>> the Foundation. This mostly

Re: [WG: Code of conduct] Proposal

10, 2024 at 3:33 PM Rich Bowen wrote: >>>> ...Many ASF projects do not have a code of conduct, and push this up to >>>> the Foundation. This mostly seems >>>> to work, in practice, most of the time, but the public *perception* is >>>> just that the

Re: [WG: Code of conduct] Proposal

> On Jun 11, 2024, at 06:31, Rich Bowen wrote: > >> On Jun 11, 2024, at 6:05 AM, Bertrand Delacretaz >> wrote: >> >> Hi, >> >> On Mon, Jun 10, 2024 at 3:33 PM Rich Bowen wrote: >>> ...Many ASF projects do not have a code of conduct, a

Re: [WG: Code of conduct] Proposal

> On Jun 11, 2024, at 6:05 AM, Bertrand Delacretaz > wrote: > > Hi, > > On Mon, Jun 10, 2024 at 3:33 PM Rich Bowen wrote: >> ...Many ASF projects do not have a code of conduct, and push this up to the >> Foundation. This mostly seems >> to work, in practi

Re: [WG: Code of conduct] Proposal

> On Jun 11, 2024, at 03:05, Bertrand Delacretaz wrote: > > Hi, > > On Mon, Jun 10, 2024 at 3:33 PM Rich Bowen wrote: >> ...Many ASF projects do not have a code of conduct, and push this up to the >> Foundation. This mostly seems >> to work, in practice,

Re: [WG: Code of conduct] Proposal

Hi, On Mon, Jun 10, 2024 at 3:33 PM Rich Bowen wrote: > ...Many ASF projects do not have a code of conduct, and push this up to the > Foundation. This mostly seems > to work, in practice, most of the time, but the public *perception* is just > that they don’t have one... I think

[WG: Code of conduct] Proposal

Hi, folks, At our board face-to-face meeting in Bratislava last weekend, the topic of a code of conduct was raised. Without getting into all of the historical confusion around our code of conduct, I have a proposal for a working group: TL;DR: We should create a recommended template Code of

Re: Code of Conduct - Over Responding

te: >> > >> >> The challenge with a CoC is knowing when to quit before becoming the >> >> thought police. Also, it should be things that are measurable and >> >> enforceable. I don't think this is either. >> >> >> >> What you are

Re: Code of Conduct - Over Responding

ice. Also, it should be things that are measurable and > >> enforceable. I don't think this is either. > >> > >> What you are suggesting is really good advice, but isn't something we > can > >> enforce with policy. > >> > > > > Th

Re: Code of Conduct - Over Responding

n't think this is either. >> >> What you are suggesting is really good advice, but isn't something we can >> enforce with policy. >> > > The Code of Conduct is mostly not "measurable and enforceable" and just > contains good advice - of the seven sect

Re: Code of Conduct - Over Responding

od advice, but isn't something we can > enforce with policy. > The Code of Conduct is mostly not "measurable and enforceable" and just contains good advice - of the seven sections the only we can enforce is the "Be careful in the words that we choose" section. I dont

Re: Code of Conduct - Over Responding

00 PM, "Niall Pemberton" wrote: > >> Hi, >> >> I really like the code of conduct, but I think it would be good to include >> something about sending too many emails. Sometimes you get people who >> dominate a thread, responding to almost everyone and they d

RE: Code of Conduct - Over Responding

+1 This is not really a CoC issue, more of a best practice one. Sent from my Windows 10 phone From: Rich Bowen<mailto:rbo...@rcbowen.com> Sent: Sunday, June 5, 2016 5:17 PM To: dev@community.apache.org<mailto:dev@community.apache.org> Subject: Re: Code of Conduct - Over Respo

Re: Code of Conduct - Over Responding

16 8:00 PM, "Niall Pemberton" wrote: > Hi, > > I really like the code of conduct, but I think it would be good to include > something about sending too many emails. Sometimes you get people who > dominate a thread, responding to almost everyone and they drain the ener

Code of Conduct - Over Responding

Hi, I really like the code of conduct, but I think it would be good to include something about sending too many emails. Sometimes you get people who dominate a thread, responding to almost everyone and they drain the energy of others to take part. My suggestion is to add a sentence to the &qu

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

I have done enough. If you feel that is not the case to satisfy you bureaucratic need, you go ahead and scratch that itch. Best regards, Pierre Smits *ORRTIZ.COM * Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrt

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

On Fri, Jul 10, 2015 at 10:56 AM, Pierre Smits wrote: > Tim, > > It seems you're rather fond of it. Huh? I'm not sure what "it" is or why you're making observations about what I'm fond of. > Quite the number of posters in this > thread are particpating in either body, or both. I feel confident t

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

On 10 July 2015 at 12:56, Pierre Smits wrote: > Tim, > > It seems you're rather fond of it. Quite the number of posters in this > thread are particpating in either body, or both. I feel confident that they > can take it as input from here and discuss appropriate follow-up in their > specific mail

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

Tim, It seems you're rather fond of it. Quite the number of posters in this thread are particpating in either body, or both. I feel confident that they can take it as input from here and discuss appropriate follow-up in their specific mailing lists. Best regards, Pierre Smits *ORRTIZ.COM

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

On Fri, Jul 10, 2015 at 10:23 AM, Pierre Smits wrote: > Branko, > > I am confident that the existing project with bylaws, policies and/or > standing rules formalised has had its share of discussions regarding > applicability of elements therein.. And have resolved those. I guess that > when such a

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

l 6, 2015 at 10:51 AM, Branko Čibej wrote: > >> > >>> On 04.07.2015 18:34, Pierre Smits wrote: > >>>> Having done a cursory review of the incubator reports to the board for > >>>> this year (January till May/June 2015), I found that only the SAMO

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

gt;> Based Manufacturing, Professional > > >> Services and Retail & Trade > > >> http://www.orrtiz.com > > >> > > >> On Mon, Jul 6, 2015 at 10:51 AM, Branko Čibej > wrote: > > >> > > >>> On 04.07.2015 18:34, Pierre

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

rofessional > >> Services and Retail & Trade > >> http://www.orrtiz.com > >> > >> On Mon, Jul 6, 2015 at 10:51 AM, Branko Čibej wrote: > >> > >>> On 04.07.2015 18:34, Pierre Smits wrote: > >>>> Having done a cursory review o

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

Pierre Smits wrote: >>>> Having done a cursory review of the incubator reports to the board for >>>> this year (January till May/June 2015), I found that only the SAMOA >>>> podling reported working on a project set of bylaws, which without >>>> knowing

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

t; will quote my summary from earlier in this thread: "In the absence of > [project] bye-laws the defaults apply. " > > -Original Message- > From: Pierre Smits [mailto:pierre.sm...@gmail.com] > Sent: Monday, July 6, 2015 11:09 AM > To: dev@community.apache.org

RE: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

erre Smits [mailto:pierre.sm...@gmail.com] Sent: Monday, July 6, 2015 11:09 AM To: dev@community.apache.org Subject: Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying) I am confident, Ross, that you are equally capable of doing that. So why don'

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

e Smits wrote: > > > Having done a cursory review of the incubator reports to the board for > > > this year (January till May/June 2015), I found that only the SAMOA > > > podling reported working on a project set of bylaws, which without > > > knowing details

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

I am confident, Ross, that you are equally capable of doing that. So why don't you give it a go? Best regards, Pierre Smits *ORRTIZ.COM * Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Mon, Jul 6, 201

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

No worries, Konstantin. I won't hold that against you. Best regards, Pierre Smits *ORRTIZ.COM * Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Mon, Jul 6, 2015 at 8:57 PM, Konstantin Boudnik wrote:

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

Just to point to the source of my confusiony. My impression came from this part: > > > Like expressed earlier, that loosely way of interpreting ASF guidelines > > > has > > > led to the situation that the board charges newly established projects to > > > define its bylaws. Charges that are then d

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

So can you summarize what you are saying. Sent from Surface From: Pierre Smits Sent: ?Monday?, ?July? ?6?, ?2015 ?10?:?47? ?AM To: dev@community.apache.org Hi Konstantin, No, I am not saying that, neither explicitly nor effectively

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

Hi Konstantin, No, I am not saying that, neither explicitly nor effectively. Thus no, not a correct representation of the point of discussion. Maybe you got that impression (regarding blanket bylaws, or projects going off the handle) by reading the postings of others. Best regards, Pierre Op ma

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

Let me see if I read you right, Pierre. Effectively, you're saying that imposing a blanket bylaws system should help to prevent some rare cases of established projects going off the handle? Is this a correct representation of the point of this discussion? I am not as eloquent as you're in paintin

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

board for this > year (January till May/June 2015), I found that only the SAMOA podling > reported working on a project set of bylaws, which without knowing details > could encompass and/or incorporate the code of conduct. > None of the other podlings reported about that. Having looked also

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

https://plus.google.com/+GoogleArtProject On 6 Jul 2015 23:45, "Pierre Smits" wrote: > Actually, Martin, I read that too a while ago, and I can't regard it as > anything else but just a viewpoint expressed by someone who is reacting to > a posting of someone else > > Such an expression neithe

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

Actually, Martin, I read that too a while ago, and I can't regard it as anything else but just a viewpoint expressed by someone who is reacting to a posting of someone else Such an expression neither makes it a policy of the ASF, nor justifies why the board, when voting on a podling wishing gr

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

On 6 Jul 2015 20:26, "Benson Margulies" wrote: > > This thread started with a discussion of the CoC. The premise of the > thread was this: that counter-CoC behavior might emerge on a project, > and that the project might tolerate, or even celebrate, that behavior, > for lack of an explicit bylaw e

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

On Mon, Jul 6, 2015 at 12:51 AM, Branko Čibej wrote: > I find myself disgusted by this widespread assumption that each project > needs its own bylaws. WTF for? Are not ASF policies and practices enough > for everyone? What sort of bylaws could you possibly invent that are > both a useful extensio

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

This thread started with a discussion of the CoC. The premise of the thread was this: that counter-CoC behavior might emerge on a project, and that the project might tolerate, or even celebrate, that behavior, for lack of an explicit bylaw explicitly adopting the CoC. This premise is wrong. The Co

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

015 at 10:51 AM, Branko Čibej > wrote: > >> > >> > On 04.07.2015 18:34, Pierre Smits wrote: > >> > > Having done a cursory review of the incubator reports to the board > for > >> > > this year (January till May/June 2015), I found that only the

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

tp://www.orrtiz.com>* > >> Services & Solutions for Cloud- > >> Based Manufacturing, Professional > >> Services and Retail & Trade > >> http://www.orrtiz.com > >> > >> On Mon, Jul 6, 2015 at 10:51 AM, Branko Čibej wrote: > &g

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

Services and Retail & Trade >> http://www.orrtiz.com >> >> On Mon, Jul 6, 2015 at 10:51 AM, Branko Čibej wrote: >> >> > On 04.07.2015 18:34, Pierre Smits wrote: >> > > Having done a cursory review of the incubator reports to the board for >> > >

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

And you can read 'determination' as well as 'perception'. Best regards, Pierre Smits *ORRTIZ.COM * Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Mon, Jul 6, 2015 at 1:34 PM, Pierre Smits wrote: > L

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

Like expressed earlier, that loosely way of interpreting ASF guidelines has led to the situation that the board charges newly established projects to define its bylaws. Charges that are then disregarded by the project and not followed up on by the board and or the appointed VP of the project. It i

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

On Mon, Jul 6, 2015 at 11:38 AM, Pierre Smits wrote: > ...The latest posting by Jan proves the point of the necessity of good > per-project bylaws when it comes to deviating from the generic guidelines > of the ASF... But as others have said, the best is to stick to those guidelines and use the d

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

; On Mon, Jul 6, 2015 at 10:51 AM, Branko Čibej wrote: > > > > > On 04.07.2015 18:34, Pierre Smits wrote: > > > > Having done a cursory review of the incubator reports to the board > for > > > > this year (January till May/June 2015), I found that only the

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

mits wrote: > > > Having done a cursory review of the incubator reports to the board for > > > this year (January till May/June 2015), I found that only the SAMOA > > > podling reported working on a project set of bylaws, which without > > > knowing details could e

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

2015), I found that only the SAMOA > > podling reported working on a project set of bylaws, which without > > knowing details could encompass and/or incorporate the code of conduct. > > I find myself disgusted by this widespread assumption that each project > needs its own b

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

o make its philosophies interpretable in only one way, I hear/see a lot of variants of what is the Apache Way or the Apache Code of Conduct from various - fellow - ASF politicians (pun intended :-)). It is bylaws that decrease the ambiguity instilled in the ASF pages, ensuring that due process is

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

mpass and/or incorporate the code of conduct. I find myself disgusted by this widespread assumption that each project needs its own bylaws. WTF for? Are not ASF policies and practices enough for everyone? What sort of bylaws could you possibly invent that are both a useful extension of these policies a

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

Hi, On Sun, Jul 5, 2015 at 6:30 AM, Pierre Smits wrote: > if a project wants to deviate from the general rule of a simple > majority voting for specific aspects - think off changing the direction or > goal of the project, or e.g. every registered contributor (iCLA filed) has > a vote with re

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

sence of bye-laws the defaults apply. > >> > >> Sent from my Windows Phone > >> ____________ > >> From: Pierre Smits<mailto:pierre.sm...@gmail.com > > >> Sent: ‎7/‎4/‎2015 3:35 PM > >> To: dev@community.apache.org dev@communit

RE: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

rtant, hence the defaults apply. Sent from my Windows Phone From: Pierre Smits<mailto:pierre.sm...@gmail.com> Sent: ‎7/‎4/‎2015 9:30 PM To: dev@community.apache.org<mailto:dev@community.apache.org> Subject: Re: Incubating, Graduating & Code of conduct @

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

of the incubator to make sure > that > > exactly this happened. > > Having done a cursory review of the incubator reports to the board for this > year (January till May/June 2015), I found that only the SAMOA podling > reported working on a project set of bylaws, which without kn

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

As it has been established in the "Veto! Veto?" thread that with procedural issues a bit more is required than the generic statements in the Code of Conduct and other pages describing the Apache Way. Especially if a project wants to deviate from the general rule of a simple majority

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

On Sat, Jul 4, 2015 at 4:12 PM, Benson Margulies wrote: > In fact, I told at least one podling that bylaws are a faint smell of > trouble -- if you have enough conflict to feel the need to write down > the rules, you might do better working out the reason for the conflict > than writing down the r

RE: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

under a set of principles, known collectively as the 'Apache Way'. If you are new to Apache development, please refer to the Incubator Project for more information on how Apache projects operate. Looking specifically at a code of conduct, the foundation has one and projects are expect

RE: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

- From: Benson Margulies [mailto:bimargul...@gmail.com] Sent: Saturday, July 4, 2015 4:13 PM To: dev@community.apache.org Subject: Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying) Writing as someone who has mentored a squad of podlings, I do not bel

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

ces and Retail & Trade >> http://www.orrtiz.com >> >> On Sun, Jul 5, 2015 at 1:36 AM, Ross Gardler (MS OPEN TECH) < >> ross.gard...@microsoft.com> wrote: >> >>> In the absence of bye-laws the defaults apply. >>> >>> Sent from my Wind

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

>> From: Pierre Smits<mailto:pierre.sm...@gmail.com> >> Sent: ‎7/‎4/‎2015 3:35 PM >> To: dev@community.apache.org<mailto:dev@community.apache.org> >> Subject: Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off >> of Bette

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

Smits<mailto:pierre.sm...@gmail.com> > Sent: ‎7/‎4/‎2015 3:35 PM > To: dev@community.apache.org<mailto:dev@community.apache.org> > Subject: Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off > of Better specifying) > > How can that be? The board o

RE: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

to be in the > spirit of the Apache Way but tuned to the specifics of that project. > > Sent from my Windows Phone > > From: Pierre Smits<mailto:pierre.sm...@gmail.com> > Sent: ‎7/‎4/‎2015 3:16 PM > To: dev@community.apache.org<mailto:

Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

specifics of that project. > > Sent from my Windows Phone > > From: Pierre Smits<mailto:pierre.sm...@gmail.com> > Sent: ‎7/‎4/‎2015 3:16 PM > To: dev@community.apache.org<mailto:dev@community.apache.org> > Subject: Incubating, Graduating &

RE: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

Smits<mailto:pierre.sm...@gmail.com> Sent: ‎7/‎4/‎2015 3:16 PM To: dev@community.apache.org<mailto:dev@community.apache.org> Subject: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying) Off list? I am sure that quite a few more than just I coul

Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

icrosoft.com> > Sent: ‎7/‎4/‎2015 10:08 AM > To: dev@community.apache.org<mailto:dev@community.apache.org> > Subject: RE: Incubating, Graduating & Code of conduct @ The ASF (spin-off > of Better specifying) > > The ASF is about doing the right thing in code, not

RE: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

From: Ross Gardler (MS OPEN TECH)<mailto:ross.gard...@microsoft.com> Sent: ‎7/‎4/‎2015 10:08 AM To: dev@community.apache.org<mailto:dev@community.apache.org> Subject: RE: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying) The ASF is about

RE: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

9:34 AM To: dev@community.apache.org<mailto:dev@community.apache.org> Subject: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying) >> Having such an official ASF policy without the executing office policing >> it, without podlings being required to accept an

Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)

project set of bylaws, which without knowing details could encompass and/or incorporate the code of conduct. None of the other podlings reported about that. Having looked also at the board reports for January up to May 2015 I found that podlings graduating to TLP were either tasked by the board to est

Re: Better specifying the scope of our Code of Conduct

Hi, As there was no opposition I have modified the first few paragraphs of http://www.apache.org/foundation/policies/conduct.html as below. -Bertrand On Tue, Jun 30, 2015 at 1:01 PM, Bertrand Delacretaz wrote: > *** reworked code of conduct intro section *** > This code of conduct appl

Re: Better specifying the scope of our Code of Conduct

projects are largely independent *when it comes to technical matters*, but as far as governance there's a number of invariants that are ASF-wide. This code of conduct is one of those invariants. -Bertrand

RE: Better specifying the scope of our Code of Conduct

scope of our Code of Conduct As Jan is saying, this is simply not accurate. "Official Policy" must be followed by all projects, and anyone can raise the concerns to various committees or board, when they think there is ongoing violation and no interest from a project to rectify it.

Re: Better specifying the scope of our Code of Conduct

y that the project must use ALv2, but also about what can be dependent upon, how to package tarballs with LICENSE and NOTICE files, and policy around patents) is just one out of a handful policies that must be complied with, by ALL projects. Branding and Code of Conduct are two other. How to package,

Re: Better specifying the scope of our Code of Conduct

On 2 July 2015 at 18:05, Pierre Smits wrote: > It is a good thing that the board and the President regard the Code of > Conduct page as an official ASF policy and expect others to follow it, but > when at least one of its members in more than one occasion states that > projects are

Re: Better specifying the scope of our Code of Conduct

It is a good thing that the board and the President regard the Code of Conduct page as an official ASF policy and expect others to follow it, but when at least one of its members in more than one occasion states that projects are independent (of the ASF) regarding how they conduct their business

Re: Better specifying the scope of our Code of Conduct

On 6/30/15 2:04 PM, Rich Bowen wrote: > > > On 06/30/2015 12:37 PM, Stefan Reich wrote: >> I'm almost tired of criticizing so much, but... I think a "code of >> conduct" >> is evil legalese and should be abandoned. >> >> Like Jesus said:

Re: Better specifying the scope of our Code of Conduct

I >> would like to see it "applied to" >> and not only "expect to be honered" for all apache events including >> apacheCON. > > >LF has a code of conduct. It's shorter than ours, and probably more >easily enforceable because it covers a very

Re: Better specifying the scope of our Code of Conduct

On 06/30/2015 12:37 PM, Stefan Reich wrote: I'm almost tired of criticizing so much, but... I think a "code of conduct" is evil legalese and should be abandoned. Like Jesus said: "Love is the only law you need." Unfortunately, that hasn't worked out for us

Re: Better specifying the scope of our Code of Conduct

t to be honered" for all apache events including apacheCON. LF has a code of conduct. It's shorter than ours, and probably more easily enforceable because it covers a very limited time and space, whereas ours covers the known universe and all time. If someone behaves badly at ApacheCo

Re: Better specifying the scope of our Code of Conduct

I'm almost tired of criticizing so much, but... I think a "code of conduct" is evil legalese and should be abandoned. Like Jesus said: "Love is the only law you need." Cheers Stefan On Tue, Jun 30, 2015 at 1:01 PM, Bertrand Delacretaz wrote: > Hi, > > Some

Re: Better specifying the scope of our Code of Conduct

e is managed by > LF... > > It says "A code of conduct which is specific to in-person events (ie., > conferences) is codified in the published ASF anti-harassment policy." > which refers to > http://www.apache.org/foundation/policies/anti-harassment.html > > Doe

Re: Better specifying the scope of our Code of Conduct

Hi, On Tue, Jun 30, 2015 at 1:23 PM, jan i wrote: > ...I read it as apacheCON CORE is not covered and > surely apache big data > (which is a "pure" LF managed event), because the space is managed by LF... It says "A code of conduct which is specific to in-person even

Re: Better specifying the scope of our Code of Conduct

+1 On Tue, Jun 30, 2015, 07:01 Bertrand Delacretaz wrote: > Hi, > > Someone mentioned to me that they find the first paragraph of > http://www.apache.org/foundation/policies/conduct.html overly broad, > and I tend to agree. > > That paragraph says "this code of conduc

Re: Better specifying the scope of our Code of Conduct

On 30 June 2015 at 13:01, Bertrand Delacretaz wrote: > Hi, > > Someone mentioned to me that they find the first paragraph of > http://www.apache.org/foundation/policies/conduct.html overly broad, > and I tend to agree. > > That paragraph says "this code of conduct go

Better specifying the scope of our Code of Conduct

Hi, Someone mentioned to me that they find the first paragraph of http://www.apache.org/foundation/policies/conduct.html overly broad, and I tend to agree. That paragraph says "this code of conduct governs how we behave in any forum and whenever we will be judged by our actions" whi

Re: Code of Conduct - links to why they are needed etc

On 3/26/15 1:46 PM, Noah Slater wrote: > Oh, thanks for the input Shane! > > I don't want to make the punitive measures stuff too complex. It should be > simple and easy to understand for both those who want protection from > harassment and so on, and those who've been spoken to about adjusting th

Re: Code of Conduct - links to why they are needed etc

*or where ever On Thu, 26 Mar 2015 at 18:46 Noah Slater wrote: > Oh, thanks for the input Shane! > > I don't want to make the punitive measures stuff too complex. It should be > simple and easy to understand for both those who want protection from > harassment and so on, and those who've been sp

Re: Code of Conduct - links to why they are needed etc

Oh, thanks for the input Shane! I don't want to make the punitive measures stuff too complex. It should be simple and easy to understand for both those who want protection from harassment and so on, and those who've been spoken to about adjusting their conduct. A strikes system is one idea. So in

Re: Code of Conduct - links to why they are needed etc

On 3/25/15 12:00 PM, Noah Slater wrote: > Yep, thanks for the reply. I'm not sure how to handle the governance side > of this. But I'm sure we can come to an agreement on this list soon. Discussing here makes sense; it's public and there are plenty of helpful voices that are likely to participate;

Re: Code of Conduct - links to why they are needed etc

> >> > > > > https://blogs.apache.org/foundation/entry/asf_ > > > publishes_long_overdue_code > > > > >> > > > > >> For example, > > > > >> Ashe Dryden's introductory resource for learning more about how >

Re: Code of Conduct - links to why they are needed etc

t; > >> 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 >

Re: Code of Conduct - links to why they are needed etc

s 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 &g

Re: Code of Conduct - links to why they are needed etc

Hi this is a whimsical post. (also a top post) But here’s a cute code of conduct video. http://goo.gl/UZF7CW > On 20 Dec 2014, at 15:14, jan i wrote: > > On 20 December 2014 at 20:55, Louis Suárez-Potts wrote: > >> Hi, >>> On 20 Dec 2014, at 09:50, Jim Jagiels

Re: Code of Conduct - links to why they are needed etc

bligatorily > 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

Re: Code of Conduct - links to why they are needed etc

Patches are welcome but please consider the document RTC, with the R happening on this list. Thanks. On Dec 20, 2014 6:34 AM, "sebb" 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

  1   2   >