[ckan-dev] organizing ckan extensions in github

[Sean Hammond]

If you're really expecting to write ~40 separate extensions that are
going to work together on one site (and that are all very specific to
that particular site), I would question whether it's a good idea to
implement them as separate extensions. It might be easier to combine the
features into a smaller number of larger extensions/plugins.

Generally one great monolithic CKAN plugin is going to be easier to test
than 40 little ones that achieve the same result. Having said that when
things really do implement separate features it is good to separate them
out into plugins/extensions, so there's a balance here.