[ckan-dev] organizing ckan extensions in github

[Pabitra Dash]

Thanks Sean for the suggestions. There may be some possibility to reduce the number of plugins.
Pabitra



> From: sean.hammond at okfn.org
> To: ckan-dev at lists.okfn.org
> Date: Tue, 10 Jun 2014 12:19:04 +0200
> Subject: Re: [ckan-dev] organizing ckan extensions in github
> 
> 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.
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140610/83c199a7/attachment-0003.html>