Re: [gentoo-project] [RFC] 'Gentoo in 2020' summary

[Alec Warner]

On Sun, Jan 3, 2021 at 12:35 AM Michał Górny <mgorny@g.o> 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.)

[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.

-A

>
> I think we'll publish this on the website, so please use Markdown
> and possibly link to the relevant projects.  The idea is that the users
> can skim through the changes in bold, and decide whether they want to
> read on.
>
>
> Example:
>
>   [dist-kernel] **The [Distribution Kernel](https://...) project was
> launched to install kernels directly from ebuilds.**  To lower
> the entry barrier and maintenance effort, the project also provides
> a stock configuration for popular architectures based on Fedora.
>
>
> I think we'll then split it into a few groups.  I'm thinking of:
>
> 1. New developers (yay!).
> 2. Major changes (focused on things impacting end users).
> 3. Other changes.
>
>
> WDYT?
>
> --
> Best regards,
> Michał Górny
>
>
>