Copyleft/guide
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Wordsmith.

Browse source
This commit is contained in:
Bradley M. Kuhn 2014-03-20 21:32:21 -04:00 • committed by donaldr3
parent 5c677924bc
commit 9ef0ff8602
1 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
compliance-guide.tex
View file

@ -270,10 +270,12 @@ source that corresponds to any deployed binary.
Too many software projects rely on only one or a very few team members who Too many software projects rely on only one or a very few team members who
know how to build and assemble the final released product. Such knowledge know how to build and assemble the final released product. Such knowledge
centralization not only creates engineering redundancy issues, but it also centralization not only creates engineering redundancy issues, but also
endangers GPL compliance, which requires you to provide build scripts. thwarts GPL compliance. Specifically, CCS does not just require source code,
but scripts and other material that explain how to control compilation and
installation of the executable and object code.
Avoid relying on a ``build guru'', a single developer who is the only one Thus, avoid relying on a ``build guru'', a single developer who is the only one
who knows how to produce your final product. Make sure the build process who knows how to produce your final product. Make sure the build process
is well defined. Train every developer on the build process for the final is well defined. Train every developer on the build process for the final
binary distribution, including (in the case of embedded software) binary distribution, including (in the case of embedded software)