1 |
On Sun, Apr 7, 2013 at 10:00 AM, Tom Wijsman <TomWij@g.o> wrote: |
2 |
> On Sun, 7 Apr 2013 03:34:05 -0600 |
3 |
> Ryan Hill <dirtyepic@g.o> wrote: |
4 |
> |
5 |
>> On Sun, 7 Apr 2013 08:27:18 +0100 |
6 |
>> Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
7 |
>> |
8 |
>> Sure, I suppose if we were trying to break everything all at once |
9 |
>> that would be the most efficient way to go about it. |
10 |
> |
11 |
> What's stopping you? An overlay is perfect for this. |
12 |
|
13 |
I imagine they could ask you the exact same thing. Again, this is a |
14 |
volunteer project. |
15 |
|
16 |
If you don't like how something works, volunteer! |
17 |
|
18 |
I'll let the toolchain maintainers speak for themselves though. From |
19 |
what I'm reading here it sounds like we should be happy to have a |
20 |
toolchain at all. If people want them to do more than they're already |
21 |
doing somebody will have to step up and help them do it. |
22 |
|
23 |
Simply writing a policy and getting the council to approve it won't |
24 |
make the work happen. I'm working on a policy for copyright |
25 |
attribution/assignment/etc and one of my biggest concerns is how easy |
26 |
it will be to comply with. If it isn't easy, then either it won't be |
27 |
obeyed, or work that could otherwise get done won't get done because |
28 |
everybody is spending all their time checking copyright notices. I'd |
29 |
even prefer a suboptimal policy that gets followed to a "perfect" one |
30 |
that gets ignored. |
31 |
|
32 |
Rich |