[quote=“guillermooo”]Creating a full new package for every plugin seems to be overkill. I think grouping small plugins in a “Plugins/Text/Source” package is the best way to go at the moment… Unfortunately, I don’t think Mercurial or git (most plugins if not all are hosted either at Bitbucket or GitHub) let you clone single files from a repo. And I don’t think anybody would like to blindly download all the plugins in the org.
So assuming this was the preferred way to deal with loose plugins, I see two compatible options:
- We create a Plugins repo in the GitHub org off of which everyone can work
- Plugin developers use the system that suits them best and provide a “Plugins.sublime-package” file for download. Sublime will copy the files to the Packages/Plugins folder on its own.
[/quote]
With strong editorial this seems to be a good compromise. By editorial I mean someone or the community should decide on what is generic and broad enough in appeal to go in the generic “Plugins/Text/Source” package, and what is esoteric enough to go in its own package.