public inbox for gentoo-trustees@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <spyderous@gentoo.org>
To: Kumba <kumba@gentoo.org>
Cc: gentoo-trustees@lists.gentoo.org
Subject: Re: [gentoo-trustees] copyright stuff
Date: Mon, 27 Jun 2005 20:26:58 -0700	[thread overview]
Message-ID: <42C0C382.7010903@gentoo.org> (raw)
In-Reply-To: <42C0B6ED.6010808@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kumba wrote:
> Call me the anarchist of the pack, but what are other organizations
> doing, like *BSD, debian, or even other open-sourced projects as far as
> copyrights go?  Why not just keep it simple and adopt the mechanism used
> by the upstream linux kernel team (which based on gregkh's description,
> seems to fit us the best, imho).

The reason I suggested this dual solution is that this is how the FSF
does it, although I'm not saying it's perfect. And while it is a bit
more maintenance, it seems like it offers the most benefits for both
sides. The foundation gets to protect everything that people are willing
to give it, and people who are unwilling to assign the copyright bear
the brunt of any infringements personally.

> As it currently stands, it seems every idea proposed so far has a flaw
> or flaw(s) that prohibits, limits, excludes, or annoys one or more of
> our devs. Surely this situtation, or a variant, has been tackled before,
> so I'm sure somewhere out there, there is something workable for us
> (possibly with minor modifications).

What's the flaw with this, again? I must've missed it.

Thanks,
Donnie
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCwMOBXVaO67S1rtsRAu4DAJ0XtGbI15dI17JazPwEuwx2gqO4owCdGPGN
MLsWXJT0aUGncLxzLZFqxRI=
=S9cF
-----END PGP SIGNATURE-----
-- 
gentoo-trustees@gentoo.org mailing list



  reply	other threads:[~2005-06-28  3:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27 19:37 [gentoo-trustees] copyright stuff Deedra Waters
2005-06-27 20:17 ` Sven Vermeulen
2005-06-27 20:21   ` Deedra Waters
2005-06-27 21:13     ` Sven Vermeulen
2005-06-28  1:57   ` Donnie Berkholz
2005-06-28  2:16     ` Donnie Berkholz
2005-06-28  2:29       ` Corey Shields
2005-06-28  2:33     ` Kumba
2005-06-28  3:26       ` Donnie Berkholz [this message]
2005-06-28  3:03     ` Deedra Waters
2005-06-28  3:27       ` Donnie Berkholz
2005-06-28  5:42         ` Daniel Robbins
  -- strict thread matches above, loose matches on Subject: below --
2005-07-12 21:58 Deedra Waters
2005-07-13 10:43 ` Sven Vermeulen
2005-07-13 11:33 ` Donnie Berkholz
2005-07-13 15:41   ` Deedra Waters
2005-07-13 16:30 ` Grant Goodyear
2005-07-13 16:31 ` Grant Goodyear

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=42C0C382.7010903@gentoo.org \
    --to=spyderous@gentoo.org \
    --cc=gentoo-trustees@lists.gentoo.org \
    --cc=kumba@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