AVB Veritas

Academic foundation · Software and law

Intellectual Property in a World of Open Source and Community Software

Leonardus Herps deliberately brought law and software technology together in his Maastricht University thesis, “Intellectual Property in a World of Open Source and Community Software.” The work is an early foundation for his present legal-technical analysis of software ownership, licensing, source-code provenance and technology evidence.

Written by Leonardus “Leo” Herps · Published 19 October 2026 · Reviewed 4 November 2026

The documented publication record

A professional profile filed in a public California Public Utilities Commission docket lists “Intellectual Property in a World of Open Source and Community Software” among Herps’s publications. His AVB Veritas profile identifies it as his Maastricht University law thesis. The exact award date and formal degree title are not stated here pending documentary confirmation, and the full thesis text is not represented as publicly available.

Why the subject matters

Open-source software does not sit outside intellectual-property law. Its use depends on copyright ownership, permission, licence conditions and the way software is copied, modified, combined, distributed or provided as a service. A technically accurate analysis must first establish what code and version were actually used before drawing legal conclusions.

Issues relevant to modern disputes

  • Authorship, ownership and assignment of source code
  • Identification of open-source components and applicable licence versions
  • Permissive, copyleft and strong-copyleft obligations
  • Derivative-work and software-combination questions
  • Distribution, source-code disclosure and notice obligations
  • Contributor, contractor and employee rights
  • Repository history, commits, dependency manifests and build records
  • Software representations, warranties and indemnities in transactions
  • AI-assisted development, provenance and inherited open-source obligations

From academic research to operational experience

The thesis is not presented as a substitute for current technical investigation. Its significance is the combination it represents: Herps studied the legal structure of software rights while also building and operating software-dependent technology and telecommunications businesses. That makes it possible to test a legal theory against repositories, architecture, deployment practice and commercial reality.

Relevance to expert-witness work

In software and intellectual-property matters, Herps can help counsel identify the relevant codebase, reconstruct provenance, distinguish factual technical findings from legal conclusions and explain how licence obligations relate to actual use. The same approach supports source-code ownership disputes, open-source compliance reviews, M&A diligence, AI-generated-code questions and rebuttal analysis.

Evidence discipline

The public CPUC filing corroborates the publication title. Until the underlying academic record or thesis text is published, this page does not state a graduation year, exact degree designation, grade, supervisor, page count or detailed thesis conclusions. Those details should be added only from primary documentation.

Questions from instructing counsel

Frequently asked questions

What was Leonardus Herps’s thesis about?

Its documented title is “Intellectual Property in a World of Open Source and Community Software.” It examined the intersection of software technology, open-source models and intellectual-property law.

Where did Leonardus Herps study law?

His professional profile states that he earned a law degree from Maastricht University and used the thesis to combine his interests in law and software technology.

Does the thesis make him an open-source licensing expert?

The thesis is one foundation. His expert offering also relies on more than 35 years of software and systems experience and on evidence-based analysis of the actual code, licences, contracts and deployment model in a dispute.

Can he analyze AI-generated code and open-source risk?

Yes. Relevant analysis can include code provenance, dependency and licence identification, human and machine contribution records, repository history and whether inherited obligations match the way the software is used or distributed.

Is the complete thesis available online?

AVB Veritas does not currently represent the full thesis as publicly available. A public CPUC filing independently lists the publication title.

Public sources

CPUC public filing listing the publication title↗

For counsel

Discuss the technical record.

For conflicts and scope review, send the parties, jurisdiction or docket, issue and deadline. Do not send confidential case files until a secure transfer method is agreed.

Contact Leo Herps ↗