MegaSquirt and GNU

Bruce nacelp at bright.net
Sat Feb 2 08:59:35 GMT 2002




> ...and lo, thus spake steve ravet on 1/31/02:
> >What are the advantages of this arrangement?

> >* no more bickering.  Theft isn't possible since the design is freely
> >available.  This is the main reason we adopted this policy.

Heavens, we can;t have that, or an author reserving what rights he might
want to claim.

> >* designer is allowed to make money from his design.  There's nothing
> >wrong with supporting your hobby (or your family) by making goods and
> >services available to others.

Which is fine for those then only see the $$ as the end all to life as we
know it

> >* development is encouraged.  People who sell GPL products for profit
> >are motivated to improve them, and those improvements are available to
> >everyone -- even the people who download the free versions without
> >paying a dime.

Who is going to develope something for free when any body can manufacture
it.   Again the perfect way to not hold men responsible for their words or
actions.

> >* slimeballs are discouraged.  Since the design is freely available, the
> >only thing that someone can charge money for is tangible items (boards,
> >parts kits, etc.), and support after the sale.  You can't charge much
> >over cost for tangibles, because anyone else can go buy the parts
> >themselves.  And a slimeball won't be able to support the product, so
> >there's no money available there either.

This is exactly backwards,  the slime balls can now get away with doing what
ever they want, and laugh on the way to the back.

> >This model works, and it works on a large scale -- AMD has donated
> >hardware to the Linux community to make sure they'll support the
> >Sledgehammer chip, Red Hat donates hardware to GNU to help improve the
> >free software that they sell.  Even companies like Compaq and Dell, who
> >most would think are in league with Hell's remote office in Redmond,
> >sell GNU products and provide support and development back to the free
> >community.

Fine, but around here we're hard pressed to get 4 people to sign on to get
somthing done, and then there are 400 people picking apart what does get
done.

> Thank you for clarifying that. It begins to make more sense to me now.
> I think an important thing to note is that with this model, you can
> choose to directly support only the product purchased - those who
> build their own are on their own. Basic support could be given in the
> form of FAQ, discussion board, or whatever, but direct call-them-up
> tech support is part of the purchase package.
> One question - if the product is appropriated by the hypothetical
> slimeball, is he required to note where the original design came
> from? Something like a copyright acknowledgement without the fees?

Read thur the archives and see how things are repeating themselves.  ie,
couple low lives cashing in on the lists work.
As far as projects go things are now dead.
Othen then PGs ion detection devise which hasn't been mentioned in months.
Yep, for the lack of th list's support we're back to bloating the archives
without much new
Bruce

> krw
> --
> Kevin Wright
> krwright at wankel.net
> krwright at ev1.net
> http://www.wankel.net/~krwright
>
> ----- End of forwarded message from owner-diy_efi at diy-efi.org -----
> --------------------------------------------------------------------------
--
> To unsubscribe from diy_efi, send "unsubscribe diy_efi" (without the
quotes)
> in the body of a message (not the subject) to majordomo at lists.diy-efi.org
>

----- End of forwarded message from owner-diy_efi at diy-efi.org -----
----------------------------------------------------------------------------
To unsubscribe from diy_efi, send "unsubscribe diy_efi" (without the quotes)
in the body of a message (not the subject) to majordomo at lists.diy-efi.org




More information about the Diy_efi mailing list