-
-
Notifications
You must be signed in to change notification settings - Fork 39
📝 Update Ts&Cs; Trademark costs & responsibility [due Sep 15] #271
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
Merged
Merged
Changes from all commits
Commits
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 hidden or 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 hidden or 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,89 @@ | ||
| # Trademark Management and Costs Policy | ||
|
|
||
| The Commonhaus Foundation (CF) manages all CF-owned trademarks, including registration, maintenance, and protection of these Marks. | ||
| CF coordinates these activities and establishes how related costs are handled in this policy. | ||
|
|
||
| - [Scope](#scope) | ||
| - [Responsibilities](#responsibilities) | ||
| - [Costs](#costs) | ||
| - [Covered Costs](#covered-costs) | ||
| - [Typical Costs (as of February 2025)](#typical-costs-as-of-february-2025) | ||
| - [Payment Responsibility](#payment-responsibility) | ||
| - [Coordination and Approval](#coordination-and-approval) | ||
| - [Related Policies](#related-policies) | ||
|
|
||
| ## Scope | ||
|
|
||
| This policy applies to: | ||
|
|
||
| - All CF-owned Marks, including project names, logos, and other brand elements. | ||
| - All projects under CF fiscal sponsorship. | ||
| - Any individual or organization authorized to use a CF-owned Mark. | ||
|
|
||
| ## Responsibilities | ||
|
|
||
| CF retains sole ownership of all Marks associated with its projects. | ||
| It coordinates all registration, renewal, and enforcement activities, and all trademark-related actions must be handled through CF’s designated legal or administrative contacts. | ||
|
|
||
| Projects are expected to report any potential filings, misuse, or infringement to CF and must not take independent action. | ||
| They must use Marks in compliance with the [Trademark Policy](./trademark-policy.md) and [Trademark Guidelines](./trademark-guidelines.md). | ||
|
|
||
| ## Costs | ||
|
|
||
| ### Covered Costs | ||
|
|
||
| Trademark-related costs may include: | ||
|
|
||
| - Registration and application fees. | ||
| - Renewal fees. | ||
| - Legal fees for protection and enforcement. | ||
| - Costs of monitoring for infringement. | ||
|
|
||
| ### Typical Costs (as of February 2025) | ||
|
|
||
| - **U.S. Single Trademark Registration** — $1,200 USD | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. define if that's per year or a one time fee
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not per year, but at registration time (lasts for x years). Renewal has a separate cost. |
||
| - Covers one trademark (name or logo) in one category (class) | ||
| - Additional category: +$350 USD | ||
| - **U.S. Trademark Transfer** — $350 USD | ||
| - Transfer of a single, USPTO-registered U.S. trademark to CF | ||
| - Additional trademark in same filing: +$25 USD | ||
| - **Non-U.S. Registration or Transfer** — Varies by jurisdiction | ||
| - Contact CF for a quote | ||
|
|
||
| **Disclaimer:** These amounts are typical costs based on current legal counsel rates and government fees. Actual costs may vary. CF will confirm the applicable costs during the quote process before work begins. | ||
|
|
||
| ### Payment Responsibility | ||
|
|
||
| Projects are expected to help ensure there are sufficient funds to maintain any registered trademarks associated with their work. | ||
| Trademark-related costs are normally paid from the Project’s restricted fund under its [Fiscal Sponsorship Agreement](../fiscal-sponsorship/terms-and-conditions.md). | ||
| Sponsors may also choose to cover these costs on behalf of a Project. | ||
|
|
||
| CF retains legal representation for trademark matters. | ||
yrodiere marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| The cost of ongoing legal availability (such as a standing retainer) is managed by CF, while any specific legal services beyond this baseline are treated as trademark-related costs and are charged to project funds as described above. | ||
| To reduce expenses, CF may coordinate grouped filings or renewals where practical. | ||
| CF does not ordinarily cover trademark expenses; any CF-funded costs require prior approval by the CF Council. | ||
|
|
||
| Projects must coordinate all trademark-related legal work through CF’s designated contacts. | ||
| If a Project does not ensure sufficient funds are available, CF may use its own funds to maintain a registration or may allow it to lapse, at its discretion. | ||
yrodiere marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| ## Coordination and Approval | ||
|
|
||
| All trademark-related expenses must be coordinated with CF before commitment or payment to ensure: | ||
|
|
||
| - Compliance with applicable law. | ||
| - Protection of CF’s ownership rights. | ||
| - Alignment with project and Foundation budgets. | ||
|
|
||
| Trademark legal work follows a quote process: | ||
|
|
||
| - CF will provide an estimate for the work based on its legal counsel’s rates and applicable government fees. | ||
| - The project (or its sponsor) must approve the estimated cost before work begins. | ||
| - Invoices for approved work will be charged to the project’s restricted fund or paid directly by the sponsor. | ||
| - Costs provided are estimates; actual amounts may vary. CF will confirm the final applicable costs before commitment. | ||
|
|
||
| ## Related Policies | ||
|
|
||
| - [Trademark Policy](./trademark-policy.md) | ||
| - [Trademark Guidelines](./trademark-guidelines.md) | ||
| - [Fiscal Sponsorship Agreement](../fiscal-sponsorship/terms-and-conditions.md) | ||
| - [Asset Transfer Agreement](../asset-transfer-agreement.md) | ||
This file contains hidden or 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 hidden or 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
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.
Uh oh!
There was an error while loading. Please reload this page.