1 |
On Thu, 2005-11-10 at 21:33 +0000, Stuart Herbert wrote: |
2 |
> My personal conclusion was that there is only one place where we can |
3 |
> have any degree of certainty that we have the attention of 100% of the |
4 |
> userbase - or as near as damn it. I believe that place is right beneath |
5 |
> the message that tells the user they have CONFIG_PROTECTED files that |
6 |
> need updating. |
7 |
|
8 |
I agree that portage should have some way of showing the number of news |
9 |
items. |
10 |
|
11 |
> Hence emerge --news. |
12 |
|
13 |
Why? |
14 |
|
15 |
There's no "emerge --etc" or "emerge --etc-update" functionality. Why |
16 |
must it be "emerge --news" at all? |
17 |
|
18 |
I think this would completely remove the "portage as a news reader" |
19 |
problem entirely. Portage would check a directory for news items. The |
20 |
news reader would take care of them after this. Portage would do |
21 |
nothing more than look at the directory for unread news items and |
22 |
display that number. |
23 |
|
24 |
> If you have found *one* place where we are even more likely to have the |
25 |
> attention of 100% of the userbase, please share it with us. If there's |
26 |
> a better place, we should use that instead, and I will very happily |
27 |
> support it. |
28 |
|
29 |
I agree that we should have news delivered by emerge --sync. I also |
30 |
think that we should increase the placement of important information on |
31 |
our site, gentoo-announce, and the forums. It is my personal opinion |
32 |
that we should put the news out on as many mediums as possible. |
33 |
|
34 |
> If we can put something together that takes the news available through |
35 |
> emerge --news, and pushes it out via other places (web, mailing lists, |
36 |
> whatever), I have no real problem with that. |
37 |
|
38 |
I think this should be a requirement. |
39 |
|
40 |
> But I think that there is a very good reason why it needs to come later, |
41 |
> why now is *not* the time. |
42 |
|
43 |
Ehh... |
44 |
|
45 |
> We need to establish *one* authoritative source of news. We can't do |
46 |
> that if we simultaneously launch several sources of news all at once. |
47 |
> We have to launch *one* service first, give the userbase time to adjust |
48 |
> to that, and then start making the news available via additional |
49 |
> sources. |
50 |
|
51 |
No, we really don't. Our users aren't idiots. They just aren't reading |
52 |
the information presented to them. While I agree that we need to have a |
53 |
single location for news, I also think that we must *require* this |
54 |
information be present in other locations. The main reason for this is |
55 |
that "emerge --news" is filtered based on the packages installed on the |
56 |
system. What about administrators that have lots of different systems? |
57 |
To them, it might be easier to receive all of the news, via |
58 |
gentoo-announce, and filter them via their own methods to determine what |
59 |
is important to them. Perhaps I want to search for an old news item. |
60 |
Why shouldn't I be able to go to a web site and enter my query in a |
61 |
search box and get all of the major news updates to dev-lang/php? |
62 |
|
63 |
If you want to reach 100% of the user base, then we should make this |
64 |
useful for as many situations as possible. I know that with the number |
65 |
of machines that I administer, it would be much easier for me to get |
66 |
*all* of the news in one place and determine what is valid for my |
67 |
machines, rather than having to read them on each individual machine |
68 |
based on the packages installed. |
69 |
|
70 |
> > Don't worry I'll shut up now as there is clearly no interest for a bit |
71 |
> > broader thinking. |
72 |
> |
73 |
> I find your thinking anything but broad on this topic. |
74 |
|
75 |
*cough* |
76 |
|
77 |
Pot. This is kettle. |
78 |
|
79 |
*grin* |
80 |
|
81 |
-- |
82 |
Chris Gianelloni |
83 |
Release Engineering - Strategic Lead |
84 |
x86 Architecture Team |
85 |
Games - Developer |
86 |
Gentoo Linux |