28.01.2023 Views

CENSIS white paper: Intellectual Property in Business

2023: This CENSIS white paper sets out to make the topic of IP more approachable, less intimidating and more manageable, offering experience-based advice and methods are are designed to help businesses structure their IP- related issues and makes the best of their IP. Covering: The role of IP, IP management during growth, IP strategy for expanding companies and corporates, Business IP Canvas - merging IP with your business model.

2023: This CENSIS white paper sets out to make the topic of IP more approachable, less intimidating and more manageable, offering experience-based advice and methods are are designed to help businesses structure their IP- related issues and makes the best of their IP.
Covering:
The role of IP, IP management during growth, IP strategy for expanding companies and corporates, Business IP Canvas - merging IP with your business model.

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Intellectual</strong> <strong>Property</strong> <strong>in</strong> Bus<strong>in</strong>ess: IP basics, IP management, IP strategy<br />

IP Management dur<strong>in</strong>g Growth (cont<strong>in</strong>ued)<br />

15 A few words for code<br />

developers: open-source<br />

software<br />

Integrat<strong>in</strong>g open-source software (OSS) <strong>in</strong>to the code is<br />

almost a standard <strong>in</strong> software development nowadays.<br />

From an IP perspective, us<strong>in</strong>g OSS is neither good nor<br />

bad. The assessment depends entirely on the adopted<br />

bus<strong>in</strong>ess strategy and whether the use of OSS supports<br />

it – more precisely, whether the types of OSS licence<br />

a company implements are compatible with its policy<br />

and the bus<strong>in</strong>ess model it aspires to. It is important to<br />

remember that OSS licences are copyright licences –<br />

multilateral licences with each of them represent<strong>in</strong>g the<br />

agreement of a specific community and reflect<strong>in</strong>g the<br />

norms of a community. 55<br />

Open-source software licences range from strictly<br />

copyleft licences, where the proprietary code must be<br />

released on the same conditions as the copyleft code it<br />

is based on, to so-called permissive licences, where the<br />

code release rema<strong>in</strong>s at the discretion of the company.<br />

Without an open-source licence, the software<br />

component is unusable by others, even if it has been<br />

publicly posted on GitHub. 56<br />

Comprehensive and useful overviews of most<br />

common OSS licences can be found at:<br />

• https://choosealicense.com/licenses/<br />

• https://opensource.org/licenses<br />

• https://www.<strong>white</strong>sourcesoftware.com/resources/<br />

blog/open-source-licenses-expla<strong>in</strong>ed/<br />

• https://en.wikipedia.org/wiki/Comparison_of_free_<br />

and_open-source_software_licences<br />

It is important that OSS is used accord<strong>in</strong>g to the licence<br />

conditions, and these must be checked beforehand. If<br />

the use violates the conditions, it will be recognised as a<br />

breach of contract or a copyright <strong>in</strong>fr<strong>in</strong>gement.<br />

Review<strong>in</strong>g the conditions of a licence beforehand<br />

has a profound importance for a bus<strong>in</strong>ess: licence<br />

requirements/obligations should comply with your<br />

bus<strong>in</strong>ess strategy, and not the opposite. Therefore,<br />

there is a need for company protocols and policies<br />

def<strong>in</strong><strong>in</strong>g which and when OSS licences should be used<br />

<strong>in</strong> code development. 57 Software developers with<strong>in</strong><br />

the company should also be made aware of their<br />

obligations under the company policies.<br />

Last but not least, open-source-based bus<strong>in</strong>esses can<br />

be commercially successful. After all, companies play<br />

with diverse features and bus<strong>in</strong>ess models to capture<br />

the value from their developments.<br />

My experience shows that code developers are aware<br />

of diverse OSS licence regimes and can navigate quite<br />

well through the jungle of OSS licences. The challenge<br />

is much more about know<strong>in</strong>g first what the bus<strong>in</strong>ess<br />

direction is and how to manage the OSS components <strong>in</strong><br />

your product.<br />

55<br />

‘Frequently Answered Questions’ (Open Source Initiative) accessed 2 December 2022.<br />

56<br />

Ayala Goldste<strong>in</strong>, ‘Open Source Licenses Expla<strong>in</strong>ed’<br />

(WhiteSource, 24 January 2021) https://www.<strong>white</strong>sourcesoftware.com/resources/blog/open-source-licenses-expla<strong>in</strong>ed/ accessed 2 December 2022<br />

57<br />

Harroch (n 1).<br />

35

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!