Narvuk Logo NARVUK

At Narvuk, we are committed to fostering innovation and collaboration through open source software. This Open Source Policy outlines our approach to participating in, contributing to, and utilizing open source projects. We are dedicated to upholding the principles of transparency, community engagement, and respect for intellectual property.

1. Commitment to Open Source

Narvuk embraces the open source philosophy, which values transparency, community collaboration, and shared innovation. We actively contribute to and use open source projects as part of our commitment to leveraging collective knowledge and advancing technology. This commitment is reflected not only in our use of open source technologies but also in our own open source initiatives.

Our commitment includes:

  • Encouraging open source contributions from our team and the broader community to drive innovation and improve our projects.
  • Ensuring that our open source projects adhere to industry standards and best practices to maintain high-quality and reliability.
  • Engaging with the open source community through active participation, collaboration, and addressing issues to support and grow the ecosystem.
  • Advocating for open source practices within our organization and promoting their benefits, including increased transparency and community involvement.

2. Open Source Licenses

Narvuk employs a variety of open source licenses to govern our projects and contributions, ensuring that software and other resources are shared in a manner consistent with open source principles. Below are key licenses we use, along with their implications:

  • GNU General Public License (GPL): This copyleft license mandates that software remains free and open by requiring that derivative works be distributed under the same license. It promotes freedom by allowing users to modify and distribute the software while ensuring that all modifications are also open source. For more details, visit the GNU GPL License page.
  • GNU Lesser General Public License (LGPL): Tailored for libraries, the LGPL permits linking with proprietary software without affecting the license of the proprietary code. It allows developers to use LGPL-licensed libraries in both open source and proprietary applications. Learn more on the GNU LGPL License page.
  • Apache License 2.0: A permissive license allowing users to use, modify, and distribute the software with minimal restrictions. It includes patent rights provisions and provides an express grant of rights, making it suitable for a wide range of applications. For details, visit the Apache License 2.0 page.
  • MIT License: Known for its simplicity and permissiveness, the MIT License allows users to freely use, modify, and distribute the software. Its minimal requirements for attribution make it easy to integrate into various projects. Find more information on the MIT License page.
  • BSD License: This permissive license is similar to the MIT License but includes clauses related to the use of the software's name for promotion. It offers flexibility for commercial and non-commercial use while preserving the rights of the original authors. Details can be found on the Open Source Initiative BSD License page.
  • Creative Commons Licenses: Designed for creative works, these licenses offer various levels of permission, such as attribution, non-commercial use, and share-alike requirements. They provide a flexible framework for licensing creative content and encouraging collaboration. For an overview of Creative Commons licenses, visit the Creative Commons License page.

3. Guidelines for Contributions

We welcome contributions from individuals and organizations that align with our open source projects. To ensure a smooth contribution process and maintain high standards, please adhere to the following guidelines:

  • Compliance with Licensing: Ensure all contributions comply with the relevant open source licenses. This includes adhering to the license terms, providing proper attribution, and including any required license texts or notices.
  • Submission Process: Submit contributions through our official channels, such as pull requests on GitHub or other version control systems. Follow our contribution guidelines and templates for consistency and clarity.
  • Documentation: Provide detailed documentation for your contributions, including descriptions of changes, bug fixes, enhancements, or new features. Comprehensive documentation helps maintain project quality and usability.
  • Code of Conduct: Adhere to our code of conduct and community guidelines to ensure a respectful and inclusive environment for all contributors.
  • Quality Assurance: Ensure that contributions are thoroughly tested and reviewed to maintain project integrity and stability. Contributions should meet our quality standards before integration.
  • Feedback and Collaboration: Be receptive to feedback and engage in constructive discussions with other contributors and maintainers. Collaborative dialogue enhances the project and supports a positive community.

4. Using Open Source Software

Our use of open source software is guided by principles of compliance and transparency. When incorporating open source software into our projects, we follow these practices:

  • Licensing Compliance: Ensure that all open source software used adheres to its respective license terms. This includes providing proper attribution, including license texts, and meeting any other requirements specified by the license.
  • Transparency: Disclose the use of open source software in our products and services, including listing open source components and their licenses in our documentation and product releases.
  • Intellectual Property: Respect the intellectual property rights of original authors and contributors of open source software. Acknowledge contributions and adhere to any restrictions imposed by the license.
  • Documentation: Provide clear documentation and instructions for users about the open source software included in our products, including its origin, licensing, and any modifications made.
  • Security and Maintenance: Monitor for and address security vulnerabilities or issues related to the open source software we use. Collaborate with the community to report and resolve these issues promptly.

5. Compliance and Enforcement

Ensuring compliance with open source licenses is a top priority for Narvuk. We have established measures to uphold legal and ethical standards. If you believe there has been a violation of this policy or any open source licenses, please follow these steps:

  • Reporting Violations: Report suspected violations via email at opensource@narvuk.com. Provide detailed information about the suspected violation, including relevant documentation or evidence.
  • Investigation: We will investigate all reports of violations promptly. This may include reviewing compliance with licensing terms, correcting errors, and implementing measures to prevent future violations.
  • Resolution: We are committed to resolving compliance issues fairly and transparently. We will work with affected parties to reach a satisfactory resolution and ensure ongoing adherence to open source licenses.

6. Open Source License Resources

For comprehensive information on open source licenses, including lists and details of various licenses, please refer to the following resources:

  • Open Source Initiative (OSI): The OSI provides a directory of approved open source licenses and detailed explanations of each license's terms and conditions.
  • GNU Licensing: Offers information on GNU licenses, including the GPL and LGPL, and their respective terms and requirements.
  • Open Source.com License Resource: A resource for understanding different open source licenses and their implications for software development.
  • Creative Commons: Provides details on Creative Commons licenses, which are commonly used for creative works, including their terms and conditions.

7. Policy Changes

This Open Source Policy may be updated periodically to reflect changes in our practices, legal requirements, or the open source landscape. The date of the most recent revision will be indicated at the bottom of this Policy.

We encourage all users, contributors, and stakeholders to review this Policy regularly to stay informed about our open source practices. Continued participation in Narvuk’s open source initiatives and use of our products and services constitutes acceptance of any revised terms.

Last Updated: 03 March 2025