mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Phillip Wood <>
To: Christian Couder <>, git <>
Subject: Re: Handling the Git trademark
Date: Tue, 20 Sep 2022 09:38:53 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Christian

On 13/09/2022 13:11, Christian Couder wrote:
> Hi everyone,
> The Git PLC (Project Leadership Committee) is responsible for handling
> the "Git" trademark and the Git logo with help from the Software
> Freedom Conservancy. And we would like at this point to report about
> how we have been handling it, and to open the conversation about this
> subject.
> We have a web page about our trademark policy on
> There, we list our guidelines for
> others who would like to use our "Git" trademark. Unfortunately a
> number of people don't respect our guidelines and use the trademark
> without asking us first (sometimes in ways that we might not like).
> If we don't enforce our trademark, there is a risk of us losing any
> right to it. So far we have tried to enforce it, especially in cases
> where people want to register a name based on it.
> The issue we have with enforcing the Git trademark is that we don't
> have much resources to enforce it. And in general we want to avoid
> spending time and money enforcing our mark in all possible instances.
> Legal discussions, going to court, etc can be very time and money
> consuming, and we would prefer doing more productive things with our
> resources instead.
> So, as much as possible, we don't want to take legal action. For
> example, we would much prefer to respond to a disagreeable use of our
> mark by first contacting the party and asking politely for them to
> change their use. Usually this is sufficient to deter infringing uses
> of our mark.
> We would be Ok if necessary to publicly say that for example one
> company is using our trademark in a way we don't like. We think that
> the threat of us doing that (if the company doesn't agree to change
> the way they use it when we ask politely) is in most cases enough to
> deter people from using it.
> This way of handling issues has worked well so far. The reason we
> think it works well, is that people think about the "Git" name as very
> cool, and that's why they want to use it in their product or company
> names. If the Git project would say that it doesn't like the way this
> company is using the Git trademark, it would likely create some bad
> buzz about that company and would go completely against their goal of
> being perceived as cool.
> Now we cannot be sure that this will always be enough to enforce it in
> the future. We might have to go to court in some cases. Also we still
> spend some time on this, so another possibility would be to stop
> enforcing the trademark and the logo altogether.
> We also would like to thank the Conservancy and the layers they have
> hired for all the information, help, advice and guidance they have
> provided on this.
> Now we are open to your thoughts about this.

Thanks for taking the time to start a discussion on this. My immediate 
reaction is that it would be a shame to lose control of the trademark by 
not enforcing it. If it is taking up too much of the leadership 
committee's time perhaps we could consider asking for more volunteers to 
handle some of the load. Would a few people volunteering a couple of 
hours a month make a useful difference?

One other thought is that there are a number of companies which use 
"git" in their name that benefit indirectly from the git project 
enforcing the trademark and thereby ensuring the name "git" is trusted. 
If we were ever in the unfortunate position of having to take time 
consuming (and presumably costly) legal action perhaps we could approach 
them for support?

Thank you to all the leadership committee for the time you spend 
handling these administrative issues.


> Thanks,
> Christian for the Git PLC

  reply	other threads:[~2022-09-20  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 12:11 Handling the Git trademark Christian Couder
2022-09-20  8:38 ` Phillip Wood [this message]
2022-09-26 15:25   ` Christian Couder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).