Self-hosted project management for devs and their clients: tickets, time tracking, docs and meetings, with an AI assistant that cites its sources. AGPL-3.0.
Ruby agplai-assistantdockerdsgvogdprhotwireissue-trackerjira-alternativeknowledge-basellmmcp-servermeeting-notesopen-sourceproject-managementredmine-alternativeruby-on-railsself-hostedticketingtime-tracking
Add a trademark policy
Guido Boyke21f6d8a96426
diff --git a/README.md b/README.mdindex 136c619..44abefb 100644--- a/README.md+++ b/README.md@@ -171,6 +171,9 @@ maintainer and a few people we invite. An issue that describes the problem helpsBundled third-party components keep their own licenses, listed in[THIRD_PARTY_NOTICES.txt](THIRD_PARTY_NOTICES.txt).+The license covers the code, not the name or the logo. A modified version or a service built on it+goes by its own name: [TRADEMARKS.md](TRADEMARKS.md).+The license covers the code. It grants no rights to the name Lalabase, and none to Lala, themascot in `.github/readme/lala-*.svg`: the figure is not covered by the AGPL, all rights arereserved, and it may not be copied, modified or used outside this repository.diff --git a/TRADEMARKS.md b/TRADEMARKS.mdnew file mode 100644index 0000000..1980a92--- /dev/null+++ b/TRADEMARKS.md@@ -0,0 +1,126 @@+<!--+Maintainer note: once the DPMA registers the word mark "Lalabase", change "trademark"+to "registered trademark" in "The marks" and drop the sentence about the ®+symbol in "Writing the name". Do not use ® before that.+-->++# Lalabase Trademark Policy++Lalabase is open source software. The [AGPLv3](LICENSE) gives you broad rights+to the code: you may use it, study it, change it, share it and run it as a+service. The license does not give you rights to the **name** Lalabase or to+its **logo**. This policy explains how you may use them.++The goal is simple: when people see the name Lalabase, they should know what+they get and who stands behind it.++## The marks++This policy covers:++- the name **Lalabase**,+- the Lalabase logo and favicon.++Lalabase is a trademark of gboyke solutions UG (haftungsbeschränkt), Germany+("we" in this policy). An application to register it is pending with the+German Patent and Trade Mark Office (DPMA).++## The short version++- **You may** talk about Lalabase, run it, build on it and say that your work+ is based on it.+- **You may not** call your own version, product or service "Lalabase", or make+ it look like the official project or an official service.++## How this relates to the AGPL++- The AGPL is a copyright license. Trademarks are a separate right. Section 7(e)+ of the AGPLv3 expressly allows a project to decline trademark rights.+- This policy does not take away anything the AGPL grants for the code. You can+ still copy, change, run, share and host Lalabase. For a changed version or a+ service you offer to others, you just use your own name.+- Even where a file that shows a mark is distributed under the AGPL, the+ copyright license does not grant rights to use that mark.+- Keeping copyright notices, license notices and the project history intact is+ required by the AGPL. Doing so is not a trademark use and needs no permission.++## Uses that need no permission++1. **Talking about Lalabase.** Articles, reviews, comparisons, talks, tutorials,+ courses, videos and social media posts may name Lalabase, as long as what+ you say is accurate.+2. **Using Lalabase.** You can run Lalabase for yourself or your organisation,+ unmodified or with your own configuration, and call it Lalabase inside your+ organisation.+3. **Describing a relationship honestly.** You may write "based on Lalabase",+ "a fork of Lalabase", "works with Lalabase" or "integration for Lalabase",+ if your own name is more prominent than ours and you do not suggest an+ official connection.+4. **Offering services around Lalabase.** You may say, in plain words, that you+ install, host, support or teach Lalabase, for example "We host and support+ Lalabase for your team". Your service carries your own name and brand, and+ you do not use the Lalabase logo.+5. **Sharing unmodified copies.** You may distribute Lalabase under its name,+ for example as a Linux package or container image, if the software is+ unmodified apart from packaging changes and security fixes published by the+ project, and you do not present your build as the official one.+6. **Linking to the project.** You may use the unmodified logo to link to the+ official Lalabase website or repository, or to illustrate an article about+ Lalabase.+7. **Community activities.** Non-commercial user groups, meetups and events may+ use the name, for example "Lalabase User Group Hamburg", if it is clear that+ we do not run them.++## Uses that need written permission++1. Using "Lalabase", or a name that is easy to confuse with it, as the name of a+ modified version, a fork or another product. Examples: "LalaBase",+ "Lala Base", "Lalabase Plus", "OpenLalabase".+2. Using the name in the name of a hosted service, a company, a domain, an app+ store listing, a package or a social media account in a way that suggests it+ is official. Examples: "Lalabase Cloud" for your own hosting,+ "lalabase-hosting.example", "@lalabase_support".+3. Suggesting that we endorse, certify, partner with or sponsor you or your+ product.+4. Changing the logo, combining it with your own marks, or using it as the+ brand of your own product, service or marketing.+5. Selling merchandise with the name or the logo.++## Modified versions and forks++If you distribute a modified version of Lalabase, or offer a modified version+as a service to other people:++- **Choose your own name and logo.** Replace the Lalabase name and logo+ wherever your users see them: the product name in the interface, page titles,+ emails, the login and registration pages, the web app manifest and any public+ or marketing pages.+- **These may stay as they are:** identifiers in the code (such as the+ `Lalabase::` module, class names, file paths, database names and+ configuration keys), copyright and license notices, the commit history, and an+ honest statement that your software is based on Lalabase.+- **What counts as modified:** anything beyond changing settings the software+ supports (for example environment variables or admin settings), packaging+ changes, and security fixes published by the project.++## Writing the name++- Write **Lalabase** as one word with a capital L. Not "LalaBase", "Lala Base"+ or "lalabase" (except in code, commands and URLs).+- Use it as a name, not as a verb or a generic term for project software.+- The registration is still pending, so please do not add the ® symbol.++## Questions, permission and misuse++Write to **[email protected]** in German or English. For a permission request,+tell us what you plan to do and where the name or logo would appear. If you see+a use that confuses people, please let us know.++When a use does not fit this policy, we will contact the people behind it first+and look for a friendly solution.++## Changes and legal scope++We may update this policy. The version in this repository applies. This policy+does not restrict uses that the law allows without permission, such as honest+descriptive references. It is not legal advice.