Git-friendly PowerShell package structure -

i have number of script (.ps1) , module (.psm1) files version control (i'm planning use github). i'm hoping deploy them package, perhaps using nuget.

i have following directory structure:

|-my documents    |-windowspowershell      |-modules        |-com.foo.bar.modulea          |-com.foo.bar.modulea.psm1        |-com.foo.bar.moduleb          |-com.foo.bar.moduleb.psm1      |-scripts        |-samples          |-foobar.ps1          |-other non-script files version 

i'm using windowspowershell folder make easier use code.

i've created github repo (which created readme.md file).

powershell-related questions:

• is using java-esque file , folder naming conventions practice modules, if want treat them package? true of scripts well? there better structure?
• if use non-standard scripting directory (not windowspowershell),can modify profile (microsoft.powershellise_profile.ps1) find it?

git-related questions: - should clone repo default directory (my documents\github) or windowspowershell? - if use github directory, should move existing files new directory (child of github)?

git-related answers:

you not need move files. git init in windowspowershell folder (or in sub-folder if want version control them independently). create .git folder repository version controlling files below windowspowershell directory.

then push github if wish. don't need if version control after. creating repository.