This policy governs use of the MrWhoOidc name, logos, and other brand assets.
The project source code is licensed separately under Apache License 2.0.
The Apache 2.0 license applies to the source code in this repository. It lets you use, modify, redistribute, and sell software built from that code, subject to the Apache 2.0 terms.
The Apache 2.0 license does not grant trademark rights. Section 6 of Apache 2.0 expressly reserves trade names, trademarks, service marks, and product names.
You may use MrWhoOidc in a descriptive, non-branding way to:
- refer to this project as the upstream source
- state factual compatibility, such as "compatible with MrWhoOidc"
- identify unmodified copies of this project
- describe that your fork or service is "based on MrWhoOidc" or "forked from MrWhoOidc", if the statement is accurate and not misleading
You may not, without prior written permission:
- market a modified version, hosted service, consulting offer, or commercial product as
MrWhoOidc - use
MrWhoOidcas the primary name of a fork, derivative product, or SaaS offering - use the
MrWhoOidcname or logos in a way that implies endorsement, sponsorship, certification, partnership, or official status - use logos, trade dress, domain names, package names, social media handles, or app store listings that are likely to confuse users into thinking your offering is the official project
If you fork, modify, or redistribute this project, you must make it clear that your version is unofficial unless you have written permission to state otherwise. If your distribution is materially modified, use your own product name and branding.
You may provide consulting, hosting, integration, support, migration, and other
commercial services related to this project. You may also truthfully describe
those services as relating to MrWhoOidc.
You may not present those services as the official MrWhoOidc offering unless
you have written permission.
All trademark rights in the MrWhoOidc name, logos, and brand assets are
reserved, except for the limited descriptive uses allowed by this policy.
Questions about permission requests should be directed to the project owner.