From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-project+bounces-9593-garchives=archives.gentoo.org@lists.gentoo.org> 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 4B6D11382C5 for <garchives@archives.gentoo.org>; Sun, 3 Jan 2021 20:36:37 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 881E8E08E8; Sun, 3 Jan 2021 20:36:36 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (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 1ABD2E08E5 for <gentoo-project@lists.gentoo.org>; Sun, 3 Jan 2021 20:36:36 +0000 (UTC) Message-ID: <92fef2b64a4ba03de0b51105ac9a96aed0b66f63.camel@gentoo.org> Subject: Re: [gentoo-project] [RFC] 'Gentoo in 2020' summary From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= <mgorny@gentoo.org> To: gentoo-project@lists.gentoo.org Date: Sun, 03 Jan 2021 21:36:31 +0100 In-Reply-To: <CAAr7Pr84DZgxDSf6HBpFABbJeG=8StPk2N71ThyUVqGAuK7bQg@mail.gmail.com> References: <2ef6e4ea5f0027d64cff71f3d210bfb902c84b4f.camel@gentoo.org> <CAAr7Pr84DZgxDSf6HBpFABbJeG=8StPk2N71ThyUVqGAuK7bQg@mail.gmail.com> Organization: Gentoo Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.2 Precedence: bulk List-Post: <mailto:gentoo-project@lists.gentoo.org> List-Help: <mailto:gentoo-project+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-project+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-project+subscribe@lists.gentoo.org> List-Id: Gentoo Project discussion list <gentoo-project.gentoo.org> 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 Content-Transfer-Encoding: 8bit X-Archives-Salt: 4edd103a-2072-4d95-8ddd-a46db9480666 X-Archives-Hash: b2d4992f8a11e8d7a354b721663f228b On Sun, 2021-01-03 at 12:10 -0800, Alec Warner wrote: > On Sun, Jan 3, 2021 at 12:35 AM Michał Górny <mgorny@gentoo.org> wrote: > > > > Hi, everyone. > > > > I think it would be really great if we could publish a summary of > > (good) things that happened in Gentoo in 2020. We weren't able to > > maintain Gentoo Weekly Newsletter, nor Monthly. However, we might be > > able to manage at least a yearly Newsletter ;-). > > > > I know I'm going to regret this but I volunteer to take care of > > combining and publishing the data. Nevertheless, I'd really appreciate > > if you could reply to this mail with ideas of what you think would be > > worth listing. I'd also use a native English speaker for editorial > > help. > > > > > > Please reply with your ideas in the form of: > > > > [sort-key] **A short sentence summarizing the change.** 1-3 sentences > > of detailed explanation. > > > [infra] Bugzilla DB migration, performance improvements. > We migrated bugzilla to a newer database cluster (mysql galera) and > ported bugzilla from CGI to mod_perl, resulting in a large performance > improvement (sometimes as much as 800ms faster per request.) I think faster Bugzilla actually counts towards a major change ;-). > > [infra] CFEngine migration 90% complete. > Infra remains on an older version of cfengine. We have deleted about > 5000 lines of config with 2 major services to migrate off of. We began > using cfengine in 2002; and started using puppet in 2010. In 2021 we > will > be free of cfengine. > > [infra] Capacity shuffle. > We turned down 3 machines this year (grebe, grouse, brambling) and > have at least 5 machines to replace in 2021 (gannet, godwit, nightjar, > nightheron, noddie) Most infra machines are around 10 years old. We > onboarded some new machines as well (pardalote, petrel, vanga) and > have additional machines coming online in 2021. In 2020 we renewed our > OSS credits with Amazon Web Services and we signed a contract with > Fastly to provide OSS credits that we are using for CDN services to > make our offerings faster for our users. > I think these two would probably be better in 'other changes'. I suppose CDN might also mean improved performance but I don't think we have had noticeably bad performance before. -- Best regards, Michał Górny