All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bradley M. Kuhn" <bkuhn@sfconservancy.org>
To: Jeff King <peff@peff.net>
Cc: Tait <git.git@t41t.com>, git@vger.kernel.org
Subject: Re: git as an sfc member project
Date: Tue, 02 Nov 2010 19:03:55 -0400	[thread overview]
Message-ID: <87wrovpbtw.fsf@ebb.org> (raw)
In-Reply-To: <20101027110807.GB3995@sigill.intra.peff.net> (Jeff King's message of "Wed, 27 Oct 2010 04:08:07 -0700")

>> > The draft agreement is here:
>> >   http://peff.net/git-sponsorship-agreement.pdf

> On Wed, Oct 27, 2010 at 12:03:48AM -0700, Tait wrote:

>> This agreement brings up one concern for me. It would make officially
>> make git a United States project based out of New York, and therefore
>> subject to the laws of New York and the United States. Among whatever
>> other laws apply, will be export restrictions and patent law. I don't
>> know whether any part(s) of git would be a concern under those laws
>> (and I haven't needed to care, until now). Is legal advice for issues
>> like this part of the services SFC can provide?

Jeff King wrote on the 27th of October:

> I am not sure that joining the SFC is going to make any difference
> with respect to those things. Developers and distributors of the
> software in the United States were already subject to such laws, and I
> don't see how our dealing with the SFC would create any special
> obligation for those outside the US. In particular, it seems to me
> that git as a legal entity signing this agreement as the SFC (which
> legally is really just an agreement between the SFC and a few members
> of the project) is different from git as a community of individuals
> who happen to contribute and distribute code.  SFC will not own any
> copyrights, nor take any responsibility for distribution.

I believe what Jeff says is basically correct.  The "Git Project" will
be part of a non-profit in New York, and it's true that the Git Project
could be therefore be subject to the laws of New York.  However, it
isn't that much different of some Git developers being in New York and
being subject thereto.  Developers outside the USA continue to operate
as volunteers for the project and aren't impacted any more than they
already are participating in an unincorporated project.

Nevertheless, I'm going to check in with Conservancy's lawyers to verify
there are no serious disadvantages to Git joining a USA non-profit that
weren't already the case anyway since some developers are in the USA
anyway.  I'll respond back when I hear from them.
-- 
Bradley M. Kuhn, Executive Director, Software Freedom Conservancy

  reply	other threads:[~2010-11-02 23:15 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 18:30 git as an sfc member project Jeff King
2010-10-22 19:19 ` Shawn Pearce
2010-10-22 19:35   ` Jeff King
2010-10-22 20:06     ` Shawn Pearce
2010-10-22 20:59       ` Sverre Rabbelier
2010-10-22 21:48   ` Junio C Hamano
2010-10-22 22:59   ` Junio C Hamano
2010-10-22 23:18     ` Jeff King
2010-10-22 23:21       ` Brandon Casey
2010-10-22 23:26         ` Junio C Hamano
     [not found]         ` <hh0bQq8TcM0saDTuJo6qVdOMgn-14aysvhF_S70syB678Of7zQOsY9jLajG2WpeGXid8jtG4kVA@cipher.nrlssc.navy.mil>
2010-10-23  0:09           ` Brandon Casey
2010-10-23  1:30             ` Brandon Casey
2010-10-23 22:48               ` Brandon Casey
2010-10-22 23:22       ` Junio C Hamano
2010-10-23 11:52       ` Ævar Arnfjörð Bjarmason
2010-10-23 13:39         ` Jeff King
2010-10-23 16:03           ` A Large Angry SCM
2010-10-26 22:39 ` Jeff King
2010-10-27  7:03 ` Tait
2010-10-27 11:08   ` Jeff King
2010-11-02 23:03     ` Bradley M. Kuhn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-02-24 15:44 Jeff King
2010-02-24 16:07 ` Jakub Narebski
2010-02-26 12:39   ` Jeff King
2010-02-26 15:56     ` Jakub Narebski
2010-03-01 10:58       ` Jeff King
2010-02-24 16:22 ` Shawn O. Pearce
2010-02-26 12:49   ` Jeff King
2010-02-24 17:44 ` Christian Couder
2010-02-26 12:25   ` Jeff King
2010-02-24 18:12 ` Junio C Hamano
2010-02-26 12:29   ` Jeff King
2010-02-26 12:37     ` Jeff King
2010-02-26 12:59 ` Jeff King
2010-02-26 13:14   ` Julian Phillips
2010-03-01 10:53     ` Jeff King
2010-02-27  6:35   ` Eric Wong

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

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

  git send-email \
    --in-reply-to=87wrovpbtw.fsf@ebb.org \
    --to=bkuhn@sfconservancy.org \
    --cc=git.git@t41t.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.