Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

About the name modules #6

Closed
czhang03 opened this issue Sep 16, 2016 · 6 comments
Closed

About the name modules #6

czhang03 opened this issue Sep 16, 2016 · 6 comments

Comments

@czhang03
Copy link
Contributor

the first sector of the list is called modules, but there are some thing definitely not modules in there, like:

  • IDEs
  • Chocolatey (Package Manager)
  • AutoSPInstaller (SharePoint) [I think this is more a script than a module]

and ect. so I suggest changing it to Modules and Utilities instead of just Modules

@janikvonrotz
Copy link
Owner

Sounds reasonable. Have to admit that my initial content sure is out of date. Where would you draw the line between Utilities and Modules?

@czhang03
Copy link
Contributor Author

hum, I think Modules is more like plugins, but utilities are apps.

utility is not written in powershell script, but can be used in powershell (like thefuck and choco). but Modules are installed in the $env:PSModulePath and written in powershell language.

That is just my defination.

@vors
Copy link
Contributor

vors commented Sep 17, 2016

Agree. The word "Module" has a strong connotations in the context of PowerShell.
It's better to move IDEs and other non-ps-module things outside or better re-think the organization structure more deeply.

In general, I think that the naming and division is very strict right now.
For example, take a look how many items are in https://github.com/unixorn/awesome-zsh-plugins#plugins and they are not divided into a granular categories. I think it's better, because some things are hard to classify (i.e. PSReflect is mainly about security, but it's also a module and is generally useful).

It also worth mention that more loose structure will encourage more contributions, because it's way more work to create a category then to add one-line into an existing (loose) one.

@janikvonrotz
Copy link
Owner

@vors I see the problem with "Module". Instead of having Module and Resources as top-level categories I propose to create something like https://github.com/ianstormtaylor/awesome-heroku. Simply using a flat and sorted structure. If necessary also add the classifier in front of the link. The PowerShell repo itself could end up under "Meta", "Source" or whatever suitable. A short introduction on every category might also help new contributors. What do you think?

@vors
Copy link
Contributor

vors commented Sep 18, 2016

@janikvonrotz good thinking, flatter structure is better.
I'd say they have the same problem: there are categories with just one entry (like blogs). Also not sure that labeles in front is a good idea.
I think as a first step, we can remove Module and Resources from the top-level. Maybe rename Resources into "Reading".
Then I'd like to make the categories more loose. If something has 1 or 2 items, maybe it should be generalised.

How that sound?

janikvonrotz added a commit that referenced this issue Sep 19, 2016
what do you think?
see #6 for discussion.
janikvonrotz added a commit that referenced this issue Sep 19, 2016
see #6 for discussion.
janikvonrotz added a commit that referenced this issue Sep 19, 2016
fix #23 sry for the inconvenience. I hope everything is fine now. This
change is still open for discussion, see #6
@czhang03
Copy link
Contributor Author

I think the flat structure resolves this problem, I will close this issue.

If any one think there is anything wrong with the flat structure, feel free to reopen this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants