1 |
On Wed, Mar 26, 2014 at 7:29 AM, Ulrich Mueller <ulm@g.o> wrote: |
2 |
> So far most license discussions took place on the licenses@g.o alias |
3 |
> which makes it impossible to trace many license related decisions. |
4 |
> This isn't in line with the Social Contract which says that "we will |
5 |
> not hide problems". |
6 |
> We have therefore created a new gentoo-licenses mailing list for |
7 |
> discussion of packages' licenses and related issues. (Thanks to the |
8 |
> Infra team for setting it up.) |
9 |
|
10 |
So, I 100% support the concept here. However, there is one potential |
11 |
wrinkle I can think of here, and I'd be interested in how other |
12 |
distros like Debian handle it. |
13 |
|
14 |
We're incorporated in the US, which is fairly well-renown for its |
15 |
"strong" IP stance and litigious culture. That actually can be a |
16 |
benefit to us since Gentoo is largely an IP-holding organization so |
17 |
holding the IP in a venue where we can actually do something about |
18 |
violations makes sense (which isn't to say there isn't benefit to |
19 |
being incorporated elsewhere). However, it is also a two-edged sword |
20 |
since accusations of infringement against us can cost us dearly in |
21 |
time and money. |
22 |
|
23 |
Is openly discussing a purported licensing problem something that |
24 |
could be considered an admission of guilt in a court of law, |
25 |
especially if officers, trustees, council members, or project leads |
26 |
(who might be construed as officially speaking for Gentoo) are |
27 |
involved in the conversation? I believe that lkml bans talk of |
28 |
patents for just this sort of reason. |
29 |
|
30 |
As I said, I'd be interested in the stance other distros take on this. |
31 |
|
32 |
Now, I don't want the solution to be "hiding problems" or not being |
33 |
open to broader participation. Maybe we just need ground rules like |
34 |
being careful not to make statements like "Gentoo is breaking the law" |
35 |
or "we are violating this license" and so on. It would be better to |
36 |
say that "we MIGHT be in violation of a license" or "somebody claims |
37 |
we are in violation of their license" or something like that. I'd |
38 |
also suggest that if anybody from Gentoo is actually contacted by a |
39 |
copyright-holder or a lawyer about a purported violation that this |
40 |
first go straight to the trustees so that they can see legal council |
41 |
before we engage in open discussion that might be more likely to end |
42 |
up being cited in court as evidence that we did or didn't handle a |
43 |
situation appropriately. |
44 |
|
45 |
After all, the only body that can actually say with certainty that |
46 |
Gentoo is or isn't breaking a law is an actual court. Anything else |
47 |
is just opinion and speculation. We should be clear that discussion |
48 |
really is just healthy debate and speculation, and in no way |
49 |
represents any kind of actionable determination on its own. This is |
50 |
why lawyers love words like "allegedly" or "purportedly" and so on - |
51 |
claims are just claims, and we can talk about them without endorsing |
52 |
them. |
53 |
|
54 |
Bottom line is that I'd especially encourage anybody who is in a role |
55 |
like an officer/trustee to just be careful about the language we use. |
56 |
Sometimes I've seen in private conversation statements like "we're |
57 |
technically violating the law" and such - I understand the spirit (we |
58 |
DO want to follow the law), but statements like this said with the |
59 |
best of intentions can end up being used against us. We can just as |
60 |
seriously consider the matter while saying things like "it is possible |
61 |
that a court might think that this is in violation of the law" and |
62 |
being clear that our speculation/opinion is just that. |
63 |
|
64 |
Just my two cents. I do fully support making this more open to the community. |
65 |
|
66 |
Rich |