[ckan-dev] Thoughts on CKAN development

[Haq, Salman]

Hi all,

After developing a non-trivial extension for CKAN, I want to share some thoughts with the development team. Some of these may not be news for the dev team but I want to share them anyway.


 1.  Interface classes lack documentation (other than function doc strings).
 2.  Request data flow is not clear from documentation.
 3.  Package form is monolithic.
 4.  'context' dictionary is used in several places but it is not documented.
 5.  Too many levels of indirection.
 6.  Cruft.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20120926/f0e70185/attachment.html>