There may be another thread on this topic somewhere else, so please forgive me if this has already been discussed.
What are the protocols/best practises for incorporating individual commands (aka, plugins, extensions, etc.) into our own packages folder? There are a lot of new commands being developed (fantastic! So much more community involvement than there ever was with E) but they’re popping up in a variety of ways such as individual repos, gists, zip downloads and the like.
What I’d like to know is, should we be encouraging people to include individual commands (such as wbond’s excellent sublime_alignment, ajpalkovic’s excellent new goodies and also dom111’s plugins) in a broader package (say Text or Source or whatever) which is how Textmate is organised? Or is the flexibility and granularity of having commands (or small related suites of commands) in their own package preferred? I can see pros and cons in both approaches.
It would be great if some of these new commands could be placed in the community repo on Github and packaged up in a consistent, standard way, thereby (hopefully) encouraging forking and collaboration. As a great example, I really like how Will (wbond) has packed up sublime_alignment complete with a great readme and prebuilt keymaps. It just works.