Philips HMP3000/12 Bedienungsanleitung PDF herunterladen (Seite 42)

this is not our job. “We ask, you answer” is us being lenient, the license technically says

we shouldn’t have had to ask in the rst place, you were supposed to provide this info

when you shipped. And even if we’re letting you delegate the implementation, you

can’t delegate the responsibility. Don’t make me look up how to spell “duciary”. (And

delegating it to nobody really isn’t a solution. Asking us to track down an ex-employee of a

defunct Taiwanese company where nobody spoke English just doesn’t go over well...)

Sorry about that. Scars from the “hall of shame” days. We have lawyers now. They’re

very nice. Where was I?

A company that wants to be legally paranoid will make a source CD for the GPL portions

of their entire product (build scripts, cross compiler toolchains, and all), and either

include the CD in the box with the product (clause 3A) or put the ISO up on the web

and mention the URL to it in their product’s documentation (clause 3B). They don’t need

our say-so to be satised with that, even a strict reading of GPLv2 says that complies with

the license terms. (You can probably even email the SFLC guys about what exactly should

go on the CD, gpl@busybox.net) This is the “make it go away” preemptive nuclear strike

approach, and probably a good idea for Fortune 500 companies that have their own legal

department to do anyway.

A Good Example

These days, Linksys is doing a good job at complying with the GPL, they get to be an

example of how to do things right. Please take a moment and check out what they do

with distributing the rmware for their WRT54G Router. Following their example would

be a ne way to ensure that you have also fullled your licensing obligations.

Add yourself to the Products page

We (BusyBox developers) would be happy to add the information about your product

which uses BusyBox to our Products page. In order to be added there, post a message

to the BusyBox mailing list when the product ships. While at it, the following information

would cover the GPL licensing questions about the product:

A) a description of the product (including the build environment: processor type, libc

version, kernel version).

B) identify the specic version of BusyBox it uses.

C) identify any modications made to that version (either by linking to a nicely broken

up series of “diff -u” patches on the web, or attaching the patches to the message, or

explicitly saying it isn’t modied).

D) attach (or give URL to) the .cong le you used to build the BusyBox binary.

E) A link to your website.

This is the “being nice to the developers” approach, which acts as a sort of free

advertising within the developer community.

You really can’t go wrong with either approach: you can obey the letter of the license

according to a strict reading, or you can make the developers as happy as possible so they

not only have no reason to make trouble, but actually like you. (Heck, we won’t complain

if you do both. :)

1 2 ... 37 38 39 40 41 42 43 44 45 46 47 ... 69 70

Keine Kommentare

Philips HMP3000/12 Bedienungsanleitung Seite 42