[ckan-dev] Experimenting with a minimal CKAN

Thu Oct 1 16:10:09 UTC 2015

You've probably thought about this quite a bit Ross - would it be too much
more work to have ckan-mini developed as a branch on CKAN itself?

It's unlikely that the work can be backwards compatible, but most orgs
using CKAN like a clear migration path. And if we start ripping things out
from CKAN with reckless abandon, an easy migration becomes impossible. That
would slow adoption, and afterwards you'll also have hundreds of legacy
CKAN instances around for years to come.

Another thing to think about is extensions. Nearly all would need major
updates, and it's highly unlikely that would happen. A lot of the less
popular ones would be left behind.

So really, what we're talking about is one of the possible alternatives for
a CKAN 3.0 branch.

- Denis

On Wed, Sep 30, 2015 at 3:15 PM, Ross Jones <ross at servercode.co.uk> wrote:

>
> > On 30 Sep 2015, at 20:03, Denis Zgonjanin <deniszgonjanin at gmail.com>
> wrote:
> >
> > I am interested! :D
> >
> > That might be ambitious, but I think we should try to build not one but
> a couple of reference front-end implementations on top of ckan-mini,
> independently of each other. That way we can make sure ckan-mini is fully
> decoupled from its front-ends. That in turn would let us:
> >
>
> That sounds like a really good idea.  One thing that has just struck me,
> is how a SPA would log in a user, I don't think basic auth works any more
> (I may be wrong) so would be hard to get the current user's APIKey. Should
> be reasonably quick to check and add something if necessary.
>
> > - More easily create highly customized CKAN sites.
> > - Keep the front-ends updated as shiny client-side technology evolves.
> > - Keep the back-end updated without being stuck to old server-side
> rendering frameworks.
> > - Build native apps and thingies.
>
> Another thing I'm hoping it'll show, is what's missing in the logic layer
> - I think having SPAs calling the action layer will show pretty quickly
> what more the API should/could be doing.
>
> Now, if only I wasn't rubbish at Javascript ....
>
>
> Ross
>
> _______________________________________________
> 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/20151001/30a76718/attachment-0002.html>