Skip to content
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

Logo Usage Policy needs work #263

Open
vinniefalco opened this issue Jul 19, 2024 · 2 comments
Open

Logo Usage Policy needs work #263

vinniefalco opened this issue Jul 19, 2024 · 2 comments
Assignees

Comments

@vinniefalco
Copy link
Member

The language of the logo usage policy needs work. The policy governing use of the logo in the documentation which goes into a release should be adjusted to ensure that third parties do not lose the ability to freely create derivative works which incorporate parts or all of Boost. How the logo is handled in this case needs to be well-defined.

And, this issue is appropriate for discussion of any areas of the policy, with the goal to ensure that a balance is struck between honoring the spirit of the BSL while protecting the logo from misuse.

@Lastique
Copy link
Member

I'll just reproduce here what I suggested on the ML:

On 7/19/24 01:45, Vinnie Falco wrote:

do you have any ideas which reach a balance
allowing use of the libraries without restriction while also providing
the means to discourage usage which harms the libraries?

Change the terms of use to only apply to marketing/promotional/social
uses of the brand and logo.

Explicitly state that the logo that is being distributed as part of
Boost documentation (whether online or in a package) is distributed
under BSL. Any additional restrictions or requirements in the TOU do not
apply to this use of the logo.

@vinniefalco
Copy link
Member Author

vinniefalco commented Oct 14, 2024

The trademark is going to be donated to the Boost project, and under control of the Fiscal Sponsorship Committee. The FSA can decide on a case by case basis whether to take a legal action. Logos in documentation will be uncontroversial. This solves the immediate problem, and we can revisit the usage policy later to explore improved wording (which needs the assistance of a lawyer).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Blocked
Development

No branches or pull requests

2 participants