From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id F24361387FD for ; Sun, 30 Mar 2014 11:22:37 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6B193E0ADD; Sun, 30 Mar 2014 11:22:32 +0000 (UTC) Received: from andre.telenet-ops.be (andre.telenet-ops.be [195.130.132.53]) by pigeon.gentoo.org (Postfix) with ESMTP id A846CE0ADB for ; Sun, 30 Mar 2014 11:22:31 +0000 (UTC) Received: from localhost ([94.226.55.127]) by andre.telenet-ops.be with bizsmtp id jnNW1n0072khLEN01nNWRK; Sun, 30 Mar 2014 13:22:30 +0200 Date: Sun, 30 Mar 2014 13:22:03 +0200 From: Tom Wijsman To: gentoo-project@lists.gentoo.org Cc: blueness@gentoo.org Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2014-04-08 Message-ID: <20140330132203.48137283@gentoo.org> In-Reply-To: <5337F95A.2060808@gentoo.org> References: <53342A5F.70903@gentoo.org> <5336D386.6080609@opensource.dyc.edu> <20140329143634.GA31923@laptop.home> <201403300012.55229.dilfridge@gentoo.org> <20140330003709.GA733@laptop.home> <20140330022034.GA1151@laptop.home> <5337F95A.2060808@gentoo.org> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.22; x86_64-pc-linux-gnu) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 86835338-a496-474c-88a4-fbc5ecb78e16 X-Archives-Hash: 4ae9fb10e329f22440cc6408922fd832 On Sun, 30 Mar 2014 07:00:42 -0400 "Anthony G. Basile" wrote: > While implementing a new policy may not be the right approach (or so > I'm hearing from the community), I can bring forward at least 3 > examples of significant changes that were not discussed. I don't > think I would have difficulty convincing people of this fact. If we > do not enact policy then how is this problem addressed? > > As far as "driving people away" I will shift my efforts to > recruiting. I am a professor and can get more students into Gentoo > development. We cannot adopt a de facto situation where devs can > misbehave because they are indispensable. Had a whole conversation with WilliamH about this; my viewpoint after that conversation has changed, it isn't anymore to just go for the policy, but it boils down that there are multiple options to pick from: 1) you fix it on the technical level, by introducing policy; 2) you fix it on the personal level, by improving relations; 3) you do nothing, letting people burn out in personal quibblings. Maybe more options exist, I dunno. Each option then has its advantages and disadvantages, a pick: 1) Advantage: You prevent the concerns altogether. You get useful feedback on what you're planning to commit. Disadvantage: The loudest people can stall progress. People who disagree speak more than people than acknowledge it, even if there is a fifty-fifty situation it's hard to tell how to proceed; that leads to less progress than without discussion. 2) Advantage: Improved communication. Disadvantage: You'll need to be though to get people to improve; as Anthony highlights, people currently are indispensable. The way to fix that is get more people, if you can get more people. 3) Advantage: People learn through burning out to work together; because well, reverting and/or whatsoever yields no progress. Disadvantage: A personal quibbling every week or so. Mood drops. There are other (dis)advantage to these things; but I'm just saying, whatever solution we pick, we must be well aware of the goal as well a the consequence of that solution. And there's no way to pick no solution; because doing so, you'll pick the current (3) by default. That being said, these things come up due to a series of minor events over the last week; they all turn out to not be huge breakage, however ... what if one day someone commits something much worse? We do our best to mitigate the situation in that case; however, I hope that these cases don't become the habit, but rather the exception. So far, we've been doing fine though; but seeing that some things get committed where unintended side effects happen, it is still a worry. -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : TomWij@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D