On Tue, Aug 13, 2002 at 09:27:25AM +1000, Tony Nixon wrote:
> Just curious, once the hardware is finally decided upon, who is going to
> do the much larger part of the job like write all the software, tutorial
> notes, create images, wiring diagrams, PCB designs, build prototypes,
> debug, decide on what beginners projects to use, develop them all as
> full projects, combine it all into a neat package, add printed matter,
> and then keep offering time, and gobs of it, to modify and/or add bits
> and pieces for customers who will ultimately want something changed.

Why you are! ;-) ;-) ;-) ;-)

>
> I know there's plenty of material available, but it may not be
> compatable with the final system.

It won't be. It'll have to be ported.

>
> >From my experience, this takes many many unpaid hours.
>
> While this may have been enjoyable for me, it might not be workable for
> someone who wants to make a little something from it all in the end.

It can't be an individual doing all of the work. I'm figuring it'll have
to be something akin to Linux kernel development, where there's simply too
much for even a small group to handle. We're going to need a lot of folks,
and there's going to have to be some type of editorial board that manages
the overall content. In the end I'm sure we'll end up having to limit the
amount of work that needs to be done.

You've already helped tremendously Tony simply by providing a framework
under which we can work. I figure that each project will need a three person
team: a developer, a writer, and an editor. We'll simply have to limit
the amount of work each individual can be assigned, and delineate our projects
based on the amount of available people power.

One service I believe that we'll have to offer to our customers are cheap
(if not free) CD updates.

I don't think we have to do everything at once to get off the ground. If we try
we'll be grounded before we ever get started.

BAJ.

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu