On Mon, 2006-01-23 at 08:42, Jeff Spaleta wrote:
> On 1/23/06, Les Mikesell <lesmikesell@xxxxxxxxx> wrote:
> > Interesting comparison. I stopped using slackware as soon
> > as another distro became easier to use.
>
> It is an interesting comparison.. considering that slackware topped
> linuxquestions.org members poll for 2004, which was held in feb of
> 2005. Perhaps the lesson here is that no-one, not even you, have a
> good idea as to what the community as a whole is interest in seeing
> improvement in.
I'd interpret that same data in a somewhat different way. Most
likely that fedora users (myself included) have never heard
of linuxquestions.org... Or perhaps that it really demonstrates
the point that people are not able to make informed decisions
easily with test drive versions.
> Let me be a tad more blunt. Stop making general comparisons about
> "other distros."
I don't get it. How else can you evaluate a distribution
other than comparing it to existing alternatives?
> What you are doing is nothing but grand standing for
> effect.
Yes, but the only way I can make a point is to mention the
obvious counterexample, like the k12ltsp distribution being
able to do a respin when needed - even though it is one guy
and not his real job.
> I demand specifics because I care about this project's
> success.
It's the process that matters, not any specific thing. When
something is broken, don't make users wait for the next release
for the fix, only to find that a different set of things
are broken at that point. The current process lets that
happen. The problem is not any specific thing being broken,
it is the difficulty of obtaining the fix as shown by the
gig or more of updates you currently would have to download
after an FC4 install - assuming your hardware works with
the FC4 installer.
> What i suggest you do, is to take a moment make a list of specific
> examples as to where the implementation in fedora installation process
> could be modified.
The issues have already been covered. Respin the isos after any
installer issue is fixed and whenever some reasonable threshold
of updates have accumulated - like 500M. Make a test drive
version, whether live CD or vmware or both and keep it up
to date so any potential new user or someone who has held off
updating from earlier releases can easily see if the current
version with updates is suitable for any particular use.
When rolling support to legacy, update the yum config so
security updates continue for administrators who are not
tracking the change. The common thread here: make it easier
and more attractive for new people to participate.
--
Les Mikesell
lesmikesell@xxxxxxxxx
