Tarball not generated yet

a) yes, the problem was on your end (sort of). even though the drupal contributions CVS repository is not configured to support cvs watches, you added some to the files in your project. therefore, when people (or the packaging script) tried to check out your files, they got a completely read-only copy. so, when the packaging script ran and tried to update your .info file with the correct version info and other things it adds before creating the tarball, it couldn't write to the file. i should fix the packaging script to be more robust in this case, but it's silly to use cvs watches when the repository can't notify you of changes, anyway. it makes it more of a pain for anyone else who checks out your code and wants to modify the files to fix bugs, etc. so, i just removed the watches, re-ran the packaging script, and everything is now working (see http://drupal.org/node/143506).

b) this is not critical.

c) we generally don't like it when contributors don't work together, and fork functionality. e.g. this line from your description: The Creative Commons Lite module simplify the functionality creativecommons http://drupal.org/project/creativecommons. this just wastes development effort, makes it harder for users of drupal (who are already faced with hundreds of choices) to find and decide what to use, and makes support more difficult. can't you find a way to cooperate with the maintainers of the real creativecommons module and help make that module easier to use, if that's your goal?