Let's discuss how to handle 3rdparty code in Qt in the future.

Qt ships with a lot of 3rd party code, not under CLA. This means the code cannot be relicensed, making it difficult to comply. Furthermore, not closely following any update changes might result in security issues.

Let's discuss how to improve the situation, e.g. by a more structured approach similar to Chromium:
- 3rd party code must always be in a '3rdparty' folder
- 3rd party code must always be included with a 'README.qt' file with details about the use of the code, where it's hosted upstream etc
- Documentation of 3rd party code is directly generated out of these files.

Furthermore we might discuss which 3rd party code we can get rid of at all, whether we can directly include upstream git repositories, use tools and standards like SPDX, provide a tool to scan for 3rd party code in custom builds ...

Info

Day: 2016-09-04
Start time: 13:00
Duration: 01:00
Track: In depth

Feedback

Click here to let us know how you liked this event.