Skip to content
dvnt.io

Resources · glossary

Source code copyright

Settling who may develop, copy and sell the code that was written. Without a written transfer of rights, they stay with the developer, even when the invoice has been paid.

Also called
  • software copyright
  • code ownership
  • IP assignment
  • transfer of copyright
  1. 01

    Paid for doesn't mean yours

    Polish copyright law requires a written agreement that lists the fields of exploitation (the specific ways the work may be used). A contract that only says "build a website" gives you the right to use it, but not necessarily to have someone else make changes.

  2. 02

    When it comes to light

    When you change agency. The new developer asks for the repository, the old one refuses, and formally they are right. This is the most common route to the situation we describe under vendor lock-in.

  3. 03

    What can't be transferred

    Third-party libraries and plugins; they stay under their own licences. The transfer covers what was created on your commission, which is why it pays to name that boundary in the contract.

  4. 04

    The minimum in the contract

    Transfer of the economic copyright on payment, the fields of exploitation listed, consent to exercise derivative rights (that is, to modify the code) and access to the repository from day one, not at the end.

Related terms

  • Vendor lock-inDependence on a single provider, where switching tools or vendors is so costly that it stops being a real option. It is rarely a decision, usually a side effect.
  • Software licencePermission to use someone else's code on set terms. It is not the same as ownership: when you buy an implementation, you usually buy the right to use it, not the code.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.