[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [N8VEM-S100:319] S-100 community project
- To: <n8vem...@googlegroups.com>
- Subject: RE: [N8VEM-S100:319] S-100 community project
- From: "Andrew Lynch" <lyn...@yahoo.com>
- Date: Mon, 20 Jun 2011 21:32:32 -0400
- Authentication-results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of lyn...@yahoo.com designates 220.127.116.11 as permitted sender) smtp.mail=lyn...@yahoo.com; dkim=pass (test mode) head...@yahoo.com
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1308619958; bh=EvV7ZMqx1YmzGn67+CTWxHiQH4Vbrgw76LLG2OEqwQ0=; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:From:To:References:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-MimeOLE:Thread-Index:In-Reply-To; b=hRKprO2LnYhDYKvOBu/x5xxDvC/rBepb9mojeOYOWs75q7L/ud3b16VQBUXxO+9dqAlwZdiy6ebkkA5gcx0i/C06o1bc6voXcW7fy2mpa2xSznMhLXztEuEVmTPE6G4Yphd8LuKZ7nBLUpbku9s9X0trCBW5LUxkOpb1NTY8ktA=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=DKIM-Signature:Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:From:To:References:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-MimeOLE:Thread-Index:In-Reply-To; b=Y+C9Bxkzd+5Y74ny81C0PCHuvemcJ8b4JUXlsYquoGmNV6VJ2etv5WQiv39i8QHXp+Sqx2QiUhGs0RS3DfaqFdN73IYqXYvmF6XZpMIAp7EE6IbXvtUVYtcEyg/bKQHlyn4ZO95ffl6dxfPIsmey49ZUVJCDn+X0SgLW4lYQcR4= ;
- In-reply-to: <4DFE592A.firstname.lastname@example.org>
- References: <C8DC29B8D1904DE68DA3E5676E4B3288@andrewdesktop> <4DFE592A.email@example.com>
- Thread-index: AcwuuydMF4EJlFfoTZiXD4fBNoYLyQA6OGMQ
> -----Original Message-----
> From: n8vem...@googlegroups.com [mailto:n8vem...@googlegroups.com] On
> Behalf Of mike
> Sent: Sunday, June 19, 2011 4:17 PM
> To: n8vem...@googlegroups.com
> Subject: Re: [N8VEM-S100:319] S-100 community project
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 11-06-19 01:03 PM, Andrew Lynch wrote:
> > Since John is already fully busy with S-100 8086 CPU board and other
> > projects, I'd like to attempt a new development approach. Since Mike
> > already has a design including a schematic, PCB layout, parts list, etc,
> > could do a community build and test. Basically this would be we take
> > existing design, gather up some funds, get some prototype boards, and
> > them out for initial build and test.
> Hi All,
> I like the community-build concept, it sort of forces those interested
> to belly up to the bar right up front.
> Andrew, I think the details may need a little clearing up though. For
> example, the gathering of the funds. How should that be done? Perhaps,
> should those interested parties, pledge a commitment, and after enough
> pledges are tallied to make it feasable to proceed, we go ahead and
> collect the pledges, or collect on delivery...anyway, something like that?
> After the project funding is sorted out, then who handles the logistics,
> currently, Andrew, you seem to be handling the bulk of that, would that
> continue to be that way in the "community build" model?
> If Andrew, you where to handle the logistics, then I would suppose you
> probably would not care to be burdened with PCB work and so on, but
> simply the collecting of funds, the ordering, and the distribution? If
> this is the case, then boards being submitted for "community build"
> would need to be provided to you with finished artwork with Gerbers and
> Drill files attached, correct?
> Sorry for very basic questions, I guess I'm just trying to clarify the
> details somewhat so we can all be on the same page with this. I guess
> the core of what I'm driving at is that even in the "community build"
> model, you still need some sort of centralized point to handle the
> I dunno, thoughts, comments?
> Mike Sharkey
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
Hi Mike! Thanks! Yes, something like that. The model we use mostly now is
I'll do schematic capture, PCB layout, parts list, PCB trace routing, etc.
Then send the board out for builder review, comments, feedback, etc.
Normally there are a few cycles of changes, fixes, etc. We get enough
builders to buy a prototype board $150/5 = $30 each or whatever
arrangements. Then I order the prototype boards and send them out to the
build and test team.
Sometimes builders buy prototype boards to get the project moving and I send
the board to a different builder to assemble. That allows builders
interested in a particular project to "sponsor" it and allow different
builders who have time but without the money to participate. Splitting the
board design work from the board build and test is a natural division of
labor. It doesn't have to be that way but spreads the load a bit so a given
builder is not a bottleneck on throughput. It is a bit of an ad hoc "stone
soup" approach and more or less works -- sometimes spectacularly (XT-IDE)
and sometimes badly (ISA OPL2 FM Synth)
Actually, I've noticed some board design companies work this way as well
although it just sort of coincidentally is that way on N8VEM. I've more or
less migrated to the schematic capture & PCB layout & prototype board
acquisition niche. Every project is different though so in this case you've
already done the schematic capture and PCB layout so all I would need to do
is get some prototype boards and distribute to the build and test team.
Usually people just send me a PayPal for a prototype board for themselves to
build and test or to give to another builder to do it. Either way works for
me and I would like to keep it simple. The key is to not collect funds
until there is something tangible to deliver though. Accepting pre-payments
is fraught with risk and is the path to the dark side.
I volunteer to do work as needed but we'll need some funds for prototype
boards ($150) and 4 or 5 volunteers for the build and test team.
I hope this helps! Thanks and have a nice day!