Should we add folders to make things easier to find?

[alanrenouf]

Should we add folders to make things easier to find in the structure, for example:

Scripts -> vCenter ----> Hosts ----> VM ----> Datastores -> Update Manager -> SRM -> NSX -> VSAN

Etc?

[lucdekens]

You could, on the other hand I can imagine scripts/functions that would fit in two or more folders. Perhaps stick with meta tags for now.

Do you plan a front-end for access?

On Sun, Jul 24, 2016 at 11:39 PM, Alan Renouf notifications@github.com wrote:

Should we add folders to make things easier to find in the structure, for example:

Scripts -> vCenter -> Hosts -> VM -> Datastores -> Update Manager -> SRM -> NSX -> VSAN

Etc?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/vmware/PowerCLI-Example-Scripts/issues/13, or mute the thread https://github.com/notifications/unsubscribe-auth/AHZrCaXtvGPoREGSTlcCCJXdhZEC6IeNks5qY9utgaJpZM4JTrO_ .

[kmruddy]

+1 on the tag usage

I don't believe a front end was in the plans so far. Do you have an example of one you like?

[lucdekens]

The PowerShell Gallery https://www.powershellgallery.com/ is quite nice, although they don't impose tags (yet). Their search looks in the Description and function names it seems.

Adding/verifying meaningful tags could be one of the tasks of the admins of the repository.

Another interface can be found at poshcode.org

On Mon, Jul 25, 2016 at 2:33 AM, Kyle Ruddy notifications@github.com wrote:

+1 on the tag usage

I don't believe a front end was in the plans so far. Do you have an example of one you like?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vmware/PowerCLI-Example-Scripts/issues/13#issuecomment-234813462, or mute the thread https://github.com/notifications/unsubscribe-auth/AHZrCcbA1FTQHcxkEyLqbwUG3KFwl0gqks5qZARcgaJpZM4JTrO_ .

[RamblingCookieMonster]

+1 to tags.

The gallery doesn't impose tags, but they do support it; for example PSDeploy is tagged with Deploy, Continuous, etc.

With those tags in the module metadata, the front end (and PowerShellGet functions) can display them:

Lastly, even if you end up implementing your own front end system, it would likely be helpful to PowerShell users who now have commands like Find-Module, Find-Script, or Install-Module, to have access to functions, scripts, or modules from this repo.

If you're interested in this, hit me up, would be happy to help drop some continuous integration and deployment scaffolding in place to automate this (Example deploying PSDeploy with PSDeploy) : )

Cheers!

[gminks]

tags will make it easier to search across the entire dataset, especially as it grows larger.