From: Peter Stuge <peter@stuge.se>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: app-text/cuneiform
Date: Sun, 24 Mar 2013 16:19:16 +0100 [thread overview]
Message-ID: <20130324151916.23155.qmail@stuge.se> (raw)
In-Reply-To: <514F13BD.7050403@gentoo.org>
Markos Chandras wrote:
> > A per-ebuild bug metric would be cool. A kind of health indicator
> > for individual ebuilds, alerting users when some of our installed
> > ebuilds go yellow, so that we have perhaps on the order of six
> > months before the package goes red, at which point it would be
> > fine to mask at will. Does that make sense? (Obviously how many
> > months yellow is depends on what else happens in the tree. It's a
> > ballpark figure.)
>
> No we don't have the human resources to do that.
Ah, no, it must be automated. Of course the metric would be
accordingly "stupid" but it would still be way more informative
than no metric at all.
I think a GSOC project is a good fit, unless of course a developer
likes to run with the idea. In any case, yes, people are needed to
do development, but working out an idea is a good start.
//Peter
next prev parent reply other threads:[~2013-03-24 15:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 23:03 [gentoo-dev] Last rites: app-text/cuneiform Markos Chandras
2013-03-23 19:52 ` James Cloos
2013-03-23 20:06 ` Markos Chandras
2013-03-23 20:13 ` James Cloos
2013-03-23 20:21 ` Markos Chandras
2013-03-23 20:29 ` Rich Freeman
2013-03-23 21:40 ` James Cloos
2013-03-24 9:45 ` Rich Freeman
2013-03-24 13:02 ` Sergei Trofimovich
2013-03-23 21:33 ` Alec Warner
2013-03-24 13:24 ` Peter Stuge
2013-03-24 13:38 ` Rich Freeman
2013-03-24 13:52 ` Peter Stuge
2013-03-24 14:12 ` Rich Freeman
2013-03-24 14:35 ` Peter Stuge
2013-03-24 14:54 ` Markos Chandras
2013-03-24 15:19 ` Peter Stuge [this message]
2013-03-24 19:24 ` Ian Stakenvicius
2013-03-24 23:40 ` Rich Freeman
2013-03-25 7:05 ` Róbert Čerňanský
2013-03-25 7:46 ` Alec Warner
2013-03-24 9:15 ` Róbert Čerňanský
2013-03-24 10:43 ` Markos Chandras
2013-03-24 11:22 ` Rich Freeman
2013-03-24 12:11 ` Markos Chandras
2013-03-24 12:18 ` Rich Freeman
2013-03-24 12:31 ` Markos Chandras
2013-03-24 12:40 ` Rich Freeman
2013-03-24 14:48 ` Markos Chandras
2013-03-25 10:22 ` Ben de Groot
2013-03-24 19:00 ` Róbert Čerňanský
2013-03-24 13:40 ` Peter Stuge
2013-03-24 13:48 ` Rich Freeman
2013-03-24 14:14 ` Alan McKinnon
2013-03-24 14:51 ` Peter Stuge
2013-03-25 0:23 ` Patrick Lauer
2013-03-25 0:26 ` Rich Freeman
2013-03-25 3:17 ` [gentoo-dev] " Duncan
2013-03-25 7:08 ` [gentoo-dev] " Róbert Čerňanský
2013-03-25 6:25 ` Sergey Popov
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=20130324151916.23155.qmail@stuge.se \
--to=peter@stuge.se \
--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