Flowchart #0: General Approval Flowchart. With thanks to Royal Philips Electronics
### Handling obligations around distributing code The bulk of the work you do with the GPL ends up popping up around when/how you distribute code. Different mediums of patching, updating, and shipping software fundamentally affect what the GPL requires you to do: Flowchart #1: How Do I Distribute?
###Flowchart #2: Device or offline distribution** Flowchart #2: Offline Distribution
###Flowchart #3: Updating firmware** Flowchart #3: Firmware Updates
###Flowchart #4: Over-the-air updates** Flowchart #4: Over The Air
Naturally, not all code is [GPL v2](https://fossa.com/blog/open-source-software-licenses-101-gpl-v2.md). Sometimes you are dealing with Library or Lessor GPL (LGPL) code. Sometimes you are dealing with Modified BSD or [Apache 2.0](https://fossa.com/blog/open-source-licenses-101-apache-license-2-0.md) Licensed code. Simple, clear flowcharts can be created for these use-cases too. If you are using a weak copyleft license like the [LGPL License](https://fossa.com/blog/open-source-software-licenses-101-lgpl-license.md), you can use this example in **Flowchart #5** that covers LGPL distribution: Flowchart #5: LGPL Code
## Adding compliance "checklists" to your process Apart from individual tasks when you distribute, staying on top of compliance involves integrating ongoing processes at your organization. When used properly, checklists can be a useful way to manage GPL compliance as well as communicate a process inside your company. The key is to start simple to avoid too much upfront process and review. Good compliance processes are ultimately a balance of work and risk. Use the template below as a way to start, and then add/customize as your organization grows in complexity: General Compliance Checklist
When it comes to more custom or complicated use cases, you might elect to add more specific checklists to address specific compliance goals. For example, when running builds of your product, the GPL requires you to distribute the "complete and corresponding" source code if incorporated in certain ways. Below you can find another checklist for this use case: Checklist for Rebuilding Product X
Plenty of options exist for more comprehensive checklists. A great place to start is the Open Compliance Program [Self-Assessment Compliance Checklist](https://compliance.linuxfoundation.org/compliance-related-templates/). This is a more detailed list running through the whole process and may be required for a larger organization. This checklist, like the material above, is free of charge and freely available so you can explore what is best to meet your requirements. ## Learn More [Practical GPL Compliance](https://www.linuxfoundation.org/resources/publications/practical-gpl-compliance) is a book written by Armijn Hemel and myself that was released at the end of April 2017. It is the culmination of ten years of working together in the Open Source compliance field. We started in European NGOs like GPL-violations.org and FSFE. As time went by our activities became more global and we started to address a more business-orientated audience. Our book bridges some of the knowledge obtained from and useful for both sectors. OpenChain is the industry standard for open source compliance in the supply chain. The OpenChain Project builds trust in open source by making open source license compliance simpler and more consistent. The [OpenChain Specification](https://fossa.com/blog/takeaways-iso-iec-dis-5230-openchain-specification.md) defines a core set of requirements every quality compliance program must satisfy. The [OpenChain Curriculum](https://www.openchainproject.org/curriculum) provides the educational foundation for open source processes and solutions, whilst meeting a key requirement of the OpenChain Specification. [OpenChain Conformance](https://www.openchainproject.org/conformance) allows organizations to display their adherence to these requirements. The result is that open source license compliance becomes more predictable, understandable, and efficient for participants of the software supply chain: [https://www.openchainproject.org/](https://www.openchainproject.org/) ## Footnote — Flowcharts and Checklists Want other formats? Get the checklists in [DOCX](https://wiki.linuxfoundation.org/_media/openchain/practicalgplcompliance-checklists.docx), [ODT](https://www.openchainproject.org/wp-content/uploads/sites/15/2017/06/PracticalGPLCompliance-Checklists.odt) or [PDF](https://www.openchainproject.org/wp-content/uploads/sites/15/2017/06/PracticalGPLCompliance-Checklists.pdf) format. Get AI, PDF, PNG, PSD, and SVG formats of the Flowcharts at: