-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First draft of Dask trademark policy based on discussion in #4 #18
Open
seibert
wants to merge
4
commits into
dask:main
Choose a base branch
from
seibert:trademark
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,72 @@ | ||
Dask Trademark Policy | ||
===================== | ||
|
||
This document describes the policy governing the use of the "Dask" trademark, | ||
which is owned by NumFOCUS and administered on behalf of the Dask project. Any | ||
use of the Dask trademark commercially or non-commercially must be in | ||
accordance with the policy described in this document unless specific written | ||
permission is obtained from NumFOCUS. | ||
|
||
Usage and modification of the Dask *software* is governed by the | ||
[license](https://github.com/dask/dask/blob/main/LICENSE.txt), which describes | ||
permissible behavior under copyright law. Trademarks are a distinct form of | ||
intellectual property, and so the guidelines in this document apply only to | ||
the "Dask" trademark and logo, but not to the software itself. | ||
|
||
Intent | ||
------ | ||
|
||
Our goal is to enable the Dask trademark and logo to be used with minimal | ||
restrictions by both commercial and non-commercial entities, but we do *not* | ||
want the Dask trademark to be used: | ||
|
||
* to cause confusion about whether a project, product, or service is endorsed | ||
by the Dask community in some way. | ||
* in a way that allows an entity to misleadingly imply ownership of Dask or | ||
influence over the Dask project. | ||
|
||
Permissible usage | ||
----------------- | ||
|
||
The Dask trademark is always subject to "nominative use rules" which allow the | ||
usage of the trademark for descriptive purposes that does not suggest | ||
sponsorship or endorsement by the trademark owner. You may freely describe | ||
that your product or service "uses Dask" or is "powered by Dask," and you | ||
may use the unaltered Dask logo to indicate this without prior approval. | ||
(Please see the [Dask Brand Guide](https://www.dask.org/brand-guide) for more | ||
details about how to use the Dask logo.) | ||
|
||
Open source projects may also use the Dask name as part of the name of their | ||
project (Ex: `dask-cuda`) so long as it satisfies *all* the following | ||
criteria: | ||
|
||
* The project is open source with a liberal license. | ||
* The project is related to Dask. | ||
* The project name should not be overly grand in claiming namespace. | ||
* The project should not make subjective claims in the name itself. | ||
|
||
Usage of the "Dask" trademark should also be consistent with the [Dask Code of Conduct](https://github.com/dask/governance/blob/main/code-of-conduct.md). | ||
|
||
Non-permissible usage | ||
--------------------- | ||
|
||
The Dask trademark may *not* be used in a commercial product or company name. Examples of disallowed uses include: | ||
|
||
* Dask Pro | ||
* Dask Enterprise | ||
* The Dask Company | ||
* CompanyName Dask | ||
|
||
Company and product logos may not derive from the Dask logo in a way that would cause brand confusion. | ||
|
||
Where to get more information | ||
----------------------------- | ||
|
||
If you are unsure whether your planned usage of the Dask trademark is allowed, | ||
or feel that you need specific written approval for your situation, please | ||
contact the Dask maintainers at [email protected]. | ||
|
||
Acknowledgements | ||
---------------- | ||
|
||
This document is the result of the community discussion found in [dask/governance#4](https://github.com/dask/governance/issues/4). It draws inspiration from both the [PSF Trademark Policy](https://www.python.org/psf/trademarks/) and the Model Trademark Guidelines, available at http://www.modeltrademarkguidelines.org. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mrocklin I note that the Coiled website says "Coiled: A Dask Company" which to me seems to be 99% the same as this disallowed example.
Should this document be updated to allow for your use of this? Or are you planning on changing your strapline?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. I think it's useful for consumers to know that we are a company pretty much entirely focused around Dask. I'd say that today we are, de-facto, "The Dask Company" but aren't saying so, instead saying "A Dask Company" to make space potentially for others.
What do folks think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's think about this a bit more. I think that there are a few outcomes:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see your intent, but I think a common interpretation of "A Dask Company" would be "A company that is owned/endorsed by Dask".
Here are some real world examples of this usage:
Given this common interpretation I think that option 3 is the correct choice here. I personally would also be up for discussing option 2, but would suggest strong consensus between all owners.
Coiled also uses the tagline "Dask that just works" which I think fits much better with the trademark policy here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to have this conversation. I think that it benefits users and reflects reality a bit. We happen to have a call in 20m. I'd like to reserve 5m at the end for this if you're game.