1 |
You obviously didn't explicitly say that. Forgive me for the lack of sarcasm tags. |
2 |
|
3 |
Yes doing work that is inaccurate and lends to no good cause is busy work. Yes, someone would have to do it. No devs wouldn't be mandated too. |
4 |
|
5 |
And years later we still have no problems with any copyright issues. |
6 |
|
7 |
These lists are full of end of the world scenarios just like the council/trustee/foundation crap. |
8 |
|
9 |
We have issues (like taxes) and then we bikeshed it until our fingers bleed all the while *one* guy tries to save it by doing actual work. |
10 |
|
11 |
Another beautiful Gentoo day. <--- Rich, this is sarcasm. |
12 |
|
13 |
On June 16, 2018 10:39:51 PM EDT, Rich Freeman <rich0@g.o> wrote: |
14 |
>On Sat, Jun 16, 2018 at 10:17 PM Aaron Bauman <bman@g.o> wrote: |
15 |
>> |
16 |
>> So, ugh, let's not do anything and let the courts do their job then |
17 |
>if they have too? |
18 |
>> |
19 |
>> You basically just said, |
20 |
>> |
21 |
>> "Let's do some busy work that is utter shit and it's cool" |
22 |
> |
23 |
>You'll have to point out where I said that. |
24 |
> |
25 |
>The policy was written in reaction to the problems that came about |
26 |
>when copyright notices were stripped from udev code, in order to |
27 |
>comply with what was perceived to be the Gentoo policy at the time. |
28 |
>That is clearly not a good policy, and this new policy was created to |
29 |
>fix that (and bikeshedded over the following few years). |
30 |
> |
31 |
>The policy does not require anybody to do "busy work" - it just tells |
32 |
>you what to put in the copyright notice line when you're editing it. |
33 |
>You don't have to look at the notice when you're making random ebuild |
34 |
>changes. |
35 |
> |
36 |
>Rich |
37 |
|
38 |
-- |
39 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |