1 |
On 8/8/10 9:22 PM, Joshua Saddler wrote: |
2 |
> I already did clean it up when I punted the last of the 2008.0 |
3 |
> references from it, and some other sundry fixes. |
4 |
|
5 |
I appreciate that cleanup, and noticed a recent "last updated" date. |
6 |
|
7 |
However, I think the page can be made even better. My goal is to make |
8 |
downloading Gentoo as straightforward as possible. |
9 |
|
10 |
On 8/8/10 9:22 PM, Joshua Saddler wrote: |
11 |
> By shifting stuff around, you've put all the explanations of "what |
12 |
> all these weirdly named things are" to the end, which means visitors |
13 |
> may be more confused. I'm not sure this was the best idea, but lemme |
14 |
> think about it awhile longer. |
15 |
|
16 |
Let's analyze it. Maybe we can display the links in a different way, but |
17 |
the only info I have moved below the download links seems to be: |
18 |
|
19 |
- releng project page link |
20 |
- information that the isos and stages are generated weekly, and other |
21 |
technical details like that |
22 |
|
23 |
Please note that the Gentoo Handbook link is still there, before the |
24 |
download links. |
25 |
|
26 |
Ideally, I'd like to expose x86 and amd64 (most common desktop arches) |
27 |
even more. People who need different arches know what they are doing, |
28 |
but many users are confused by all this arch thing, but may still be |
29 |
able to install Gentoo by following the instructions precisely. |
30 |
|
31 |
So the idea would be to split the links into two groups: x86 and amd64 |
32 |
at the top, and all the rest below that. |
33 |
|
34 |
On 8/9/10 12:20 AM, Roy Bamford wrote: |
35 |
> I would like to see some explaination of what each arch covers. Many |
36 |
> users get the wrong iso/tarball the first time around. |
37 |
> |
38 |
> e.g. x86 instead of i686 and vice versa, ia64 instead of amd64. |
39 |
> |
40 |
> If this were a table, you could list the CPU families covered by each |
41 |
> group. |
42 |
|
43 |
Roy, I was considering something like this. However, I'm not really sure |
44 |
what to write for arches other than x86 and amd64. And there are a lot |
45 |
of x86 cpu families. |
46 |
|
47 |
Maybe we can do the cleanup incrementally. This change suggestion is |
48 |
focused on moving the download links to the top of the page. A next |
49 |
change suggestion may focus on explaining the arches, and choosing the |
50 |
best place for it (download page vs. the handbook, or maybe handbook has |
51 |
it already covered). |
52 |
|
53 |
On 8/8/10 9:22 PM, Joshua Saddler wrote: |
54 |
> Also, please don't EVER set reply-to to "gentoo-project" when the |
55 |
> topic is actually something related to distribution development, in |
56 |
> this case, the landing page. |
57 |
|
58 |
Now I get some conflicting advice. This is exactly what some other |
59 |
developer has asked me to do (send to gentoo-dev-announce and reply-to |
60 |
gentoo-project instead of sending just to gentoo-project). |
61 |
|
62 |
If you meant that this belongs on gentoo-dev, then what belongs on |
63 |
gentoo-project? My current understanding is like this: code, ebuilds, |
64 |
eclasses, technical stuff - gentoo-dev. project direction, website, |
65 |
non-code policies - gentoo-project. |
66 |
|
67 |
Paweł |