About the calculus for the project
About the calculus for the project
Posted Feb 3, 2012 23:33 UTC (Fri) by marcH (subscriber, #57642)In reply to: About the calculus for the project by raven667
Parent article: A tempest in a toybox
> I think that is a mischaracterization of the stated concern, its not that they are being willfully ignorant of their suppliers its that in a large organization it's easy for some team to accidentally distribute pirated software by not doing due diligence on the vendor (or the vendor lying).
I think this is an overly nice way to say the exact same thing.
You MUST carefully select and watch your suppliers, period. Make sure they have a good reputation, tie them in very strict contracts, make sure they are too big too fail (and can pay you any damages back), force them to give you their source code and audit it yourself... this is really just business 101. If the managers of your company cut corners on business 101 in order to be first to market, then I sincerely hope your company dies in copyright litigations (GPL or else) because for sure my company forces us to be thorough and extremely careful, which obviously has a cost, and I would hate you beating us on the market because of that.
[Don't take it personally: it was just easier to give you the role of the bad guy]
> "Hostile Copyright Owner"
Too bad neither Hollywood nor the BSA never cared educating the masses with this new and interesting "HCO" concept.
Anyway I agree with i3839 to some extend. Even assuming that the most HCO owns and defends busybox today and that busybox gets successfully replaced, the most HCO will be someone owning something else in one year time and back to square one.
Posted Feb 4, 2012 14:51 UTC (Sat)
by marcH (subscriber, #57642)
[Link] (4 responses)
"Some say the only two products not covered by product liability today are religion and software. For software that has to end;"
"If a builder builds a house for someone, and does not construct it properly, and the house which he built falls in and kills its owner, then the builder shall be put to death." (Hammurabi's Code, approx. 1700 BC)
Posted Feb 5, 2012 12:35 UTC (Sun)
by alankila (guest, #47141)
[Link] (3 responses)
Then I read the link and observed it advocates liability only for closed source software, where the author of the software must be trusted, and eliminates it for software with source code, where the user could (in theory) become fully informed consumer of the software product.
Posted Feb 6, 2012 9:03 UTC (Mon)
by marcH (subscriber, #57642)
[Link] (2 responses)
"if you make MONEY selling something, you'd better do it properly, or you will be held responsible for the trouble it causes" (emphasis is mine).
It's really more about *business* rather than closed source. If you sell open source then you are accountable (or should be). If you give closed source software for free then you should not. In the latter case you typically do not even know who is using the software and for what.
Posted Feb 6, 2012 11:31 UTC (Mon)
by alankila (guest, #47141)
[Link] (1 responses)
Posted Feb 6, 2012 16:47 UTC (Mon)
by nybble41 (subscriber, #55106)
[Link]
About the calculus for the project
About the calculus for the project
business
business
business