1 |
> A more reliable way of getting news of critical updates out to users is |
2 |
> required to avoid repeats of the various recent upgrade debacles. |
3 |
|
4 |
Examples of the "recent upgrade debacles" aren't needed, but you should at |
5 |
least state some of the outcomes that occurred, whether it be unscheduled |
6 |
downtime, data corruption or whatever. |
7 |
|
8 |
> Preemptive |
9 |
> Users should be told of changes *before* they break the user's system, |
10 |
> after the damage has already been done. |
11 |
|
12 |
s/after/when/ perhaps? This sentence takes a couple of reads... |
13 |
|
14 |
> No user subscription required |
15 |
> It has already been demonstrated [#forums-whining]_ that many users do |
16 |
> not read the ``gentoo-announce`` mailing list or ``RSS`` feeds. |
17 |
|
18 |
Could you use "complaints" instead of "whining" or whatever will represent |
19 |
what the users are doing from an unbiased point of view please? |
20 |
|
21 |
> Quality control |
22 |
> There should be some way to ensure that badly written or irrelevant |
23 |
> messages are not sent out, for example by inexperienced developers, |
24 |
> those whose English language skills are below par or morons. |
25 |
|
26 |
"morons" is not needed either. |
27 |
|
28 |
> The following headers are used for filtering. If none of these headers are |
29 |
> specified, the news item is displayed for all users. Otherwise, the news |
30 |
> item is displayed if *at least one* header matches. |
31 |
|
32 |
It would seem more useful if the headers were sorted into the three classes |
33 |
first. A news item would then only be displayed if a header from the class |
34 |
matches or the class is empty. This would allow for rules such as |
35 |
"net-www/apache is installed and the keyword is either mips or sparc". |
36 |
|
37 |
> ``Display-If-Installed:`` |
38 |
> A dependency atom or simple package name (for example, |
39 |
> ``<dev-lang/php-5_alpha`` or ``net-www/apache``). If the user has the |
40 |
> package specified installed, the news item should be displayed. |
41 |
> |
42 |
> ``Display-If-Keyword:`` |
43 |
> A keyword [#glep-22]_ name, for example ``mips``. If the user is on the |
44 |
> arch in question, the news item should be displayed. |
45 |
> |
46 |
> ``Display-If-Profile:`` |
47 |
> A profile path, for example ``default-linux/sparc/sparc64/server``. If |
48 |
> the user is using the exact profile in question, the news item should be |
49 |
> displayed. This header may be used to replace ``deprecated`` files in |
50 |
> the future. |
51 |
|
52 |
Isn't keyword just a generalization of profile? Why have both? |
53 |
|
54 |
> Thus, all proposed news items must be posted to the ``gentoo-dev`` or |
55 |
> ``gentoo-core`` mailing list, and ``Cc:``\ed to ``pr@g.o`` at least |
56 |
> 72 hours before being committed (exceptions may be made in exceptional |
57 |
> circumstances). Any complaints regarding wording or clarity **must** be |
58 |
> addressed before the news item goes live. |
59 |
|
60 |
Why gentoo-core? It's a news item; it's purpose is to be made public. |
61 |
|
62 |
> Client Side |
63 |
> ''''''''''' |
64 |
> |
65 |
> Whenever relevant unread news items are found, ``emerge`` will copy or |
66 |
> symlink the news file into ``/var/lib/gentoo/news/``. |
67 |
> |
68 |
> Notification that new relevant news items will be displayed via the |
69 |
> ``emerge`` tool in a similar way to the existing "configuration files need |
70 |
> updating" messages: |
71 |
> |
72 |
> :: |
73 |
> |
74 |
> * Important: 3 config files in /etc need updating. |
75 |
> * Type emerge --help config to learn how to update config files. |
76 |
> |
77 |
> * Important: there are 5 unread news items. |
78 |
> * Type emerge --help news to learn how to read news files. |
79 |
> |
80 |
> The unread news message will also be displayed immediately after an |
81 |
> ``emerge sync``. |
82 |
> |
83 |
> Portage may also warn of unread news items using, for example, a red flashy |
84 |
> before actions such as merging a package. |
85 |
> |
86 |
> Portage must keep track of news items which have already been installed to |
87 |
> avoid repeatedly reinstalling a deleted news item. |
88 |
|
89 |
Why put this in portage at all? Post sync hooks will likely be available in |
90 |
2.0.54. If adding hooks were as easy as adding a file to a portage config |
91 |
directory, would adding the package that does the above to the system package |
92 |
set be enough to force this new information dispersal method on users? |
93 |
|
94 |
> Once a news item is 'installed', third party tools (or a traditional Unix |
95 |
> pager and ``rm``) can be used to display and view the news files. An |
96 |
> ``eselect`` [#eselect]_ module shall be created as the 'suggested' display |
97 |
> tool; other display tools (for example, a news to email forwarder, which |
98 |
> would be ideal for users who sync on a cron) are left as options for those |
99 |
> who desire them -- the simple file format make this relatively simple. |
100 |
|
101 |
This is just more reasoning that nothing should be added to portage at all... |
102 |
|
103 |
-- |
104 |
Jason Stubbs |
105 |
|
106 |
-- |
107 |
gentoo-dev@g.o mailing list |