For explanation of some terms, see the Glossary / Sanasto (in Finnish)

 

VALIDOS' GENERAL INSTRUCTION FOR REDISTRIBUTION OF OPEN SOURCE PACKAGES BY COMPANIES

THREE STEP INSTRUCTION:

  1. Follow the general instructions of Validos below in this document
    • If the summary of all Validos reports (requires logging in) does not contain an "AR" marker for the relevant software, step 1 is enough
    • If the summary of all Validos reports contains an "AR" marker, then you need to go through steps 2 and 3, as well
  2. Follow the OS-package specific instructions in the use instruction of the package (requires logging in)
    • Section 3.1 of the use instruction, if you do not modify the code
    • Sections 3.1 and 3.2 of the use instruction, if you modify the code
    • If the package has not yet been validated, ask for validation
  3. Include the document stated in section 3.3. of the use instruction, if any, in any redistribution as a part of your documentation and refer to it in your other documentation.

GENERAL INSTRUCTIONS:

Remember to always check your customer contract (or similar) for clauses on the use of open source software, and comply with the requirements set out therein.

When redistributing an open source package:

  1. Keep all copyright notices, license references, license texts, notice-texts and warranty disclaimers (readme.txt, notice.txt, license.txt, credits.txt and the like) intact and redistribute these together with the package when you redistribute the package.
  2. Do not use the name or any mark of (i) the software, (ii) the project, (iii) any author or (iv) any copyright holder in any marketing, promotional or similar material or for such purposes, nor in the name of your product or in any other such way.
  3. When you modify an open source package and redistribute it as modified, you should:
    • Always mark your own modifications clearly added with the date of your change. This is typically done by markings at the beginning of the relevant file.
    • (We also recommend that you, in connection with such markings, add your own copyright notice and the compliant license or compliant license reference, under which you license your modifications.)
  4. When you distribute the open source package as binary, you should also preferably always distribute the source code distribution of the original open source package together with the binary and state in the binary that the original source is distributed together with the binary.
  5. If item 4 is not possible (e.g. due to space restrictions) verify that all separate text files listed in item 1 are contained in the binary distribution in a corresponding directory.

This instruction does not address patent or trademark related terms, nor applicable law provisions. For these, if any, see software package specific use instructions.