| 1 |
On Wed, Feb 18, 2015 at 9:56 AM, hasufell <hasufell@g.o> wrote: |
| 2 |
> Dean Stephens: |
| 3 |
>> On 02/15/15 22:26, hasufell wrote: |
| 4 |
>>> Scripts no one can read except the team (even after being asked to |
| 5 |
>>> publish them) is by definition propriety software. It was used to |
| 6 |
>>> develop and package emul-linux-x86-* packages until this very day. |
| 7 |
>>> |
| 8 |
>> Your prose might benefit from labeling when you are using hyperbole, |
| 9 |
>> otherwise when you make factually inaccurate claims it might seem as |
| 10 |
>> though you actually believe them. |
| 11 |
>> |
| 12 |
>> In case that was unclear: while those scripts might not be formally |
| 13 |
>> published, they have been made available to people who are not on the |
| 14 |
>> team. Unless, that is, you define "the team" as anyone who has seen the |
| 15 |
>> scripts; in which case you would be trivially correct by definition. |
| 16 |
>> |
| 17 |
> |
| 18 |
> Are you saying you only share the code with your buddies? In that case, |
| 19 |
> it is against our social contract as well. |
| 20 |
|
| 21 |
Yes, fine, it is. I don't think you're making an interesting point. |
| 22 |
|
| 23 |
> Not only that, it is even a serious security problem since the developer |
| 24 |
> community doesn't know how these things are packaged and neither do the |
| 25 |
> users. |
| 26 |
|
| 27 |
There's a serious security problem if they were to release the scripts |
| 28 |
(passwords and all) right this second. |
| 29 |
|
| 30 |
There's a lack of man power and that's completely sufficient to |
| 31 |
explain why these things haven't happened. |
Archives