public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed

From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] [RFC] 'Gentoo in 2020' summary
Date: Sun, 03 Jan 2021 09:35:50 +0100	[thread overview]
Message-ID: <2ef6e4ea5f0027d64cff71f3d210bfb902c84b4f.camel@gentoo.org> (raw)

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.

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

next             reply	other threads:[~2021-01-03  8:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03  8:35 Michał Górny [this message]
2021-01-03  9:14 ` [gentoo-project] [RFC] 'Gentoo in 2020' summary Joonas Niilola
2021-01-03 10:06   ` Michał Górny
2021-01-03 17:08   ` Aaron Bauman
2021-01-03 19:44     ` Aisha Tammy
2021-01-03 20:16       ` Michał Górny
2021-01-04  0:54         ` Aisha Tammy
2021-01-03 22:05     ` Aaron Bauman
2021-01-03 22:21       ` Aaron Bauman
2021-01-03 12:55 ` Marek Szuba
2021-01-03 20:21   ` Michał Górny
2021-01-03 21:27     ` Marek Szuba
2021-01-03 19:48 ` Aisha Tammy
2021-01-03 20:34   ` Michał Górny
2021-01-03 23:58     ` Aisha Tammy
2021-01-03 20:10 ` Alec Warner
2021-01-03 20:36   ` Michał Górny
2021-01-04 12:17 ` Andreas K. Huettel
2021-01-04 13:32   ` Andreas K. Huettel
2021-01-05 11:48     ` Michał Górny
2021-01-05 11:12 ` Agostino Sarubbo
2021-01-05 11:46   ` Michał Górny
2021-01-05 12:00 ` Michał Górny
2021-01-05 19:46 ` Poncho
2021-01-05 23:12   ` Michał Górny
2021-01-06 17:41     ` Poncho
2021-01-06 18:05       ` Michał Górny
2021-01-15 11:31 ` Benda Xu
2021-01-16 17:50   ` Andreas K. Hüttel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2ef6e4ea5f0027d64cff71f3d210bfb902c84b4f.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox