[task #16067] Submission of Dezyne

[Jan Nieuwenhuizen]

Follow-up Comment #6, task #16067 (project administration):

```
Ineiev writes:

> Follow-up Comment #5, task #16067 (project administration):
>
> [comment #4 comment #4:]
>>
>> The baseline files are generated, like so
>>
>>     ./pre-inst-env dzn -v verify test/all/Alarm/Alarm.dzn \
>>        > test/all/Alarm/baseline/verify/Alarm \
>>        2> test/all/Alarm/baseline/verify/Alarm.stderr
>
> That doesn't make them uncopyrightable: if I generate an ASCII art file from
a
> bronze statue, the result will be a derived work and inherit the copyright
of
> the original picture; the fact that it's machine-readable mustn't
> matter---after all, any file is machine-readable (did you mean something
> else?).

I wholeheartedly agree that we must reduce ambiguity and minimize the
risk of error thereby mitigating the risk of legal exposure. At the
same time this risk -- a product of likelyhood and impact -- has to be
weighed against the effort involved.  I struggle to find a
satisfactory solution for this.  I have asked some other free software
developers and have looked for inspiration in other GNU
projects. These are my findings:

GAWK and SED use generated ASCII output in a tree directory structure,
without individual copyright/licence headers:

    https://git.savannah.gnu.org/cgit/gawk.git/tree/test/badargs.ok

Gawk does have the README in the same directory but it does not
mention all ~1000 files explicitly.

    https://git.savannah.gnu.org/cgit/gawk.git/tree/test/README

SED does not have a README in their test baseline directory and
depends on a higher level README, like Dezyne does right now:

    https://git.savannah.gnu.org/cgit/sed.git/tree/testsuite/8bit.good

GCC and GLIBC use an approach that is even more similar to Dezyne, no
copyrigt/licence header on any of their test baseline data, see e.g.,

   
https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=fixincludes/tests/base/bits/fenv.h
    https://ftp.gnu.org/pub/gnu/gcc/gcc-11.2.0/gcc-11.2.0.tar.gz
      gcc-11.2.0/fixincludes/tests/base/bits/fenv.h

   
https://sourceware.org/git/?p=glibc.git;a=blob;f=iconvdata/testdata/ANSI_X3.4-1968
    https://ftp.gnu.org/pub/gnu/glibc/glibc-2.34.tar.gz
      glibc-2.34/iconvdata/testdata/ANSI_X3.4-1968

and no README in every individual directory that mentions every file
explicitly.

After seeing these examples, I fail to see why the README

    dezyne-2.14.0.rc2.10-c7b90/test/all/README

in

    https://savannah.nongnu.org/task/download.php?file_id=52258

that states it holds for all subdirectories, does not adequately
address all our collective needs.

Greetings,
Janneke
```

    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/task/?16067>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/