However, the status quo is that neither the .info.tcz is included in an extension and also if any build info would be included it would need to have a very clearly distinguishable name, making it explicit that it is not addressed at every end-user as the suggested 'readme.txt' would imply.
The status quo is not forever. So, my point of view is:
- any name & folder into .tcz is OK as long as ALL info in included inside.
- any .info & . dep & build instructions, and so on, COULD be in tcz
My scenario is that I use appbrowser to read the info before try the extension. But later, I have to unnecessarily fire again the browser and connect to the internet, read the info, and search for build instructions in various places, etc.
I wonder why this waste time procedure. Even if, let say, dep file are updated, or small info changed, IMHO it is worth to have an optional folder into tcz with old bits of info about extension creation (history).
The main info will remain in specific files as dep, info, etc. But text files inside tcz will not hurt tcz size. I saw some not necessary lang, sound, image etc into tcz, more bloat than my suggested text infos.
As a general goal, I think the scripting of extension creation is the future, and for others (without willing/ knowledge/ resources, just try for fun/ benchmark etc) tcz will be the fastest solution.