Looks like good information to have on a webpage somewhere that
discusses our policies ;)
-Joan
- Original Message -
From: "Noah Slater"
To: dev@couchdb.apache.org, "Andreas Wenk"
Sent: Wednesday, April 30, 2014 8:56:00 AM
Subject: Re: [DISCUSS] Apache CouchDB Devel
issues raised are addressed promptly and disclosed as soon as feasible.
>>
>> -Joan
>>
>> - Original Message -
>> From: "Bruno Rohée"
>> To: dev@couchdb.apache.org
>> Sent: Tuesday, April 29, 2014 7:42:29 PM
>> Subject: Re: [DISCUSS] Apache Cou
t;
> - Original Message -
> From: "Bruno Rohée"
> To: dev@couchdb.apache.org
> Sent: Tuesday, April 29, 2014 7:42:29 PM
> Subject: Re: [DISCUSS] Apache CouchDB Developer Code of Conduct
>
> Joan Touzet wtrote:
>
> > We will keep our entire bug r
-
From: "Bruno Rohée"
To: dev@couchdb.apache.org
Sent: Tuesday, April 29, 2014 7:42:29 PM
Subject: Re: [DISCUSS] Apache CouchDB Developer Code of Conduct
Joan Touzet wtrote:
> We will keep our entire bug report database open for public view at all
times. Reports that people fil
Joan Touzet wtrote:
> We will keep our entire bug report database open for public view at all
times. Reports that people file online will promptly become visible to
others.
My two cents : there are good, practical reasons to keep some bugs
confidential before a fix/workaround is available. Name
:
>>>> > Can I ask folks who prefer the Django one to the Debian one specially
>>>> > why? Is there something in Django's that's not in Debian's? Is there
>>>> stuff
>>>> > in the Debian one that people don't like explicitlly
>> > For me, I agree the Django one is shorter and better formatted, but it
>>> > seemed to cover less ground than the Debian one.
>>> >
>>> > -Joan
>>> >
>>> > - Original Message -
>>> > From: "Nick North
>> > seemed to cover less ground than the Debian one.
>> >
>> > -Joan
>> >
>> > - Original Message -
>> > From: "Nick North"
>> > To: dev@couchdb.apache.org
>> > Sent: Tuesday, April 29, 2014 9:30:48 AM
>>
is shorter and better formatted, but it
> > seemed to cover less ground than the Debian one.
> >
> > -Joan
> >
> > - Original Message -----
> > From: "Nick North"
> > To: dev@couchdb.apache.org
> > Sent: Tuesday, April 29, 2014
ground than the Debian one.
>
> -Joan
>
> - Original Message -
> From: "Nick North"
> To: dev@couchdb.apache.org
> Sent: Tuesday, April 29, 2014 9:30:48 AM
> Subject: Re: [DISCUSS] Apache CouchDB Developer Code of Conduct
>
> +1 on the CoC idea. I also like the Djang
to cover less ground than the Debian one.
-Joan
- Original Message -
From: "Nick North"
To: dev@couchdb.apache.org
Sent: Tuesday, April 29, 2014 9:30:48 AM
Subject: Re: [DISCUSS] Apache CouchDB Developer Code of Conduct
+1 on the CoC idea. I also like the Django example as a
+1 on the CoC idea. I also like the Django example as a starting point. And
definitely +1 on no profanity - plenty of people are offended by it, and
that in itself should be enough to rule it out. It also adds nothing to the
process of communicating ideas to the community.
Nick
On 29 April 2014
Jason,
My thinking here is modelled on a typical HR policy. There are minor
offences and major offences. Minor ones are met with warnings, and
major ones are met with summary dismissal.
If a PMC member unambiguously, and seriously, acts against the best
interests of the project, then I think it i
On Tue, Apr 29, 2014 at 6:56 PM, Mike Rhodes wrote:
> On 29 April 2014 11:18, Jason Smith wrote:
>
> > Rule: No profanity
> >
> > Secondly, this is only a suspicion, but I think profanity (and also cocky
> > faux hatred), is a shibboleth indicating manhood and that we are in a
> > men-only club.
On 29 April 2014 11:18, Jason Smith wrote:
> Rule: No profanity
>
> Secondly, this is only a suspicion, but I think profanity (and also cocky
> faux hatred), is a shibboleth indicating manhood and that we are in a
> men-only club. It's like a loud fart or belch, or scratching your groin.
> Men ge
On 28 April 2014 21:28, Joan Touzet wrote:
> All,
>
> The PMC would like to move forward towards establishing an Apache CouchDB
> Developer Code of Conduct (CoC for short). To make that happen, we need your
> help.
>
> We do not at this time have a specific text proposal. We'd like to open that
On Tue, Apr 29, 2014 at 2:18 PM, Jason Smith wrote:
>
> Rule: No profanity
>
> Consequence: private email from $somebody asking to stop (i.e. I propose
> that this is the most minor transgression possible, but it's still
> frowned-upon)
Big +1. First ask politely in private what's you're doing wr
Noah, may I propose a rule and consequences not listed in any of the CoCs
so-far:
Rule: No profanity
Consequence: private email from $somebody asking to stop (i.e. I propose
that this is the most minor transgression possible, but it's still
frowned-upon)
Background:
Sorry if this is bike sheddi
TL;DR = Is immediate removal from the project really worth thinking about?
Noah, can you think of an example infraction that could plausibly trigger
an immediate removal from the project, for a first offense? Yes we can all
think of hypothetical examples, but something plausible from this communit
On 29 April 2014 10:54, Benoit Chesneau wrote:
> On Mon, Apr 28, 2014 at 11:02 PM, Dirkjan Ochtman >wrote:
>
> > On Mon, Apr 28, 2014 at 9:28 PM, Joan Touzet wrote:
> > > The PMC would like to move forward towards establishing an Apache
> > CouchDB Developer Code of Conduct (CoC for short). To
On Mon, Apr 28, 2014 at 11:02 PM, Dirkjan Ochtman wrote:
> On Mon, Apr 28, 2014 at 9:28 PM, Joan Touzet wrote:
> > The PMC would like to move forward towards establishing an Apache
> CouchDB Developer Code of Conduct (CoC for short). To make that happen, we
> need your help.
>
> Sounds like a goo
On Mon, Apr 28, 2014 at 9:28 PM, Joan Touzet wrote:
> The PMC would like to move forward towards establishing an Apache CouchDB
> Developer Code of Conduct (CoC for short). To make that happen, we need your
> help.
Sounds like a good idea. Here are the Python and Django versions:
https://www.p
"Noah Slater"
To: dev@couchdb.apache.org
Sent: Monday, April 28, 2014 4:01:52 PM
Subject: Re: [DISCUSS] Apache CouchDB Developer Code of Conduct
A requirement for me for our CoC is that we have a well defined
response procedure. This is a commonly done for conferences, but is
usually
A requirement for me for our CoC is that we have a well defined
response procedure. This is a commonly done for conferences, but is
usually kept private to conference organisers. Obviously, ours will be
public.
To give you an idea of what I'm thinking:
- Minor infractions vs. major infractions
-
Benoit said:
> This one looks really good. What's your plan about the social contract?
> Take something adapted?
In the context of this CoC it only refers to:
"We will not hide problems
We will keep our entire bug report database open for public
view at all times. Reports that people file
On Mon, Apr 28, 2014 at 9:28 PM, Joan Touzet wrote:
> All,
>
> The PMC would like to move forward towards establishing an Apache CouchDB
> Developer Code of Conduct (CoC for short). To make that happen, we need
> your help.
>
> We do not at this time have a specific text proposal. We'd like to o
All,
The PMC would like to move forward towards establishing an Apache CouchDB
Developer Code of Conduct (CoC for short). To make that happen, we need your
help.
We do not at this time have a specific text proposal. We'd like to open that
up to contributions from the developer community. Exam
27 matches
Mail list logo
