From: Nicholas Jones <carpaski@gentoo.org>
To: gentoo-trustees@lists.gentoo.org
Subject: Re: [gentoo-trustees] Where to go now for copyright discussions
Date: Wed, 13 Apr 2005 14:33:33 -0400 [thread overview]
Message-ID: <20050413183333.GA6923@twobit.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0504130603530.14978@shell.osuosl.org>
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
> the rest of the trustees decide wether they want a copyright assignment
> or not. So far we've got 2 against, 1 for. we need 7 for a decision.
I'm still interested in hearing [Redacted]'s research/position on
the fourth proposed option. I'm in favor of copyright assignment,
or at least "Owner AND/OR Foundation" enforcement capabilities,
if the fourth option isn't viable.
Option four seemed to be the best fit... Just not proven useful.
I'd foresee a lot less noise if it proved adequate.
--NJ
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-13 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 8:47 [gentoo-trustees] Where to go now for copyright discussions Sven Vermeulen
2005-04-13 13:06 ` Deedra Waters
2005-04-13 18:20 ` Corey Shields
2005-04-13 18:33 ` Nicholas Jones [this message]
2005-04-13 18:15 ` Corey Shields
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=20050413183333.GA6923@twobit.net \
--to=carpaski@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