GPL compliance is in fact a very simple matter --- much simpler than

typical proprietary software agreements and EULAs. Usually, the most

difficult hurdle is changing from a proprietary software mindset to one

that seeks to foster a community of sharing and mutual support. Certainly

complying with the GPL from a users' perspective gives substantially fewer

headaches than proprietary license compliance.

For those who go into the business of distributing {\em modified}

versions of GPL'd software, the burden is a bit higher, but not by

much. The glib answer is that by releasing the whole product as Free

Software, it is always easy to comply with the GPL. However,

admittedly to the dismay of FSF, many modern and complex software

systems are built using both proprietary and GPL'd components that are

clearly and legally separate and independent works, merely aggregated

together on the same device.

exchange for this amazing benefit, the license requires that the modifier gives

back to the commons that made the work easier in the first place. It is a

reasonable trade-off and a way to help build a better world while also

making a profit.

Note that FSF does provide services to assist companies who need

assistance in complying with the GPL. You can contact FSF's GPL

Compliance Labs at $<$licensing@fsf.org$>$.

%FIXME-LATER: should have \tutorialpart

If you are particularly interested in matters of GPL compliance, we

recommend the next two parts, which include both recommendations on good

compliance and compliance case studies.

% =====================================================================