Potential lack of corresponding source code for Cortado 0.6.0 official binaries
For the cortado-ov-stripped-0.6.0.jar binary, which is dated March 19, 2010 and which is available at the http://downloads.xiph.org/releases/cortado/ URL, it is not clear as to whether one can easily obtain the corresponding source code for the binary (such as would be required for license compliance when redistributing the binary on physical media.)
Although there is a cortado-0.6.0.tar.gz archive which is also dated March 19, 2010 and which is available at the http://downloads.xiph.org/releases/cortado/ URL, the contents of this archive do not seem to mention the Proguard software, even though the official cortado binary was supposedly processed with the Proguard software after the binary was built. As such, it seems unclear as to whether this archive file would constitute the complete corresponding source code for the official cortado-ov-stripped-0.6.0.jar binary.
At the http://git.xiph.org/?p=cortado.git;a=commit;h=d8611fc913f69fe8f25a7276c9a08c9fd4a6e726 URL, there is a "snapshot" option which, from what it appears, will download the source code in the source repository up to and including the "0.6.0" tag. Although the downloaded source includes a "cortado.proguard" file, there does not seem to be any other mention of the Proguard software, and trying to compile the source produced Cortado binaries that did not appear to have been processed with the Proguard software. (In addition, the latest entry in the "Changelog" file dated back to May 28, 2007.)
At the http://git.xiph.org/?p=cortado.git;a=commit;h=21fc8dd2cc0dc558ed44422044d3d055fe7e0114 URL, it appears than one can download a more up-to-date snapshot of the source code. As of December 1, 2010, however, the snapshot of the code does not seem to mention the Proguard software outside of the "cortado.proguard" file. (On a side note, with this soure code on the Ubuntu Linux platform with Apache Ant version 1.7.1 and javac version 1.6.0_18, it appeared that the "ant stripped" option failed to build the applets when invoked for the first time, though it worked when invoked a second time. From what one remembers, though, the binaries had not been processed with the Proguard software.)
With the source code, the "README" and "HACKING" files should mention the use of the Proguard software, as well as any additional post-processing that should be done in order to regenerate the official binaries.
If possible, the build scripts would automatically process the binaries with the Proguard software, or at the very least would mention the Proguard software (as well as any additional post-processing that should be done.)
Files that contain version histories or which refer to a date on which something was done should be updated if necessary.
It might not hurt to include copies of the GPLv2 and LGPLv2 license files in the Cortado source collection.