1 |
On Sat, 2005-11-05 at 00:58 +0000, Ciaran McCreesh wrote: |
2 |
> Feedback from people who have something useful to say would be very much |
3 |
> welcomed, assuming of course that they've read the GLEP. |
4 |
|
5 |
|
6 |
It is written in the GLEP (Requirements): |
7 |
|
8 |
No user monitoring required |
9 |
It has already been demonstrated [#forums-whining]_ that many users |
10 |
do not read news items posted to the Gentoo website, or do not read news |
11 |
items until it is too late. A solution that relies upon active |
12 |
monitoring of a particular source has no advantage over current methods. |
13 |
|
14 |
And later in Specification->Overview: |
15 |
|
16 |
5. Users fetch the news item when they sync. This ensures that the news |
17 |
items in question are pushed to the user before the user accidentally |
18 |
makes an unwanted change. No changes to the existing rsync process are |
19 |
required by this GLEP. |
20 |
|
21 |
My concerns are twofold: |
22 |
|
23 |
The first is the method of delivery: Through 'emerge sync', which |
24 |
requires that users run this on a regular basis to receive relevant |
25 |
news. Further, this process can take a very long time and transfers a |
26 |
relatively large amount of data along with the news. |
27 |
|
28 |
My second concern is the frequency that users sync. A stated concern is |
29 |
getting news to users before it is too late. Is there any way to gauge |
30 |
the number of unique users which sync on a regular basis? When is "too |
31 |
late"? Is there an acceptable window for delivering news? It is not |
32 |
uncommon for me to refrain from running emerge sync (or even cvs up on |
33 |
the entire gentoo-x86 tree) for weeks or months on machines I wish to |
34 |
keep somewhat static. |
35 |
|
36 |
-- |
37 |
Regards, |
38 |
Lisa Seelye |
39 |
GPG: 09CF5 2D6B8 2B72B 997A7 601BC B46B5 561E4 96FC5 |
40 |
http://www.thedoh.com/~lisa/site |