| 1 |
Hi guys, |
| 2 |
I'm still on this list. You can remove me if you want, though. (If you're |
| 3 |
going to, please send me a |
| 4 |
courtesy email to let me know when I've been bumped) |
| 5 |
My advice is to define a clear goal. What are you trying to accomplish? |
| 6 |
Then, talk to your lawyers about |
| 7 |
some practical steps you can take to get as close to this goal as you can. |
| 8 |
Your lawyers can help you |
| 9 |
to determine what tradeoffs, if any, should be considered. |
| 10 |
You might also want to ask your lawyers their opinion about how important |
| 11 |
they think this copyright |
| 12 |
issue actually is. If it's very important, it might be worthwhile upsetting |
| 13 |
and potentially losing some |
| 14 |
developers to fix it. If it isn't that important, then it might not be. |
| 15 |
Maybe there are some key areas that |
| 16 |
you could straighten out more easily (like the Portage code itself) and then |
| 17 |
others you could at least |
| 18 |
temporarily ignore due to their complexity. I'm thinking of the actual |
| 19 |
ebuilds being a very complex issue. |
| 20 |
Which is more likely to be ripped off? This should all factor into your |
| 21 |
plan. |
| 22 |
I have tried to tackle this issue in the past, and it is harder than it |
| 23 |
looks. I think I would have been more |
| 24 |
successful if I had tried to straighten out copyrights for some key areas of |
| 25 |
Gentoo rather than try to tackle |
| 26 |
everything at once. Ebuilds are particularly thorny because so many people |
| 27 |
have touched them. |
| 28 |
If fixing all the ebuilds is an impossible goal, then maybe focus on the |
| 29 |
possible instead? |
| 30 |
I hope you can find a good solution. If you're ever in need of any |
| 31 |
additional paperwork from me, please |
| 32 |
let me know. |
| 33 |
-Daniel |
| 34 |
On 6/27/05, Donnie Berkholz <spyderous@g.o> wrote: |
| 35 |
> |
| 36 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 37 |
> Hash: SHA1 |
| 38 |
> |
| 39 |
> Deedra Waters wrote: |
| 40 |
> > I'd suggest the license. I suspect that as long as the terms are right, |
| 41 |
> > that people won't have problems with the license. Trying to maintain |
| 42 |
> > both a copyright, and a license would cause a lot of problems, and a |
| 43 |
> > copyright is much harder to handle since we would have to get anyone |
| 44 |
> > under 18 to get their parents to sign the thing etc etc etc. |
| 45 |
> |
| 46 |
> People under 18 can't consent to a license any more than an assignment, |
| 47 |
> so I don't understand your last point. But yes, maintaining both would |
| 48 |
> be more work. The question is: Is it worth it? |
| 49 |
> |
| 50 |
> Thanks, |
| 51 |
> Donnie |
| 52 |
> -----BEGIN PGP SIGNATURE----- |
| 53 |
> Version: GnuPG v1.4.1 (GNU/Linux) |
| 54 |
> |
| 55 |
> iD8DBQFCwMO0XVaO67S1rtsRAk1BAKDgLzs1y0SOkNO2ThVfnMbs5nBEXwCgjFmv |
| 56 |
> ZQB0X4QB6xceRMVCzjggbxw= |
| 57 |
> =MyVE |
| 58 |
> -----END PGP SIGNATURE----- |
| 59 |
> -- |
| 60 |
> gentoo-trustees@g.o mailing list |
| 61 |
> |
| 62 |
> |
Archives