ckan / ideas

[DEPRECATED] Use the main CKAN repo Discussions instead:
https://github.com/ckan/ckan/discussions
40 stars 2 forks source link

CKAN Roadmap and v3 in particular #248

Open rufuspollock opened 4 years ago

rufuspollock commented 4 years ago

Current page is out of date https://ckan.org/developers/roadmap/ and could do with anb upda

There's also a discussion to be had about what we want to see in CKAN v3

Initial Thoughts (presented on tech team call 14 May 2020 by @rufuspollock)

Comments welcome

https://docs.google.com/document/d/1Bv-01m6_jKExs78foS9kbeyymhUom-idZJ8D4wQ_erE/edit#

Previous discussion (Aug-Sep 2018)

See https://lists-archive.okfn.org/pipermail/ckan-dev/2018-August/022860.html

https://docs.google.com/document/d/1qxU-wkUBf7BgMsBzOvMUKNcyYCyzBsbNQoKtdioRReg/edit#heading=h.ka47zlvu99u

wardi commented 4 years ago

I created a milestone for some important features it would be nice to have merged for 3.0 https://github.com/ckan/ckan/milestone/14

jasonlally commented 3 years ago

Hello, just wondering which is the official record for roadmap plans for CKAN 2 and 3? Where should I be looking for the source of truth so to speak :-) @rufuspollock

wardi commented 3 years ago

The only truth is code that's working, reviewed, and merged :sunglasses:

This repo is no longer updated but some of the current important feature work has been collected under https://github.com/ckan/ckan/projects/4 which we're trying to keep up to date.

The next release is slated to be called "2.10" for now; we've been saving "3.0" for a release with big incompatible changes. I think our next release is a good candidate for a "3.0" because it's python3-only but there's no consensus in the core team yet.