1 |
On Mon, 2005-10-31 at 17:32 -0500, Michael Crute wrote: |
2 |
> On 10/31/05, Chris Gianelloni <wolf31o2@g.o> wrote: |
3 |
> > Another thought would be an approach similar to the |
4 |
> installer irc |
5 |
> > channel where you have to read through a really long FAQ |
6 |
> before you |
7 |
> > are told how to download the stage1 or 2 tarballs. |
8 |
> |
9 |
> My personal impression is that this will piss off the end |
10 |
> user. This |
11 |
> works for the installer *channel* but would never work for a |
12 |
> CD |
13 |
> installation. It's simply asinine to ask the user to jump |
14 |
> through hoops |
15 |
> to do what they want. |
16 |
> |
17 |
> Well I wasn't really referring to a CD (but in this case read the MS |
18 |
> license agreement when installing Windoze I think that would be the |
19 |
> equivalent of this :). What I was really referring to was putting up |
20 |
> some sort of scenario like that to download the stage1/2 tarballs. |
21 |
|
22 |
Like I said, alienating users isn't the best idea for future growth. |
23 |
|
24 |
> Even if we stopped shipping stage1 tarballs, there's nothing |
25 |
> stopping |
26 |
> some inventive user from grabbing a stage3 tarball and making |
27 |
> a stage1 |
28 |
> tarball from it using catalyst. It only takes a couple hours |
29 |
> on a |
30 |
> decent machine. |
31 |
> |
32 |
> True but if they fire up catalyst to make a stage1 chances are they |
33 |
> aren't going to be so dumb as to request support when their use flag |
34 |
> combinations don't work. The problem is ignorant users and most of |
35 |
> them can't us catalyst. |
36 |
|
37 |
Exactly. That was my entire point. If they're taking the time and |
38 |
energy to build the stage themselves, perhaps they would understand some |
39 |
of the issues and would be better educated. |
40 |
|
41 |
Consider it a very high barrier of entry on the ability to be able to do |
42 |
something extremely dumb with your system. |
43 |
|
44 |
We don't put reiser4 tools on our CD, either. Why should we put stage1 |
45 |
on there? Personally, I believe a stage1 to be much more dangerous and |
46 |
time-wasting for us developers and our users than reiser4. |
47 |
|
48 |
> My point is that once again, we're not *really* removing |
49 |
> choice even if |
50 |
> we were to drop the earlier stages altogether, we're just |
51 |
> making the |
52 |
> user do the work themselves and removing one more abysmal |
53 |
> headache and |
54 |
> QA nightmare from our already enormous and growing list of |
55 |
> stuff that |
56 |
> has been delaying the past few releases well beyond our |
57 |
> scheduled |
58 |
> release dates. |
59 |
> |
60 |
> Regardless of how foolish you may think it is to do a stage1 install |
61 |
> (and it may well be) I would still greatly appreciate the stage1 |
62 |
> tarballs even if you refuse to support them. Personally I have never |
63 |
> needed support on a stage1 that I couldn't get by simply RTFM. |
64 |
|
65 |
I see no reason whatsoever to release anything that we refuse to |
66 |
support. It doesn't speak much on our professionalism or our quality if |
67 |
we're willing to put out release media that we won't support. |
68 |
|
69 |
I would much rather not release them and deal with the potential flames |
70 |
and blowback from a user community that has been wrongly trained that |
71 |
the stage1 tarball is a good thing than to release something completely |
72 |
unsupported. All that does is raise more user->developer relations |
73 |
problems and widens the gap between users and developers. |
74 |
|
75 |
-- |
76 |
Chris Gianelloni |
77 |
Release Engineering - Strategic Lead |
78 |
x86 Architecture Team |
79 |
Games - Developer |
80 |
Gentoo Linux |