[ckan-dev] Looking forward to CKAN 2.4

Fri Mar 13 08:44:21 UTC 2015

That is *fantastic*.  

It'd be good to get https://github.com/ckan/ckanext-spatial/pull/93 <https://github.com/ckan/ckanext-spatial/pull/93> reviewed and merged so everyone can use the awesome. Who knows most about ckanext-spatial nowadays?

Ross

> On 13 Mar 2015, at 02:04, Florian May <florian.wendelin.mayer at gmail.com> wrote:
> 
> +1 for spatial edition! My end users wanted easier georeferencing.
> 
> Prototype - https://vimeo.com/116324887 <https://vimeo.com/116324887>
> Request - https://github.com/ckan/ideas-and-roadmap/issues/138 <https://github.com/ckan/ideas-and-roadmap/issues/138>
> 
> Cheers,
> Florian
> 
> On Fri, Mar 13, 2015 at 1:22 AM, Ross Jones <ross at servercode.co.uk <mailto:ross at servercode.co.uk>> wrote:
> Hello,
> 
> I was wondering if it is too early to talk about CKAN 2.4 yet?  I'm still totally stoked that 2.3 is out (thanks everyone), and I'm really looking forward to seeing some sites migrate up to it, but I was wondering if now would be a good time to discuss what happens next.
> 
> Currently we have 124 open ideas at https://github.com/ckan/ideas-and-roadmap/issues <https://github.com/ckan/ideas-and-roadmap/issues> (if you didn't know about it, please add more), although without sponsors some of them may never happen.  I guess the core team will pick ideas that they're interested in, or are required by their sponsor, but as a bigger picture I was hoping there might be some sort of steer from the, um, steering group and user base as a whole as to some sort of priority. This might help other people wanting to contribute* to pick things to work on.
> 
> Perhaps we should pick themes for the releases - so for instance, there's been a lot of interest in more geospatial features - we could make 2.4 the geospatial edition?  Just a thought.   Obviously outstanding issues need to be fixed, and people will pick up from the ideas repo as things interest them, but perhaps a theme, or at least some priorities for the next release would be a good idea.  
> 
> Ross.
> 
> 
> p.s. I've posted this to ckan-dev, and hoping that some of the steering group may be on the list because I didn't want to cross-post to the ckan-global-user-group list. Cross-posting is evil and I'd hate to be one of those people who start emails "Sorry for cross-posting".
> 
> * Reminder you don't have to be a dev to contribute, ticket-gardening, documentation, translations, testing, all very, very, very useful. 
> 
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org <mailto:ckan-dev at lists.okfn.org>
> https://lists.okfn.org/mailman/listinfo/ckan-dev <https://lists.okfn.org/mailman/listinfo/ckan-dev>
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev <https://lists.okfn.org/mailman/options/ckan-dev>
> 
> 
> _______________________________________________
> 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/20150313/4a58f625/attachment-0003.html>