README/HACKING.md does not specify license and copyright terms

This page summarizes the projects mentioned and recommended in the original post on /r/tutanota

Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • Tutanota makes encryption easy

    Tuta is an email service with a strong focus on security and privacy that lets you encrypt emails, contacts and calendar entries on all your devices.

    https://github.com/tutao/tutanota s README does not mention the license in play (most of it is GPLv3 as the LICENSE file suggests).

  • your-repository

    This is your repository (by fwolfst)

    I'd usually open a github issue and link to https://github.com/fwolfst/your-repository/issues/3 , but the repo states that gh-issues shall be used for bugs exclusively, and most likely there are only a few license-nerds that consider this a bug. Feel free to ask me for a PR, though (and for that I'd open an issue).

  • SurveyJS

    Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  • reuse-tool

    reuse is a tool for compliance with the REUSE recommendations.

    Putting the copyright and licensing information in every file was very common, and FSFEs reuse has some interesting specifications if compliance is an issue (e.g. I do not fully understand what the OpenSSL license included in the app-ios/tutanota/include folder covers, which also includes a APL-licensed files) - but thats a different topic.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts