public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: R Hill <dirtyepic.sk@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: GLEP 42 (Was: Getting Important Updates To Users)
Date: Sun, 06 Nov 2005 13:32:05 -0600	[thread overview]
Message-ID: <dkllnm$hi5$1@sea.gmane.org> (raw)
In-Reply-To: <200511051408.09014.jstubbs@gentoo.org>

Jason Stubbs wrote:

> I seem to be repeating myself... What's an example of repository-specific 
> non-package-specific news? Why does `emerge --changelog` not suffice for 
> package-specific news?

a) maintainers don't put important news in their changelogs.

there are a few exceptions.  gregkh's udev bumps, for example, always 
come with an explanation of what changes have been made and what to 
watch out for.  but mostly all the info you're going to get is "Version 
bump.", if that.

b) there's no way to separate the wheat from the chaff.

while i could (and usually do) emerge every update with -l, it's not 
something anyone with a life would do.  the signal to noise ratio is 
very low, and not many people are going to go through reading the 
changelogs for every package on the odd chance that there might be some 
important nugget of info they need to know.  combine this with a) and 
you'd have better luck playing the lottery than getting pertinent 
information that specifically applies to you.

c) it's a passive system

the user has to actually make an effort to retrieve this news.  we 
_already_ have a number of different sources that they could be getting 
important info from.  another is not what's needed.  what we're looking 
for is a proactive solution where the news is dropped at their feet 
below a bigass neon arrow saying READ ME.

d) news isn't necessarily package-based.

news items could be based on a user's profile, language preference, 
architecture, USE flags, etc.  there could also be general news to the 
entire community about global changes in Gentoo.


--de.

-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2005-11-06 19:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 23:36 [gentoo-dev] GLEP 42 (Was: Getting Important Updates To Users) Chris White
2005-10-31 23:41 ` [gentoo-dev] " Dan Meltzer
2005-10-31 23:52   ` Dan Meltzer
2005-11-01  7:56     ` Wernfried Haas
2005-11-01 14:32       ` Chris Gianelloni
2005-11-01 19:32       ` Stuart Herbert
2005-11-01 19:51         ` Chris Gianelloni
2005-11-03 19:40           ` Stuart Herbert
2005-11-04  1:10             ` Nathan L. Adams
2005-11-04  8:22               ` Sami Näätänen
2005-11-04 14:26               ` Xavier Neys
2005-11-04 16:44                 ` Jason Stubbs
2005-11-04 18:53                   ` Alec Joseph Warner
2005-11-05  5:08                     ` Jason Stubbs
2005-11-05  5:34                       ` Alec Warner
2005-11-07 10:11                         ` Paul de Vrieze
2005-11-07 12:37                           ` Jason Stubbs
2005-11-07 16:06                             ` Grant Goodyear
2005-11-07 16:44                               ` Jason Stubbs
2005-11-07 16:43                             ` Stuart Herbert
2005-11-05  9:58                       ` [gentoo-dev] " Duncan
2005-11-05 12:54                       ` [gentoo-dev] " Michiel de Bruijne
2005-11-06 19:32                       ` R Hill [this message]
2005-11-01 19:53         ` Mike Williams
2005-10-31 23:46 ` [gentoo-dev] " Brian Harring
2005-11-01 10:51   ` Jason Stubbs
2005-11-01  0:42 ` Ciaran McCreesh

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='dkllnm$hi5$1@sea.gmane.org' \
    --to=dirtyepic.sk@gmail.com \
    --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