[ckan-dev] organizing ckan extensions in github

[Pabitra Dash]

Thanks Vitor for the suggestions. I am not too worried about other people being able to find and install these plugins as they are very specific to our ckan instance and may not have any general use. I am thinking from the development point of view what would be best to manage code on github for pull and push.
Pabitra




From: vitor at vitorbaptista.com
Date: Mon, 9 Jun 2014 20:54:54 -0300
To: ckan-dev at lists.okfn.org
Subject: Re: [ckan-dev] organizing ckan extensions in github

Hi Pabitra,
I'd rather have a separate repository for each extension. In my opinion, this keeps it more organized, and also allow people to install them using pip. To make it easier for other people to find the extensions I would create them all using some pattern for the name (e.g. ckanext-*), and maybe think about writing them in a separate organization.


Cheers,

2014-06-09 13:42 GMT-03:00 Pabitra Dash <pkdash_reena at hotmail.com>:





Hi All,
I know it is more of a GitHub question rather than ckan. We intend to develop about 40 ckan extensions which are very specific to our instance of ckan. I am not sure if it is better to create a separate gthub repo for each of these extensions or create one repo and organize all extensions with some kind of folder structure within that single repo. Would like to know from anyone who has been involved in developing multiple ckan extensions on how they have organized their code in github.


Thanks,PabitraUtah State UniversityLogan UT, USA


 		 	   		  

_______________________________________________

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




-- 
Vítor Baptista

Developer  |  http://vitorbaptista.com | LinkedIn | @vitorbaptista

The Open Knowledge Foundation

Empowering through Open Knowledge

http://okfn.org/  |  @okfn  |  OKF on Facebook  |  Blog  |  Newsletter





_______________________________________________
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/10aadb10/attachment-0003.html>