1 |
On 10/24/15 10:49 AM, Rich Freeman wrote: |
2 |
> On Sat, Oct 24, 2015 at 10:28 AM, Anthony G. Basile |
3 |
> <basile@××××××××××××××.edu> wrote: |
4 |
>> |
5 |
>> Hence we should get legal council here. |
6 |
>> |
7 |
>> Legal council is advise on what reasons fly in the courts. |
8 |
>> |
9 |
>> I don't want to play a guessing game. Are you against getting legal advise |
10 |
>> on this question? |
11 |
>> |
12 |
> |
13 |
> Asked and answered. :) |
14 |
> |
15 |
> On Sat, Oct 24, 2015 at 10:17 AM, Rich Freeman <rich0@g.o> wrote: |
16 |
>> On Sat, Oct 24, 2015 at 9:42 AM, Anthony G. Basile |
17 |
>> <basile@××××××××××××××.edu> wrote: |
18 |
>> |
19 |
>>> It is not unreasonable to request legal council at this |
20 |
>>> point so that we are better informed. |
21 |
>> |
22 |
>> By all means do so. If there is some kind of legal precedent for any |
23 |
>> of this I'm all ears. |
24 |
> |
25 |
> I'm pretty skeptical that anything strong will be found, but I'm not |
26 |
> opposed to asking. Lawyers aren't really the last word though, and |
27 |
> they tend to be risk-averse. If we stopped distributing Gentoo |
28 |
> entirely then we'd be less likely to be sued for copyright violation, |
29 |
> for example. So, I wouldn't avoid something simply because of a |
30 |
> hypothetical risk - risk needs to be weighed against benefit. |
31 |
|
32 |
That's true, they're mostly risk adverse. But asking is good no matter |
33 |
what answer we get. These emails leave a track the we took due |
34 |
diligence. That's what's bothering me after the last committee meeting. |
35 |
We're all just bantering our opinions about and haven't sought any |
36 |
expert advice. The other avenue is FSF. |
37 |
|
38 |
> |
39 |
> On Sat, Oct 24, 2015 at 10:28 AM, Anthony G. Basile |
40 |
> <basile@××××××××××××××.edu> wrote: |
41 |
>> |
42 |
>> Contract are not just limited to software. |
43 |
>> |
44 |
> |
45 |
> I'm not sure I claimed that they are. I already said that if we were |
46 |
> spending Gentoo money on services like Github it might be more |
47 |
> problematic because arguably the contributors did not intend for the |
48 |
> money to be spent in that manner. On the other hand, contributions |
49 |
> made after we made some announcement that we're officially using |
50 |
> Github would arguably not be as much of a problem, since contributors |
51 |
> would have had access to this information before they contributed. |
52 |
> |
53 |
> In any case, I think that we should be concerned about the Social |
54 |
> Contract because that is a big part of what we're about. I suspect |
55 |
> we're already being a lot harder on ourselves than any court is likely |
56 |
> to be. Look at how a typical big US non-profit like the Red Cross |
57 |
> spends its money and try to tell me with a straight face that we're |
58 |
> doing a worse job of adhering to our mission. |
59 |
> |
60 |
|
61 |
|
62 |
-- |
63 |
Anthony G. Basile, Ph. D. |
64 |
Chair of Information Technology |
65 |
D'Youville College |
66 |
Buffalo, NY 14201 |
67 |
(716) 829-8197 |