Merge pull request #752 from nextcloud/ci/reuse

chore(ci): add reuse check and fix reuse

.editorconfig

@@ -26,3 +26,8 @@ tab_width = 2
 [{*.markdown,*.md}]
 tab_width = 2
 trim_trailing_whitespace = false
+
+[{*.yml,*.yaml}]
+tab_width = 2
+indent_size = 2
+indent_style = space

.github/workflows/reuse.yml

@@ -0,0 +1,22 @@
+# This workflow is provided via the organization template repository
+#
+# https://github.com/nextcloud/.github
+# https://docs.github.com/en/actions/learn-github-actions/sharing-workflows-with-your-organization
+
+# SPDX-FileCopyrightText: 2022 Free Software Foundation Europe e.V. <https://fsfe.org>
+#
+# SPDX-License-Identifier: CC0-1.0
+
+name: REUSE Compliance Check
+
+on: [pull_request]
+
+jobs:
+  reuse-compliance-check:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332 # v4.1.7
+
+      - name: REUSE Compliance Check
+        uses: fsfe/reuse-action@3ae3c6bdf1257ab19397fab11fd3312144692083 # v4.0.0

LICENSES/LicenseRef-AppleAppStoreBadge.txt

@@ -0,0 +1,46 @@
+App Store Badges
+
+Include App Store badges in all digital and printed marketing materials as a clear call to action to get your app. App Store badges are available in 40 localizations to help you reach a broader audience. Versions are available for the App Store for iPhone and iPad, the Mac App Store, and Apple TV.
+
+
+Preferred Badges
+
+Use the preferred black badge in all marketing communications promoting your app. The gray border surrounding the black badge is part of the badge artwork and should not be modified. Whenever one or more badges for other app platforms appear in the layout, use the preferred black badge. Place the App Store badge first in the lineup of badges.
+
+
+Legal Requirements
+Trademark Symbols
+
+In communications distributed only in the United States, the appropriate symbol (™, ℠, or ®) must follow each Apple trademark the first time it is mentioned in body copy. Do not use trademark symbols on products, product documentation, or other product communications that will be distributed outside the United States.
+
+For example, use Apple Watch®, iPhone®, iPad®, iPod touch®, Apple TV®, App Store®, Mac App Store℠, Mac®, MacBook Pro®, MacBook Air®, and iMac®.
+
+Don’t add symbols to headline copy or to the App Store badge artwork provided by Apple.
+
+For the correct trademark symbols, refer to the Apple Trademark List.
+Credit Lines
+
+Use the appropriate credit lines in all communications worldwide, listing all the Apple trademarks and products included in your communication and advertising. Include the credit lines only once in your communication or website, and place the credit lines wherever you provide legal notification. Follow standard practices for the placement of legal copy, such as creating additional screens or providing interactive links. When the App Store badge is used, credit both Apple and the Apple Logo.
+
+Refer to the Apple Trademark List for the correct trademark symbol, spelling of the trademark, and generic term to use with the trademark. Generally, the symbol appears at the right shoulder of the trademark (except the Apple Logo, where the logo appears at the right foot).
+
+Use the following formats for distribution within the United States only:
+
+______ and ______ are registered trademarks of Apple Inc.
+
+______ and ______ are trademarks of Apple Inc.
+
+For distribution outside the United States, use one of the following international credit notices:
+
+______ and______ are trademarks of Apple Inc., registered in the U.S. and other countries.
+
+______ and______ are trademarks of Apple Inc.
+
+A translation of the legal notice and credit lines (but not the trademarks) can be used in materials distributed outside the U.S.
+
+For more information on using Apple trademarks, see Using Apple Trademarks and Copyrights.
+Association with Apple
+
+Your app screen images, Mac, Apple Watch, iPhone, iPad, iPod touch, and Apple TV product images, or photographs thereof cannot be used in any manner that falsely suggests an association with Apple or is likely to reduce, diminish, or damage the goodwill, value, or reputation associated with the App Store, the Mac App Store, iPhone, iPad, iPod touch, Apple Watch, Apple TV, or Apple itself.
+
+see https://developer.apple.com/app-store/marketing/guidelines/

LICENSES/LicenseRef-CollaboraTrademarks.txt

@@ -0,0 +1,30 @@
+Trademark policy
+
+1) Collabora, Collabora Productivity, Collabora Office, Collabora Online, Collabora Online Development Edition (CODE), Collabora CloudSuite, Collabora GovOffice and the Collabora Productivity logo are the property of either Collabora Productivity Ltd or Collabora Ltd. Collectively they will be referred to as the “Marks” in this policy document.
+
+2) We acknowledge and support your right to make “fair use” of the Marks and do not mean to suggest with these guidelines that our permission is required in such cases. We cannot, however, tell you categorically what will or will not qualify as “fair use”.
+
+3) Your use of the Marks must be non-disparaging and you must avoid any attempt to unfairly or confusingly capitalise on the goodwill of the Marks. Use of the Marks must in no way indicate a greater degree of association between you and Collabora/Collabora Productivity than actually exists.
+
+4) You should not include any of the Marks in the name of your application, product or service without our written permission, regardless of whether it’s commercial or non-commercial in nature. This includes online services, such as e-commerce, community, blog, informational, promotional, and personal home page sites as well as client apps or third party apps which interact with Collabora Productivity software.
+
+4.1) If you are producing new software that is intended to provide integration with a product using a Mark, you may use the Mark in a way which indicates the intent of your product. For example, if you are developing a plugin tool to integrate Collabora Online with another system, acceptable project titles might be “Collabora Online plugin for …” or “Collabora Online integration for …” However, you may not use the Marks in a way which implies an endorsement where that doesn’t exist,
+or which attempts to unfairly or confusingly capitalize on the goodwill or brand of the project.
+
+5) Domain Names: If you want to include all or any of the Marks in a domain name, you should seek our permission (see Contact Information below to request permission). People naturally associate domain names with organizations whose names sound similar. Almost any use of the Marks in a domain name is likely to confuse someone, thus running afoul the overarching requirement that any use of a the Marks must not be confusing. By “domain name” we mean to refer to top-level domains and second-level domains, but not sub-domains.
+
+6) Distributing unmodified Collabora Productivity binaries: You can use the Marks to identify Collabora Productivity binary downloads separately or as part of a Virtual Machine, docker image, installer, or in another form as long as you have not made any modifications to the Collabora Productivity binaries themselves
+
+7) Distributing modified Collabora Productivity binaries: In making such a distribution you must remove all trademark uses of the Marks from the version of the Collabora Productivity software you are modifying.
+
+8) Although we love to encourage authors, if you want to include all or any of the Marks in the name of a publication such as a book or magazine, you need our permission (see Contact Information below to request permission). But you can use any or all of the Marks in a title of review inside a magazine, for example, as long as you use the Marks to refer to the official Collabora Productivity software or products.
+
+9) Collabora Productivity reserves the sole right to determine compliance with, modify or grant exceptions to this policy.
+
+10) Contact Information:
+
+Please contact us if you need assistance regarding these Guidelines, e.g. for discussing your case or requesting permission, by sending an Email to trademark@collaboraoffice.com.
+
+11) Licence for these Guidelines
+
+These Guidelines are published under Version 3 of the Creative Commons Attribution Share-Alike License (https://creativecommons.org/licenses/by-sa/3.0/), and are derived in part from the ownCloud Trademark Guidelines (March 1st 2016) which in turn is derived in part from the openSUSE Trademark Guidelines (April 20, 2015), which in turn is derived in part from the OpenSolaris Trademark Policy 1.0 (May 5, 2008), the Ubuntu and Mozilla Trademark guidelines.

LICENSES/LicenseRef-FacebookTrademarks.txt

@@ -0,0 +1,17 @@
+Facebook brand resources and guidelines
+
+The logo is our most important brand asset. We use it with consistency and intention to represent the world of social discovery to billions of people around the world.
+
+Our Logo Evolution
+
+Our logo has evolved over time, building on our past heritage, using an 'f' within a blue circle. The current logo has been refined in shape and color to make it more accessible and legible. Always ensure you are using the current version of our logo in any new designs or communications.
+
+Legal
+
+Meta dedicates substantial resources to the development and protection of its intellectual property. In addition to seeking registration of its trademarks and logos around the world, Meta enforces its rights against people who misuse its trademarks.
+
+Meta's trademarks are owned by Meta and may only be used as provided in these guidelines or with Meta’s permission. A list of some of Meta’s trademarks can be found here (https://about.meta.com/brand/resources/meta/our-trademarks/). You may not use or register, or otherwise claim rights in any Meta trademark, including as or as part of any trademark, service mark, company name, trade name, username or domain registration. You should not use or claim rights in any trademark in a way that is confusingly similar to or dilutive of Meta’s trademarks, including as, or as any part of, a trademark. Do not use Meta's trademarks for anything that would be inconsistent with Meta’s Terms of Service (https://www.facebook.com/terms.php) or Community Standards (https://transparency.meta.com/policies/community-standards/).
+
+We may revoke permission to use Meta’s trademarks at any time. Meta reserves the right to withhold approval of content that it considers inconsistent with the Meta brand.
+
+A copy can be found at https://about.meta.com/brand/resources/facebook/logo/

LICENSES/LicenseRef-GooglePlayBadge.txt

@@ -0,0 +1,23 @@
+badge guidelines
+Dos & Don'ts
+
+Follow these guidelines whenever you are using a Google Play badge.
+
+* Use the badges as provided. Never alter the badges.
+* There must be clear space surrounding the badge equal to one-quarter the height of the badge.
+* The badge must be large enough that all of the text is legible.
+* The Google Play badge should be the same size or larger than other application store badges.
+* Badges must be shown on a solid colored background or a simple background image that does not obscure the badge.
+* Match the badge language to the language of your marketing campaign whenever possible.
+* Any online use of the badge must link to the Google Play store. Use the generator below to get the HTML to include in your digital marketing.
+* The badge can only be used to promote content available on Google Play.
+* Include the appropriate Google Play legal attribution when there is space in the creative. See the badge generator for localized legal attributions.
+* Use of the Google Play badge must be reviewed and approved by the Google Play Partner Brand team if the badge will be in:
+  * a TV commercial
+  * an out-of-home marketing campaign
+  * a marketing campaign that will receive over 1 million impressions
+* Use this form (https://partnermarketinghub.withgoogle.com/login/?next=/submit-assets/) to submit your marketing for approval.
+
+see https://play.google.com/intl/en_us/badges/
+
+Google Play and the Google Play logo are trademarks of Google LLC.

LICENSES/LicenseRef-MastodonTrademarks.txt

@@ -0,0 +1,46 @@
+Trademark Policy
+
+Last updated December 21, 2022
+
+The Mastodon name and logos are trademarks of Mastodon gGmbH. As such, their use is restricted and protected by intellectual property law. While the software we create is available under a free and open source software license, the copyright license does not include an implied right or license to use our trademarks.
+
+The role of trademarks is to prevent the exploitation of the good name and reputation of Mastodon by other people and organizations, and to provide assurance about the quality of the products and services associated with it.
+
+To use our trademarks beyond what is considered "fair" or "nominative" use, you must follow these guidelines. By making use of our trademarks, you agree to abide by the following terms and conditions. You further agree that any dispute arising in connection with your use of our trademarks or under these terms and conditions shall be under the exclusive jurisdiction of the state and federal courts of New York in the United States of America and that the state and federal courts of New York shall have personal jurisdiction over you for the purposes of adjudicating any dispute concerning the use of our trademarks or these terms and conditions.
+
+You agree to defend and indemnify Mastodon gGmbH from and against any and all claims and losses brought by a third party in connection with your use of the Mastodon trademarks.
+
+To request the use of the Mastodon name and logos in a way not covered in these guidelines, or to report violations, please contact us at trademark@joinmastodon.org. In the event that we do not approve such use of the Mastodon name and logos within ten (10) business days, your request shall be deemed denied.
+General guidelines
+
+In general:
+
+* Only use the Mastodon marks to accurately identify those goods or services that are built using the Mastodon software.
+* Do not use the Mastodon marks in any way that could mistakenly imply that Mastodon GmbH has reviewed, approved, or guaranteed your goods or services.
+* Do not use or register, in whole or in part, the Mastodon marks as part of your own or any other trademark, service mark, domain name, company name, trade name, product name, or service name.
+* Do not use the Mastodon marks in a manner that disparages or defames the marks, Mastodon gGmbH, or Mastodon’s products.
+* Do not use the Mastodon marks in connection with any illegal activity.
+* You may use the Mastodon word mark in referential phrases such as "for", "for use with", or "compatible with".
+* You may use the Mastodon marks when embedding or otherwise displaying user generated content published using the Mastodon software.
+* Do not change or modify the Mastodon marks.
+* Any all use of the Mastodon marks, and any goodwill accrued as a result of that use, belongs entirely to, and shall inure for the benefit of, Mastodon gGmbH.
+
+Server guidelines
+
+If you run your own Mastodon server using the Mastodon software, including modified Mastodon software on the condition that the modifications are limited to switching on or off features already included in the software, minor tweaks in visual appearance, translations into other languages, and bug fixes:
+
+* You may not use the Mastodon word mark, or any similar mark, in your domain name, unless you have written permission from Mastodon gGmbH.
+* As long as you abide by the terms and conditions of this agreement, you may use the Mastodon marks included in the Mastodon server software for the purposes of running the server.
+
+Open source project guidelines
+
+If you choose to build on or modify Mastodon's open-source code, beyond modifications limited to switching on or off features already included in the software, minor tweaks in visual appearance, translations into other languages, and bug fixes:
+
+* You must choose your own branding, logos, and trademarks that denote your unique identity so as to clearly signal to users that there is no affiliation with or endorsement by Mastodon gGmbH.
+* You may use word marks, but not our logos, in truthful statements that describe the relationship between your software and ours, for example "this software is derived from the source code of the Mastodon software".
+
+Social media guidelines
+
+The name and handle of your social media account and any and all pages cannot begin with a Mastodon word mark, or a similar mark (e.g. "mastodoon", "mast0don", "mstdn"). In addition, Mastodon logos cannot be used in a way that might suggest affiliation with or endorsement by Mastodon.
+
+A copy can be found at https://joinmastodon.org/de/trademark