... add a license.txt and license in all your source modules ...-f0dder
a) one could interprete that, as if I would have intended the source to be seen by a lot of people;
b) I use to comment my sources using my own (German) language, not willing to translate it into every other relevant language;
... mouser has my full confidence ...-f0dder
that is fine, but where in the rules could I find the names of all people, who will be authorized to look into contributed program's sources? And why is in not sufficient to simply verify their compilability?
I still cannot see a need to look inside the sources. Contributors would be well known namely. Including bad code thus will not be possible anonymously. Instead object / runtime code easily could be qualified as been produced using BC Builder or BDS or not. Maybe elected winners' programs' sources could be revisited by a neutral trustee, whether they would compile and link with a Borland C++ Builder or not and be identical to the entered executables.
Maybe I have got the wrong impression from some postings, that the contest seems to be interested more in sources than in resulting programs. But there will be of course a lot of people who do not care at all about that question.
...what i meant about sandbox is that we might accept entries without sourcecode, and do testing within a sandbox, with the understanding that before we sanctioned official winners we'd have to be able to compile it ourselves or otherwise satisfy ourselves that the code was safe.-mouser
If after such a verification all transferred source code would be deleted and the people involved would be made known to the programmer it could be an acceptable compromise.
Regards, Reinhard.