git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Dov Grobgeld <dov.grobgeld@gmail.com>
Cc: Nikita Malikov <nikitam@devart.com>,
	Konstantin Khomoutov <kostix+git@007spb.ru>,
	git@vger.kernel.org
Subject: Re: Partnership with Git
Date: Tue, 21 Feb 2017 11:04:09 -0800	[thread overview]
Message-ID: <xmqqy3wzfjrq.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CA++fsGEvYPeP1UYniHF7OnowTH8-UeH3Kwe2KqaYMRouWVzEbg@mail.gmail.com> (Dov Grobgeld's message of "Tue, 21 Feb 2017 17:04:21 +0200")

Dov Grobgeld <dov.grobgeld@gmail.com> writes:

> As git is free software, you are free to use it in any way you see fit, as
> long as you adhere to its licensing terms, and to the copyright
> restrictions on using the term "git". Thus there is no need to ask
> permission and there does not on the git side exist any entity interested
> in "cross marketing activities".

s/copyright/trademark/.  

As one of Software Freedom Conservancy projects, I suspect that the
Git PLC git@sfconservancy.org may be the closest to such "entity"
that represents open source Git community's interest to the outside
world with help from lawyers.

Not that I think Git PLC is interested in such a cross marketting
arrangement, but if Devart wants to advertise on their webpage
saying "we support Git by making contributions to SFC" or something
like that, they are the people to talk to.

  reply	other threads:[~2017-02-21 19:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 11:21 Partnership with Git Nikita Malikov
2017-02-21 12:22 ` Konstantin Khomoutov
2017-02-21 14:08   ` Nikita Malikov
2017-02-21 15:04     ` Dov Grobgeld
2017-02-21 19:04       ` Junio C Hamano [this message]
2017-02-22  9:06         ` Nikita Malikov

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqy3wzfjrq.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=dov.grobgeld@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kostix+git@007spb.ru \
    --cc=nikitam@devart.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://80x24.org/mirrors/git.git

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).