From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 40A9A138330 for ; Fri, 7 Oct 2016 14:43:06 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2D11FE0C2E; Fri, 7 Oct 2016 14:43:05 +0000 (UTC) Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EF4C2E0C2D for ; Fri, 7 Oct 2016 14:43:04 +0000 (UTC) Received: by mail-pa0-f47.google.com with SMTP id ry6so23660799pac.3 for ; Fri, 07 Oct 2016 07:43:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=xrAAyxyOI4DBsNfCMjAiLL8iqQVlyWljQH50vTQ2lW8=; b=i1ZevxOlTz7owMiDXNOViBsJcyhgAIXJyyEaCOOjNgQRY6v3HCaNkkbJHq8kpGN9Qw pkupKTMrQlrTQ0L4LM/kZPBVfwW2tbGkpyUOLfxgoeUvn1dH07IdHb6415YRTfFY0Ugr w2JyXhYaikaI9gJSyZ1LFEwrj8dtYUxDwOSrDB1RonimxlIMB0cr9pzSCUZkZc3XZxk1 vNRJM5oqhujGyw4N9Scfcz589VgXNC55CrkI9ac01b8TzA/uYuEAtrQOwajxK7BHiqn0 +GxTb9TrLxNeiqg5g3mMnVNz0s8LehuLq9laVkM0eSObR4Lic5q7U6GG2HrMhqyoWuu2 ZgcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=xrAAyxyOI4DBsNfCMjAiLL8iqQVlyWljQH50vTQ2lW8=; b=kZUH0dBcEpzYUmrsLJ7fmwUHQz7YTys+OczEkj9rmUeiZB92RGqFa75RKaEfLDXog9 Bz049uTXDddZiQOzMHTvgswiOMQiBQDWhhSv/bx0ZFHWBAvelH+ieZ8oB42e31UviO9C FTdjrVsqyry9hprw1teqP+vgAdmFMjPUYqA3+cHP1pZQbIupfG2DZsLnjHodEHE8lcUx NW6zRZQAQYvnARWU/DEgJqdEbqN/0TKgofpf1w0TSCraELTvjtx+96mv4/x6Gggng5iE NWsSE6LVXZqYHS4HerMXE3fABLMHZ3MaNgj68wA0WK1pJXPH+bESNUUoR/hM3RqGPZm7 oiSg== X-Gm-Message-State: AA6/9Rkj4El3hwupsmXxY4uCnc9wqsdi76xPSl20o0QpqNeVOke19QU7JRACJdTiZcxZuw== X-Received: by 10.66.86.9 with SMTP id l9mr30568449paz.72.1475851383727; Fri, 07 Oct 2016 07:43:03 -0700 (PDT) Received: from ?IPv6:2601:602:9c00:cf41:a15c:1ca:cdf1:57a3? ([2601:602:9c00:cf41:a15c:1ca:cdf1:57a3]) by smtp.googlemail.com with ESMTPSA id d75sm14596699pfl.81.2016.10.07.07.43.01 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Oct 2016 07:43:02 -0700 (PDT) Subject: Re: [gentoo-project] Re: Trying to become a Gentoo Developer again spanning 8 years... To: gentoo-project@lists.gentoo.org References: <832d6b86-ee0e-4509-7f74-1e19fd4e4db9@gentoo.org> <46323553-e9c0-8d52-3c2a-a75b0245c7ce@gentoo.org> From: Nick Vinson Message-ID: <38df2901-f32b-3cdf-1f7a-f630f54a7eb4@gmail.com> Date: Fri, 7 Oct 2016 07:42:57 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gJItN30w0TjhAbTpGH36sEfjHc1pNvXsO" X-Archives-Salt: 31eee6ce-0058-441e-a377-19ff528888fb X-Archives-Hash: 999acc0326f7d6a8a83de65e1e73d3ce This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gJItN30w0TjhAbTpGH36sEfjHc1pNvXsO Content-Type: multipart/mixed; boundary="UAxF0jBIk5as7HqooMAVUbXaE4Ul4OiMv" From: Nick Vinson To: gentoo-project@lists.gentoo.org Message-ID: <38df2901-f32b-3cdf-1f7a-f630f54a7eb4@gmail.com> Subject: Re: [gentoo-project] Re: Trying to become a Gentoo Developer again spanning 8 years... References: <832d6b86-ee0e-4509-7f74-1e19fd4e4db9@gentoo.org> <46323553-e9c0-8d52-3c2a-a75b0245c7ce@gentoo.org> In-Reply-To: --UAxF0jBIk5as7HqooMAVUbXaE4Ul4OiMv Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 10/07/2016 04:58 AM, Rich Freeman wrote: > On Fri, Oct 7, 2016 at 12:57 AM, NP-Hardass wro= te: >> >> Well, what is the purpose of an appeal? >> Presumably, it is twofold: 1) that the procedures that lead up to the >> initial decision were just and appropriate, 2) that the logic that lea= d >> to the initial decision was valid and correct. >> >=20 > It seems far more important to me that the purpose is to confirm > whether the underlying complaint is valid, and whether the action > taken by Comrel was appropriate. If the procedures/logic were flawed > that seems more like a refinement. >=20 > If somebody was harassing somebody else, and Comrel boots them, and it > turns out that they didn't file some information correctly, is it > better to let the booted dev back in and tell Comrel to boot them > again correctly this time? >=20 > When somebody doesn't commit a package properly we tell them not to do > it again, and we make any appropriate fixes. We don't arbitrarily > revert the commit without thinking about the pros and cons of doing > this vs fixing the problem in some other way. Sometimes a reversion > is appropriate solution, but sometimes the right solution is to move > things forward to a better state. Ultimately we need to be concerned > with the user experience. >=20 > In the same way we need to be concerned with the community experience. > Sometimes overturning a comrel decision might be the right move, but > sometimes it might just need a nudge in the right direction, or no > change at all as far as the outcome goes, even if something went wrong > along the way. Doing otherwise just leads to lawyering where we argue > over the process completely ignoring the reason why Comrel is > necessary in the first place. >=20 >> The likelihood of a ComRel member changing their mind at the Council >> appeal stage should be minimal, and their decision is most likely >> against an individual at this point. This means that the votes in an >> appeal are already stacked against an individual if a Council member i= s >> a ComRel member. >=20 > That makes sense. >=20 >> Recusing oneself reduces an initial bias against an >> individual. >=20 > I don't see this as bias, though bias has many definitions. Typically > bias implies some kind of unfairness. A fully-informed decision isn't > bias. >=20 >> >> Hopefully it should be more clear as to why recusal or independence is= >> being promoted as superior to the alternative. It promotes >> imparitality, something you'd hope for in an appeal. "Conflict of >> Interest" probably wasn't the proper terminology to use earlier. >> "Impartiality" is. >> >=20 > Having previously heard a case doesn't mean that somebody isn't > treating all sides of the case equally, which is what partiality is. >=20 > Note that most court systems do not generally strive for independence > between court levels. Usually lower courts are completely subject to > the higher ones. This makes sense when you consider how appeals work. > Imagine if a lower court and a higher court were completely in > disagreement. Anybody who the higher court felt was guilty was set > free by the lower court, and anybody the higher court felt was I'm not following this logic. Are you defining independence as also being equals? The appeals courts don't manage the lower courts in the same way a company manages its employees. And while it may not be universally true in the US, if a lower court decides someone is not guilty (or a jury for that court does), then it's over. The appeals court opinion is moot. ComRel and the council share the same setup. If ComRel chooses not to discipline a dev due to a complaint, then no appeals can be filed. Afterall, the complainant will never know what actions ComRel did or did not take in regards to the complaint unless the accused mentions it. > innocent was declared guilty by the lower court. This would result in > a system where the lower court is a meaningless exercise in process, > because every single decision would be overturned. You want the lower > court to follow the direction of the higher court, so that the > majority of decisions are never appealed in the first place, and most > appeals fail. >=20 > That actually brings up a separate issue with how Comrel operates. > Right now the most common interpretation of the code of conduct says > that the only person who can appeal a Comrel decision is somebody > being punished by Comrel. If dev A complains to Comrel about dev B > doing something wrong, and Comrel decides to take no action against > dev B, dev A has no recourse for appeal. That is a system biased > against action because there are two opportunities to stop action, but This is a good thing. Should you really have to worry so much about what you say in emails, forum posts, IRC channels, so you don't offend anyone and risk them reporting you and then you getting an X duration ban= ? Like it or not, there are going to be conflicting opinions and discussions on those opinions will sometimes get heated and on occasion complaints will be filed because emotions have taken over, but none of that is justification for ComRel to intervene. > only one opportunity to take action. If Comrel simply ignored every > case or dismissed them all, they wouldn't be subject to any oversight > at all under the present system. That's an accountability problem not a bias for action problem. This is a point that has been made several times in this thread already. There needs to be better/more ways to handle accountability concerns when dealing with ComRel. The fact that its inner workings are basically a black box to most on the outside is not a good thing. There's nothing positive of going to someone out-of-the-blue and saying "We received complaints about you, we agreed with the complaints, so here's what your punishment is. Don't like it file an appeal". >=20 > In an ideal world I'd certainly prefer to see more fresh blood in > Comrel, but this is an area we need to be careful about. I'm less > keen on having Comrel entirely elected unless we fix the issue with > not being able to appeal inaction, because this essentially means we > have two different independent bodies steering CoC enforcement in > different directions. If people are upset about the independence of > Council and Trustees then adding more independent governing bodies > that aren't entirely subordinate seems like a step in the wrong > direction. Most organizations try to have just one body ultimately in > charge with delegation down from there. >=20 I don't recall anyone suggesting that comrel become independent of the council. What I have seen and personally suggested was that comrel membership be voted in by the full Gentoo dev community just as the council is. Everything would remain the same. That means ComRel is still overseen by the Council and anyone who doesn't agree with a ComRel decision can appeal. Comrel isn't a normal project, it has the ability to significantly affect Gentoo as a whole. The council has the same ability. I see little wisdom in letting people join ComRel without a vetting from the greater community when when Council members are required to go through such a vetting process. -Nicholas Vinson --UAxF0jBIk5as7HqooMAVUbXaE4Ul4OiMv-- --gJItN30w0TjhAbTpGH36sEfjHc1pNvXsO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJX97RxAAoJEAQpRPZaa5gqcokQAIjyoOGguqb50H6ee2GyAgoa I68or0wV3hYy/Abs4b16igneqr9tlEHZTJmNjcQKBUTMmcltH/hPB7QtFOYhpZsW yemby+Ftup0j1q1AY1pqGt27w3wLvD0hQaU4wE5gTVcavA9hn/Y8feNQwuBbrjQN DdBeMwbAorieu3cYepgdsbk8onRC531qaNwPJZ7CSkpoX4TplyoOM+M34bCfCjLn hC9/+M8I31jvd3P8U5Ofdehd8oCmgqKbK46gZH3YB0zDwLnT/vA/N+WlW70D9O1S Loci8HGQ0Ed6l7IRJm2ggvFV2ehQq8qDH1JkJ4poukzNj5NyvOP4haVlNfMI9WLZ RIhPALefUIyfkBAbZuwt5lUqSEJ5BBb3qbK0cqsdySxExVjd+x5GZUNZUz4SCR/Q hegkSe4ho4MYn5KpKE5N1xdJlp4Nna0FX4KJ6Bi5K6jcl0kPBzb8sFUDnWpgW23c twRbKWIMWlrKFKO7vDeAahMNEEk37Oh0aJ2rGA2w5JmargEYuymSQ/bicvbh9nsc OnJiVzOADkAlKS8D8+rcTxI1fDoCzlCXox+KYTsUdnxPebFOyHUcnBU7S94Xzxyq TCuXwpqewcOfFHq+v/36AjZJmiWnGFGprDKYHrt8V1ZnCST/x1yHUGekpvwf/nQV s9dPtfN6qOQeqEVRO6YP =RCXh -----END PGP SIGNATURE----- --gJItN30w0TjhAbTpGH36sEfjHc1pNvXsO--