Uploaded September 2026 | Updated November 2026, 2 days ago
With Briar Francis.
As a tech lawyer, there is no higher calling than source code review.
That is a lie. Source code review is the bane of my existence and hell hath no fury like a lawyer red-flagging copyleft licenses in code repositories.
More and more, investors are getting savvier about knowing the assets they're sinking money into. They're getting into every nook and cranny of an investment before they seal the deal – and that includes hiring someone like me to review your code so there's no nasty surprises. And if they're not doing that, they're making you give them some scary warranties and indemnities in your contract to compensate.
Needless to say, it bums me out when I see problematic open-source code in a project. But I can't really blame the developers. Intellectual property is an archaic, needlessly complex concept, and we as a (seemingly) intelligent society have collectively decided to make matters worse by licensing "free" stuff on terms a regular joe can't understand, nor fully appreciate.
So, let me help you help me. In this talk I'm going to take you through an open-source crash course. I'll break down some IP basics, analyse the major types of open-source licenses and their differences, cover some typical traps in license terms, and get on my soap box about good project hygiene.
If you use open-source assets in your projects (so… everyone at GCAP), then this talk is for you.
Video courtesy of GCAP and IGEA
www.gcap.com.au
With Briar Francis.
As a tech lawyer, there is no higher calling than source code review.
That is a lie. Source code review is the bane of my existence and hell hath no fury like a lawyer red-flagging copyleft licenses in code repositories.
More and more, investors are getting savvier about knowing the assets they're sinking money into. They're getting into every nook and cranny of an investment before they seal the deal – and that includes hiring someone like me to review your code so there's no nasty surprises. And if they're not doing that, they're making you give them some scary warranties and indemnities in your contract to compensate.
Needless to say, it bums me out when I see problematic open-source code in a project. But I can't really blame the developers. Intellectual property is an archaic, needlessly complex concept, and we as a (seemingly) intelligent society have collectively decided to make matters worse by licensing "free" stuff on terms a regular joe can't understand, nor fully appreciate.
So, let me help you help me. In this talk I'm going to take you through an open-source crash course. I'll break down some IP basics, analyse the major types of open-source licenses and their differences, cover some typical traps in license terms, and get on my soap box about good project hygiene.
If you use open-source assets in your projects (so… everyone at GCAP), then this talk is for you.
Video courtesy of GCAP and IGEA
www.gcap.com.au










