public inbox for gentoo-trustees@lists.gentoo.org
 help / color / mirror / Atom feed
From: Deedra Waters <dmwaters@gentoo.org>
To: gentoo-trustees@lists.gentoo.org
Subject: Re: [gentoo-trustees] copyright transfer agreement
Date: Tue, 12 Apr 2005 12:03:10 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0504121200130.14978@shell.osuosl.org> (raw)
In-Reply-To: <20050412183444.GW23529@bmb244.uth.tmc.edu>

ok.... We're going to have a document that transfers "everything" from
daniel to us. that's one doc....
This is what [Redacted] and i had been working on, which is why I wanted
the list of "everything" that gentoo technologies is signing over to us.
I didn't even think about equipment in that list, but if there's infra
stuff that he owns, then that needs to be transfered from him to us as
well. On the other hand if he's already given us the equipment, then we
probably don't need to worry about it.



another doc is to write up a copyright assignment or what ever the heck
we decide on, and have that.
On Tue, 12 Apr 2005, Grant Goodyear wrote:

> Date: Tue, 12 Apr 2005 13:34:44 -0500
> From: Grant Goodyear <g2boojum@gentoo.org>
> Reply-To: gentoo-trustees@lists.gentoo.org
> To: gentoo-trustees@lists.gentoo.org
> Subject: Re: [gentoo-trustees] copyright transfer agreement
>
> Deedra Waters wrote: [Tue Apr 12 2005, 01:16:17PM CDT]
> > Grant, the equiptment must be included as well, since this doc will
> > transfer "everything"
>
> Why do you say that?  I can't see where in the text I have either
> explicitly or implicitly suggested that more than copyrights and
> trademarks are transferred?  Or are you saying that we _should_ transfer
> everything at one time?  If that's the case, is it something that we've
> already discussed and that I missed?
>
> -g2boojum-
>

-- 
Deedra Waters - Gentoo developer relations, accessibility and infrastructure -
dmwaters@gentoo.org
Gentoo linux: http://www.gentoo.org

--
gentoo-trustees@gentoo.org mailing list


  reply	other threads:[~2005-04-12 19:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 17:02 [gentoo-trustees] copyright transfer agreement Grant Goodyear
2005-04-12 17:07 ` Corey Shields
2005-04-12 17:18   ` Grant Goodyear
2005-04-12 17:35     ` Paul de Vrieze
2005-04-12 18:16     ` Deedra Waters
2005-04-12 18:34       ` Grant Goodyear
2005-04-12 19:03         ` Deedra Waters [this message]
2005-04-12 19:12           ` Corey Shields
2005-04-12 19:19             ` Deedra Waters
2005-04-12 19:32               ` Corey Shields
2005-04-12 19:47                 ` Grant Goodyear
2005-04-13  7:44               ` Sven Vermeulen
2005-04-12 19:12           ` Paul de Vrieze
2005-04-12 19:29             ` Daniel Robbins
2005-04-12 19:52 ` Grant Goodyear
2005-04-12 19:57   ` Deedra Waters
2005-04-12 20:20     ` Grant Goodyear
2005-04-12 20:29       ` Paul de Vrieze
2005-04-12 21:17         ` Deedra Waters
2005-04-12 21:20           ` Daniel Robbins
2005-04-12 21:34             ` Corey Shields
2005-04-12 20:27     ` Daniel Robbins
2005-04-12 20:11 ` Grant Goodyear
2005-04-13  7:48 ` Sven Vermeulen

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=Pine.LNX.4.58.0504121200130.14978@shell.osuosl.org \
    --to=dmwaters@gentoo.org \
    --cc=gentoo-trustees@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox