public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] bug queue size over time
Date: Wed, 02 May 2018 19:24:48 +0200	[thread overview]
Message-ID: <9909496.vGJQEaZEsL@pinacolada> (raw)
In-Reply-To: <57b5992d-4812-5ee2-7cf7-5224a12464ba@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 895 bytes --]

Am Mittwoch, 2. Mai 2018, 18:42:32 CEST schrieb Paweł Hajdan, Jr.:
> 
> Just checking back here - what would be the best way to graph number of
> bugs with given assignee, preferably with historical backfill?
> 
> I'm not necessarily looking for something ready to use right away. If
> there's some work to be done or code to implement, I may be willing to
> do so.
> 
> Paweł

Hi Pawel, 

some graphs already exist (and I'm doing it the dumb way, ask me about the 
details if interested). E.g., 
https://www.akhuettel.de/gentoo-bugs/arches.php

Feel free to send me any e-mail addresses you want on a similar page; it's 
fairly easy to add. I'm only adding fresh data, though, so if I dont have it 
yet your line will start today.

Cheers, 
Andreas

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, perl, libreoffice, comrel)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  reply	other threads:[~2018-05-02 17:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20  2:33 [gentoo-dev] bug queue size over time Paweł Hajdan, Jr.
2018-03-20  4:24 ` Kent Fredric
2018-03-20  4:33   ` Alec Warner
2018-03-20  5:05     ` Paweł Hajdan, Jr.
2018-03-20 10:13       ` James Le Cuirot
2018-05-02 16:42       ` Paweł Hajdan, Jr.
2018-05-02 17:24         ` Andreas K. Huettel [this message]
2018-05-02 17:45           ` Matt Turner
2018-05-05 10:10             ` Andreas K. Huettel
2018-03-20  5:03 ` Matthew Thode

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=9909496.vGJQEaZEsL@pinacolada \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-dev@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