[ckan-dev] organizing ckan extensions in github

Mon Jun 9 23:54:54 UTC 2014

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,
> Pabitra
> Utah State University
> Logan 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
<http://www.linkedin.com/in/vitorbaptista> | @vitorbaptista
<http://twitter.com/vitorbaptista>

The Open Knowledge Foundation <http://okfn.org>

*Empowering through Open Knowledge*

http://okfn.org/  |  @okfn <http://twitter.com/okfn>  |  OKF on Facebook
<https://www.facebook.com/OKFNetwork>  |  Blog <http://blog.okfn.org/>  |
Newsletter <http://okfn.org/about/newsletter/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140609/f441dfa2/attachment-0003.html>