Start simple: plan for "flavors", but work them out later, and other comments

I think it's best to start simple, then add things later.
Start with the 2-5 things that people really want, then add
the other things later.   I believe the "short list"
is Open Office and Mozilla... so let's get those on.

I think it's appropriate to start by using each of their
installers; if they're too hard to use, then work to either
(1) make theirs better or (2) create a generic installer,
and then try to convince the other projects to use it.
Otherwise, you'll have a lot of work interfering with
each other.

Flavors are a _great_ idea, but since there isn't even
_one_ CD yet, I think it's time to create one CD now
and add the others later.  I think it _is_ important to agree
that other Flavors will come; that way, people won't be worried
that gcc or the source code aren't on the initial CD... instead,
they'll know that it'll go on a yet-to-be-released CD.
When those other CDs are added, they
need to have simple names, preferably telling you
what's on them.  E.G. "Software Development",
"Games", "Servers", "Education", "Desktop" (or "Office Desktop").
A "source code" CD makes sense, too, to support those who
don't have good bandwidth.

Ideally the infrastructure should be more media-independent, but
CDs are the most universal format right now.  Older machines
won't have DVD readers, and we want users with older machines
to be able to use this.


--- David A. Wheeler



_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [email protected]