[ckan-committers] Fwd: Information about CKAN 3.0

Wed Mar 20 09:54:54 UTC 2019

FYI

---------- Forwarded message ---------
From: Adrià Mercader <adria.mercader at okfn.org>
Date: Wed, 20 Mar 2019 at 10:54
Subject: Re: Information about CKAN 3.0
To: Lothar Hotz <hotz at informatik.uni-hamburg.de>, Ogeigha Koroyin <
koroyin at informatik.uni-hamburg.de>

Hi Ogeigha,

Thanks a lot for you help offering! We will be doing a detailed scoping and
planning of the migration to Python 3 and other major improvements in the
following weeks. Once we have that in place it will be much easier to see
which extensions you can help with and what's the work involved. I think
the timeline that you suggest towards the second half of 2019 will work
really well as we'll be probably focusing on extensions by that point.

Thanks again and I'll keep in touch.

Adrià

On Sat, 16 Mar 2019 at 01:49, Ogeigha Koroyin <
koroyin at informatik.uni-hamburg.de> wrote:

> Hi Adrià,
>
> we've been looking through our options and would like to offer our help
> (probably towards the second half of 2019 could be realistic). First of
> all, I'd like to give some details about what extensions we currently use
> and extensions we have written so that you can assess in what areas we
> could be of help. Please note that we have only worked on extensions (not
> on core CKAN) so far.
>
> These are the extensions we currently use:
>
>    - ckanext-dcat
>    - ckanext-dcatde
>    - ckanext-harvest
>    - ckanext-spatial
>    - ckanext-archiver
>    - ckanext-qa
>    - ckanext-report
>
>
> These are some extensions we have written (some haven't been published
> yet) for our products (also in use):
>
>    - ckanext-distributed-harvester
>    - ckanext-fulltext
>    - ckanext-highlighting
>    - ckanext-hmbtg
>    - ckanext-hmbtgharvesters
>    - ckanext-odsh
>
>
> Attached is a list of the current dependencies which would need to be
> ported. We have a few questions with regard to porting:
>
> - firstly, what extensions and modules will you port (or plan on porting)?
>
> - secondly, concerning the extensions and modules that you are'nt planning
> on porting yourselves:  do you know who is / will be responsible?
>
> - lastly, could you give us a rough estimate of how much effort is
> necessary?
>
> Thank you!
> Best Regards
> Ogeigha
>
> P.S.: I'll be absent from my office next week, so that's why the reply-to
> points also to my colleague Lothar Hotz.
> Am 20.02.2019 um 13:25 schrieb Ogeigha Koroyin:
>
> Hi Adrià,
>
> just wanted to say, we'll study the plan and necessary changes and see if
> we can help with anything.
>
> Thanks again for your fast reply.
>
> Best Regards
>
> Ogeigha
> Am 19.02.2019 um 12:22 schrieb Ogeigha Koroyin:
>
> Dear Adrià,
>
> thank you for your help!
>
> Regards, Ogeigha
> Am 19.02.2019 um 11:57 schrieb Adrià Mercader:
>
> Dear Ogeigha,
>
> Thanks for reaching out. It's true that we haven't been very vocal about
> the python 3 support. We will aim to do a better job on that front.
> In the meantime, copied below is an internal summary that goes over our
> plan for migrating to python 3. The bottom line is that we are on the right
> track but as always progress is limited by what resources are available. If
> your organization can contribute in some way please let us know :)
>
> Hope this helps,
>
> Adrià
>
>
> Migrating to Python 3 involves:
>
> 1. Support Py3 in the codebase:
> 1.1 Core: this is done. We were lucky to have an external contributor do
> the bulk of the work regarding syntax changes and even set tests to prevent
> py2 only code being used from now on.
> 1.2 Extensions: this is not done. Selected extensions will need to be
> updated but I expect that it won't be difficult as the code bases are small
> in general (eg running lib2to3, using six, etc)
>
> 2. Drop Python 2 only requirements
> There might be smaller outliers which are not worrying but the main two
> things are:
>
> 2.1 Our beloved VDM: David has been quietly and steadily working on this
> critical refactor for over a year and it looks like we are reaching the
> final stages (
> https://github.com/ckan/ckan/pull/3972#issuecomment-454302773)
>
> 2.2 Pylons: Of course the main task involved in the Py3 migration. The
> bulk of the actual code work is done. I want to acknowledge Sergey and
> Konstantin that after the 2016 Brook/Adrià work Paul mentions did the
> majority of the blueprints migrations and addressed several Flask related
> issues. What is left is:
>
> 2.2.1 Small bits of Pylons code in tests etc
> 2.2.2 Refactor CLI to make drop paste.script: Konstantin has done the
> first initial work and now it's just a matter of migrating commands to a
> new syntax.
> 2.2.3 Write migration guide for extension developers
> 2.2.4 Migrate selected extensions to make sure they don't require Pylons.
> For the most commonly used ones that are following conventions this should
> not be a big job. There are certain compatibility issues for extensions
> that need to support both pre and post Flask CKAN versions but we'll deal
> with those as we go
> 2.2.5 Unknown minor issues that will surface as we use more and more the
> new version
> 2.2.6 Decide and implement a deprecation plan that allows people to
> migrate and ends up with a Flask only/ Py3 CKAN version by the end of the
> year (integrated in the wider roadmap that Kevin put together)
>
>
>
>
> On Mon, 18 Feb 2019 at 11:54, Koroyin, Ogeigha <
> koroyin at informatik.uni-hamburg.de> wrote:
>
>> Dear Mr. Mercader,
>>
>> we are a non-profit organisation located in Hamburg, Germany. We develop
>> and maintain several CKAN portals (amongst other things). At the moment
>> we've been trying to find out more Information about the development of
>> CKAN 3.0 (seeing as the Support for Python 2.7 will end on 1.1.2020),
>> but, unfortunately, have not found any pertinent information to date. We
>> would very much appreciate it, if you could give us some information
>> concerning this topic or, pointers to where we could find out more.
>>
>> Thank you in advance for your help!
>>
>> Yours Sincerely
>> Ogeigha Koroyin
>>
>> --
>> -----------------------------------------------------------
>> Ogeigha Koroyin
>> Hamburger Informatik Technologie Center (HITeC) e.V.
>> Vogt-Kölln-Strasse 30
>> 22527 Hamburg
>>
>> Telefon: 040 - 428 83 2613
>> Fax: 040 - 428 83 2617
>> Mail: koroyin at informatik.uni-hamburg.de
>> http://www.hitec-hamburg.de/
>>
>> --
> Ogeigha Koroyin
> Hamburger Informatik Technologie Center (HITeC) e.V.
> Vogt-Kölln-Strasse 30
> 22527 Hamburg
>
> Telefon: 040 - 428 83 2613
> Fax: 040 - 428 83 2617
> Mail: koroyin at informatik.uni-hamburg.dehttp://www.hitec-hamburg.de/
>
> --
> Ogeigha Koroyin
> Hamburger Informatik Technologie Center (HITeC) e.V.
> Vogt-Kölln-Strasse 30
> 22527 Hamburg
>
> Telefon: 040 - 428 83 2613
> Fax: 040 - 428 83 2617
> Mail: koroyin at informatik.uni-hamburg.dehttp://www.hitec-hamburg.de/
>
> --
> Ogeigha Koroyin
> Hamburger Informatik Technologie Center (HITeC) e.V.
> Vogt-Kölln-Strasse 30
> 22527 Hamburg
>
> Telefon: 040 - 428 83 2613
> Fax: 040 - 428 83 2617
> Mail: koroyin at informatik.uni-hamburg.dehttp://www.hitec-hamburg.de/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ckan-committers/attachments/20190320/a5cc3989/attachment.html>