Andrew N. Shrosbree wrote: > Refer to http://argus.healthopenware.org.au/ > > "The Argus Developer's Edition source code is released under the GNU General > Public License (GPL) which is a free software and copyleft licence. This > licence > allows users freedom to run, copy, distribute, study, change and improve the > software. In using this software or exercising these rights it is implied > that > you have read and accepted the conditions of the GNU GPL licence which can be > found at: http://www.gnu.org/licenses/gpl.html.";
Yes, but the only reasonable interpretation of the information the HOWF web site is that the GPL licensing applies only to the source code for the ancient version of Argus available via CVS from the HOWF site itself. There is no mention on the HOWF site of the SVN repository on the ArguSConnect web site containing (presumably, but there is no unversioning information, so it is hard to tell) more recent source code. Nor is there any reference in that SVN repository to the GPL or to HOWF. If ArgusConnect really want their product to be considered as open source, with all of the positive associations that brings, then it has to invest a small amount of effort in attending to these matters - about 30 minutes work, I'd estimate, to add a README, VERSION and LICENSING files to the ArgusConnect SVN repository. Adding license and version headers to each of the source code files contained in that repository would be good practice, but is not essential. Or, if ArgusConnect employees do not consider it as part of their job description to do such work (and at least one ArgusConnect employee clearly doesn't), then HOWF should organise for someone to transfer a copy of the recent Argus source code to the HOWF web site and create the abovementioned files. I dare say someone would volunteer to do it provided that appropriate access to the necessary resources can be provided. But even paying someone for the hour or two of work involved should be possible for HOWF. There is a lot of goodwill toward ArgusConnect because of its open source policy, but a very small amount of effort is required on the part of ArgusConnect and/or HOWF to these operational matters in order to maintain that goodwill. Tim C > Tim Churches wrote: >> Andrew N. Shrosbree wrote: >> >>> Ian, >>> >>> The code won't just "appear". You must go to >>> http://www.argusconnect.com.au/index/documentation >>> and look for "Subversion access URL" . >>> ;-) >>> >> >> There doesn't seem to be any files in that SVN repository which indicate >> the form of licensing of the code, nor even its version number, and very >> surprising, there are no copyright headers in any of the source code >> files. Sloppy practice if you are putting source code out there on the >> Web - its a jungle out there. >> >> Or maybe I just overlooked the files. >> >> Tim C >> _______________________________________________ >> Gpcg_talk mailing list >> [email protected] >> http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk >> >> > > -- > Andrew N. Shrosbree B.Sc, B.Ec > Technical Director > ArgusConnect Pty Ltd > http://www.argusconnect.com.au > Mob: +61 (0)415 645 291 > > Skype: andrewshroz > > _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
