X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail-qk0-f175.google.com (mail-qk0-f175.google.com [209.85.220.175]) by lists.alpinelinux.org (Postfix) with ESMTP id 11D375C4A98 for ; Mon, 15 May 2017 06:16:15 +0000 (GMT) Received: by mail-qk0-f175.google.com with SMTP id k74so85956404qke.1 for ; Sun, 14 May 2017 23:16:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dereferenced-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DSyHKMwqQq4hrjja173NL9WqHOpgOtB/lfE3aixtCpc=; b=Mj7I3MephHpriTuS64dNtoWSysJHT5B35Dc9rq616bHV0npPxpd1sD/VMeWigz6ZeI rp02DCwuw76/oxSU5kAvn3JbB2R8ASKO87435DWGw6j6qBf1recR6x5Jv3sHxDEqakc2 1vGalnXeEU4vVpODjZBEN6GCnluH17lemCQZT+9EOjYG60WoDPyC6IrFE9EEaRJmR47v sf4TzmzNrX5nVit3XWaRXDPiWCkK5Hi21QuRpX+mLzghmoHfyTO2jkornfWffVbohI8e 5M65Ah90QVpyg9nKSImDz/T1TPyjor7d9YPPyhlD9VlscYB3GUsUJYjmj42j43HFrp2u mnGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DSyHKMwqQq4hrjja173NL9WqHOpgOtB/lfE3aixtCpc=; b=t2FXpPb6zh+iLD5N4DUtbRfnFuEU8hb/93QWU/jgCLpJp727C3KflX04LVvWcPTu9/ bcm/5kDSFKbuwxRd4zVYIvkKLAEZjhdFYJPEDi/pRZic8dtV9WvZQ5o3cNUcmE998s9w D37wETQBpzB5neI+SwIkYaCA9tDGCVsejnKlwCEbKklWvPaB56vGkahi/s8UW/M/6ypT TST//32i43H+zQ42xWKTSTzNptXtOIeCx6HaW9ZwpcXUD9cYvQ/Z0PC7NuFYVC8rEuyN ifnPPFMWBga2VvOAUyeYTZ3yZTZizSI+Z+YnjFivKygitccr0XvxC1Bl39V9C86QsZ0J J+zw== X-Gm-Message-State: AODbwcAGxfavNUDo7uNl7vtwYW1RL9o3kH6i29JMJHOMivHgcARjJrmy PKa4HPUiAeSKMzYACEORudqkjnAKBg== X-Received: by 10.55.217.155 with SMTP id q27mr4204485qkl.217.1494828975209; Sun, 14 May 2017 23:16:15 -0700 (PDT) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 10.237.62.120 with HTTP; Sun, 14 May 2017 23:16:14 -0700 (PDT) In-Reply-To: <76bddf47-8f79-ab8b-1624-d51c4a7dfa65@mail.com> References: <412A395A-202C-490A-B113-C5580CCD4AE4@shiz.me> <7e304eda-7ffc-6bd0-87ec-76c12f0f2e3b@mail.com> <9f90daa2-b74a-2c1d-0411-ba095d842f99@mail.com> <76bddf47-8f79-ab8b-1624-d51c4a7dfa65@mail.com> From: William Pitcock Date: Mon, 15 May 2017 01:16:14 -0500 Message-ID: Subject: Re: [alpine-devel] Code of Conduct To: 7heo <7heo@mail.com> Cc: alpine-dev Content-Type: text/plain; charset="UTF-8" Hi, On Sat, May 13, 2017 at 12:18 PM, 7heo <7heo@mail.com> wrote: > Breno Leitao makes a good point about the language barrier; and I will be > thinking of a way to re-add the "good faith" point without giving too much > space for it to be a loophole. Some sort of "do not assume you are being attacked personally because your work is being criticized" is important for me to support the CoC. People who are behaving defensively can become very toxic. >> On 5/12/2017 1:50 PM, Laurent Bercot wrote: >>> >>> It is exactly because we are not exposed to challenges that we may fail >>> to perceive them. I have experienced this first-hand. Pretending to be >>> able to foresee everything is just hubris; if we are going to have a CoC >>> ready for when the community has grown and needs one, I'd rather have it >>> done right. A CoC is not enough to improve the diversity situation, but is a good start. We should consider a diversity statement, and perhaps a diversity subproject to encourage minorities to make Alpine their home base instead of other distributions. It is also important to me, personally, that the CoC does not try to make special nods to minorities: when CoCs do this, it comes off as "white men" paying lip service -- it's not authentic. >>>> We are all Humans, and the paragraph two is meant as a catch-all for >>>> abuses towards Humans (if I remember correctly, awilfox was supporting >>>> it, saying something along the lines of "no personal attacks, and >>>> you're good"), no matter their individual characteristics. >>> >>> >>> Sure, and that's fine with me, too. But is there any harm in running >>> it by >>> people who may have a different perspective, just to be sure? I have a different perspective being that I'm not "white" (what is really meant by "white" is Caucasian). My family has some immigrants (and really I do cherish that heritage too) in it, but is largely native. >From my perspective: there are *perceived* biases that may or may not actually be present. A lot of us are taught to just pretend we're white, as it's "easier that way." In fact, in America, a lot of tribal citizenship rolls are having to be reconstructed because their ancestors gave up tribal citizenship in order to appear more "white." A Code of Conduct alone cannot solve that, if the goal is to encourage minorities to be comfortable participating in Alpine, they need to feel like they will not be "found out." I do not pretend to know the solution, I just know that we need more than a Code of Conduct, nor should we attempt to fool ourselves into believing that a CoC would be an effective vehicle for that kind of outreach. Imposter syndrome is quite real and can cause *extra* attrition in contributions from minorities, and some sort of other solution would be needed to help resolve that. In fact, writing the above was very difficult for me because I was worried about being "found out" and how those facts would be perceived. Thankfully, until now, it has not really come up, as FOSS is really about code first and discourse second. >>>> Making it more explicit, and detailing each case is a role a refuse to >>>> take, as it will exponentially increase the pain of discussing and >>>> redacting the CoC; >>> >>> >>> That's not what I suggested. >>> I know you thought people would make that suggestion and so you felt >>> compelled to address it, but as it turns out, I didn't. Please react to >>> what I wrote, not to what you think I would write. And for the record, >>> I agree with you on that point. As I said above: I don't think it needs to be *explicit*. The point that should be communicated is that it is the intent of the Alpine project to provide a safe collaborative space for *everyone* (including "white" males). With that said, I think a secondary document alongside the CoC which lists some common hypothetical situations (swatting / doxing, harassment inside and outside of the space originating from some statement / action in Alpine) is necessary to help interpret the spirit of the CoC. For example: if I say I want to switch Alpine to GLIBC and systemd and somebody else swats me or harasses my boss trying to get me fired, this should not be allowed behaviour. Swatting and harrassing my boss are both technically activities which occur outside of the Alpine collaborative space, but the actions stem from something that did occur in that space. If the CoC has no guidance to address this, then it is a worthless CoC. Oh, and this (swatting) has actually happened to me before working in other spaces, so please do not tell me this is unnecessary. >>>> In short I'm not against asking around, but please be careful who you >>>> ask: if this becomes the kind of long and complicated debate >>>> attracting mobs of lobbyists from any side >>> >>> >>> That is *also* not what I wrote. As a matter of fact, since it's >>> something >>> that really does endanger open source projects and often flies under the >>> radar, I am in favor of adding a mention to paragraph 4 that would say >>> something like: excessive lobbying or engaging the Alpine community on >>> non-technical matters *is* a disruption of the collaborative space and a >>> violation of the CoC. (In other words: make it clear that >>> politics, drama or any other kind of noise => out.) I agree with this. >>>> Let's make our CoC as we like our software. Simple, reliable, and small. >>> >>> >>> Yes. And to me, reliability includes checks from people with more >>> experience than we have in these matters. I also agree with this. Hopefully my perspective is insightful. William --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---