Follow-up Comment #27, task #16067 (project administration): As escalating this issue has shown (it would be great if the escalation process was documented and transparent, let's work on that later), the Dezyne sources are compliant with the requirements for copyright and licensing.
Please approve the Dezyne package to be hosted on savannah: https://savannah.nongnu.org/task/?func=detailitem&item_id=16067#votes Some background and rationale: The approval process should establish if the submitter of a package is willing to make any effort. If they are, the most egregious issues should be pointed out and corrected. Let minor stuff be fine, maybe point it out. Lack of license, lack of _clear_ liccense, license problems are most important. In general, regular source files should have copyright headers. Such problems were pointed out (thank you!!) and corrected in the first few messages. There it should have stopped. While all source code in the Dezyne package comes with copyright and license headers, the source tarball does include some ASCII files without individual copyright and license headers. That is OK; for data files or included snippets we need to strike a balance between the effort involved of adding headers and the triviality of the data. Adding a header to such files would be _very_ inconvenient and is unnecessary. A README file is used to explain the copyright and license status of such files. Also, one or two disputable cases are not enough to disqualify a package, especially if the author's intentions are reasonably clear. Of course, if a header can be added without any complications, that should always be preferred and we should ask the author to do so. That happened in the first few messages in this thread. The detais below should not be necessary, this has been almost discussed "to death" in this task. Anyway: * Test baseline data: test/all/<test>/baseline/* These be generated by running "test/bin/update.sh" (to be distributed, only in git right now). Because these baseline files are trivial and moreover can be generated automatically. * Input trace data test/all/<test>/trace The amount of actual information in that is so little that they are trivial for copyright. Also, these can be generated by running "dzn verify" or "dzn traces". The file "test/all/README" explains the license for this test data to be CC0-1.0. * Dezyne and gerenated .texi snippets included in the manual: doc/examples/*.dzn doc/parse/*.dzn doc/parse/*.texi doc/semantics/*.dzn These file are a necessary part of the manual and thus follow the copyright of the manual. On top of that, these doc/examples/README doc/parse/README doc/semantics/README README files explain their copyright and license. That's it, thank you for reading this far. After approving Dezyne, let's make sure that the maintainer's guidelines and approval process are documented better to reflect this, and make for a more welcoming and pleasant experience for newcomers, and less frustrating work for the evaluators! Greetings, Janneke _______________________________________________________ Reply to this item at: <https://savannah.nongnu.org/task/?16067> _______________________________________________ Message sent via Savannah https://savannah.nongnu.org/