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 44F601382C5 for ; Tue, 23 Jun 2020 17:48:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 12790E07F2; Tue, 23 Jun 2020 17:48:11 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E48A0E0636 for ; Tue, 23 Jun 2020 17:48:10 +0000 (UTC) Subject: Re: [gentoo-project] Corporate affiliations of Council members To: gentoo-project@lists.gentoo.org References: From: Patrick Lauer Message-ID: <38ba2c99-d811-8cd7-de2b-ca607f393ba8@gentoo.org> Date: Tue, 23 Jun 2020 19:48:04 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Archives-Salt: 7e298b2f-7166-41c9-a952-e3259c470b8d X-Archives-Hash: f851b061522b5511b047b697e455eccb On 2020-06-22 18:18, Michał Górny wrote: > Hello, > > Here's another question for the Council nominees. I'd like to ask > the Council members to disclose their corporate affiliations, > in particular whether they are employed or in partnership with companies > using Gentoo or Gentoo derivatives. > > This is because I believe that the electorate deserves to know whether > their elected Council member may end up being in conflict of interest > between doing what's right by the wide community and what's requested by > his employer. > As you may or may not know I've been working at Adjust GmbH (www.adjust.com) for the last almost 5 years. Most of my job is babysitting a fleet of around 1000 servers running Gentoo, and ensure things work. I've had a few silly job titles, but I'm basically still Fixer of Things. (We're hiring!) This inherently makes me motivated to have things in a sane state - e.g. packages actually compiling, updates not breaking and other very outdated traditional ideas about software development. (And this is why I'm against things like the current py2 purge: There is code out there that works, can't be rewritten to py3 in a reasonable time*, and hasn't been rewritten in another language yet. There is no fundamental reason to exorcise all things older than 6 weeks, and it just forces me to spend time on useless busywork instead of doing something useful. And it's inconsistent - packages like chromium won't get masked, because ... err... ? But I don't have the time to fight against this madness, so I just move everything useful to an overlay where it is vandalism-safe. Somehow that doesn't sound like a smart strategy to me but what can you do) This doesn't mean I'm a statist, progress can be nice, but these days it's both computationally expensive with some packages taking more than a cpu-day to build, and lots of breakage because very few upstreams to anything resembling software engineering. (e.g. gcc breaking ABI (wtf gcc5), glibc breaking collation (glibc 2.28 which makes updating things exquisitely super fun times), random packages bundling in LLVM, openssl** and whatever else looks cute) tl;dr: I want to be lazy, so stop breaking stuff ;) Have fun, Patrick * "can't be rewritten" - there's some corners of python like manipulating binary data that are not cleanly portable to py3, and the people who would do the rewrite-from-scratch prefer using other languages like Go that don't mutate as fast (since rewriting sucks); as such this legacy py2 code will exist until it is either no longer needed, or the cost of rewriting is smaller than the negligible cost of maintenance. ** yes, a bundled-in security issue. Isn't it great!