-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #45252 from nextcloud/chore/noid/spdx-batch2
Add SPDX header - batch #2
- Loading branch information
Showing
1,033 changed files
with
3,160 additions
and
13,478 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,3 @@ | ||
# SPDX-FileCopyrightText: 2019 Nextcloud GmbH and Nextcloud contributors | ||
# SPDX-License-Identifier: AGPL-3.0-or-later | ||
custom: https://nextcloud.com/include/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
SPDX-FileCopyrightText: 2018 Nextcloud GmbH and Nextcloud contributors | ||
SPDX-License-Identifier: AGPL-3.0-or-later |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,5 @@ | ||
# SPDX-FileCopyrightText: 2018 Nextcloud GmbH and Nextcloud contributors | ||
# SPDX-License-Identifier: AGPL-3.0-or-later | ||
firstPRMergeComment: > | ||
Thanks for your first pull request and welcome to the community! | ||
Feel free to keep them coming! If you are looking for issues to tackle then have a look at this selection: https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
SPDX-FileCopyrightText: 2022 Nextcloud GmbH and Nextcloud contributors | ||
SPDX-License-Identifier: AGPL-3.0-or-later |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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. |
Oops, something went wrong.