You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 31, 2018. It is now read-only.
If you want to grow this new community over the long term, the project needs a trademark policy for ayo.js and whatever logos you come up with. Having a policy doesn't prevent all abuse of your project brand, but it helps reduce it and gives you the start of some tools to protect the name in the future.
I'm happy to provide advice to the core team/committee/board here or elsewhere, if you can explain the long-term goals of how you're planning to run the project. You need to match a trademark policy with how you want the community and corporations to use your brand.
If you want to grow this new community over the long term, the project needs a trademark policy for ayo.js and whatever logos you come up with. Having a policy doesn't prevent all abuse of your project brand, but it helps reduce it and gives you the start of some tools to protect the name in the future.
Useful background on FOSS trademarks:
I'm happy to provide advice to the core team/committee/board here or elsewhere, if you can explain the long-term goals of how you're planning to run the project. You need to match a trademark policy with how you want the community and corporations to use your brand.
Dependency: #2
The text was updated successfully, but these errors were encountered: