From: Daniel Robbins <drobbins.daniel@gmail.com>
To: Donnie Berkholz <spyderous@gentoo.org>
Cc: Deedra Waters <dmwaters@gentoo.org>,
Sven Vermeulen <swift@gentoo.org>,
gentoo-trustees@lists.gentoo.org
Subject: Re: [gentoo-trustees] copyright stuff
Date: Mon, 27 Jun 2005 22:42:37 -0700 [thread overview]
Message-ID: <226689f10506272242c1330f7@mail.gmail.com> (raw)
In-Reply-To: <42C0C3B4.7070703@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2619 bytes --]
Hi guys,
I'm still on this list. You can remove me if you want, though. (If you're
going to, please send me a
courtesy email to let me know when I've been bumped)
My advice is to define a clear goal. What are you trying to accomplish?
Then, talk to your lawyers about
some practical steps you can take to get as close to this goal as you can.
Your lawyers can help you
to determine what tradeoffs, if any, should be considered.
You might also want to ask your lawyers their opinion about how important
they think this copyright
issue actually is. If it's very important, it might be worthwhile upsetting
and potentially losing some
developers to fix it. If it isn't that important, then it might not be.
Maybe there are some key areas that
you could straighten out more easily (like the Portage code itself) and then
others you could at least
temporarily ignore due to their complexity. I'm thinking of the actual
ebuilds being a very complex issue.
Which is more likely to be ripped off? This should all factor into your
plan.
I have tried to tackle this issue in the past, and it is harder than it
looks. I think I would have been more
successful if I had tried to straighten out copyrights for some key areas of
Gentoo rather than try to tackle
everything at once. Ebuilds are particularly thorny because so many people
have touched them.
If fixing all the ebuilds is an impossible goal, then maybe focus on the
possible instead?
I hope you can find a good solution. If you're ever in need of any
additional paperwork from me, please
let me know.
-Daniel
On 6/27/05, Donnie Berkholz <spyderous@gentoo.org> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Deedra Waters wrote:
> > I'd suggest the license. I suspect that as long as the terms are right,
> > that people won't have problems with the license. Trying to maintain
> > both a copyright, and a license would cause a lot of problems, and a
> > copyright is much harder to handle since we would have to get anyone
> > under 18 to get their parents to sign the thing etc etc etc.
>
> People under 18 can't consent to a license any more than an assignment,
> so I don't understand your last point. But yes, maintaining both would
> be more work. The question is: Is it worth it?
>
> Thanks,
> Donnie
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFCwMO0XVaO67S1rtsRAk1BAKDgLzs1y0SOkNO2ThVfnMbs5nBEXwCgjFmv
> ZQB0X4QB6xceRMVCzjggbxw=
> =MyVE
> -----END PGP SIGNATURE-----
> --
> gentoo-trustees@gentoo.org mailing list
>
>
[-- Attachment #2: Type: text/html, Size: 3316 bytes --]
next prev parent reply other threads:[~2005-06-28 5:42 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
2005-06-28 3:03 ` Deedra Waters
2005-06-28 3:27 ` Donnie Berkholz
2005-06-28 5:42 ` Daniel Robbins [this message]
-- 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=226689f10506272242c1330f7@mail.gmail.com \
--to=drobbins.daniel@gmail.com \
--cc=dmwaters@gentoo.org \
--cc=gentoo-trustees@lists.gentoo.org \
--cc=spyderous@gentoo.org \
--cc=swift@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