I just came across this post which I thought was interesting. He talks about the old aphorism, Keep It Simple, Stupid and how it applied to a PowerCLI versus shell script example that he ran into.
http://www.dailyhypervisor.com/2009/07/27/keep-it-simple-stupid-registering-unregistered-vms/
What I took from this was that we need a Search-Datastore and Register-VM cmdlets. 
But also, greater exposure to third-party and community scripts and modules such as the VI Toolkit Extensions (http://vitoolkitextensions.codeplex.com/).
What do you think?
[vExpert|http://www.vmware.com/communities/vexpert/], PowerShell MVP, VI Toolkit forum moderator
Author of the book: Managing VMware Infrastructure with PowerShell
Co-Host, PowerScripting Podcast (http://powerscripting.net)
Follow me on Twitter: @halr9000
Couldn't agree more.
The visibility is, IMHO, primarily hampered by the "poor" search facilities offered in the VMTN Communities.
The lack of a decent tagging/indexing system doesn't help either.
The new Developer: Sample Code could help, but the problem here is that the user/author needs to take additional action. And duplication of effort doesn't go well with admins and programmers 
This should IMHO be (partially) automated.
Why not provide, for example, an option on threads where the users could select "Add to Sample Code".
And perhaps the Sample Code repository should provide an easy way to link to/copy from external resources.
But the ultimate question in this: Who will provide the resources needed to maintain a decent repository ?
____________
Blog: LucD notes
Twitter: lucd22