A comment/suggestion:
I don't know what the system is for overseeing the publication of Packages, available via pPackage Management in Revo, but we could do with a bit of quality control in the Descriptions department.
This is basically a shop window where we look for a product to fit a requirement, or maybe just where we explore and window shop. There seem to be a fair few packages where the author has not bothered to write a description of what the package actually does (eg Loginza). It seems crazy, after all the effort of creating and testing the code, to put it out there with an immediate disadvantage, to both author and potential users..
Sometimes there is just the last changelog entry in liu of a description, but this isn't really of any use.
People have to remember that good documentation is VERY important! It is the intellectual lubricant that allows averything to operate smoothly and efficiently (with reduced forum-dependency!)
Code can be brilliant, but uinless we know what it does and how it works, it will be under-used.
Is there a set of requirements that contributers have to comply with before releasing packages? Something like that would be very useful for maintaining a good level of quality and maybe a bit of standardisation too.
