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: Re: [gentoo-project] [RFC] 'Gentoo in 2020', next round
Date: Thu, 14 Jan 2021 09:38:56 +0100	[thread overview]
Message-ID: <9f1e6ae91650b83ad3af6f1d84e9fccf8e335e14.camel@gentoo.org> (raw)
In-Reply-To: <3c2397a7-b273-d1f0-10f5-c1cc367630c9@gentoo.org>

On Thu, 2021-01-14 at 10:26 +0200, Joonas Niilola wrote:
> 
> On 1/14/21 12:45 AM, Andreas K. Hüttel wrote:
> > Hi all, 
> > 
> > taking over on Michal's request, here is latest version of the "2020 in 
> > retrospect" post. 
> > 
> > https://gist.github.com/akhuettel/a5ffcce70f3b3152fc9d654b696bbbe7
> > 
> > The first paragraph (above "Gentoo in numbers") will be the text visible on 
> > the main www.g.o. page.
> > 
> > Let's publish this sometime on the weekend; in the meantime, feedback and more 
> > suggestions for content are welcome.
> > 
> > Please keep in mind that here we want to mainly show off **user-visible** 
> > news.
> > 
> > Cheers, 
> > Andreas
> > 
> ------
> 2020 featured almost 25500 bugs reported, compared to 15000 in 2019. ...
> The total number of bugs closed in 2020 was 23500, compared to 15000 in
> 2019.
> ------
> 
> 15000 created and closed bugs in 2019 seems suspicious. Could that
> number be verified? I see even in 2020 the numbers are very close to
> each other. But just in case.

antarus grabbed these numbers using some magical SQL.  Note that I've
applied rounding to a multiple of 500.

> ------
> packages.gentoo.org The packages website has received a lot of
> improvements towards being a central source of information on Gentoo
> packages. It now shows the results of QA checks, bugs, pull requests
> referencing a package, and a maintainer dashboard indicating
> stabilization candidates and outdated versions (according to Repology).
> ------
> 
> I'd like to add somewhere that these new checks are fully uniquely
> customizable via session (cookies?). For anyone wondering what I'm
> talking about, check
>   https://packages.gentoo.org/user/preferences
>   https://packages.gentoo.org/user/preferences/packages
> 
> 
> Then the last part... discontinued projects. I'd like to end this on a
> happier note. Like moving the whole "Please note that we can describe
> here only a few major items. We would like to thank all Gentoo
> developers for their relentless everyday Gentoo work. While they are
> often not recognized for this work, Gentoo could not exist without
> them." part at the very end, and somehow disconnect it from
> "Discontinued projects" via markdown. Just my opinion.
> 
> 

Yeah, I've indicated that we'd use some summary, and certainly it would
make sense to make that a part of it.


-- 
Best regards,
Michał Górny




  parent reply	other threads:[~2021-01-14  8:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13 22:45 [gentoo-project] [RFC] 'Gentoo in 2020', next round Andreas K. Hüttel
2021-01-14  8:26 ` Joonas Niilola
2021-01-14  8:28   ` Joonas Niilola
2021-01-14  8:38   ` Michał Górny [this message]
2021-01-14 10:13   ` Ulrich Mueller
2021-01-15  0:55   ` Andreas K. Hüttel
2021-01-14 11:52 ` Ulrich Mueller
2021-01-14 11:56   ` Aisha Tammy
2021-01-15  0:58   ` Andreas K. Hüttel
2021-01-15 23:48 ` 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=9f1e6ae91650b83ad3af6f1d84e9fccf8e335e14.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox