Dead project?

[frafra]

Hi,
as I am continuing to develop and maintain this code and it seems that you are no more interested in it, would you like to block this repository and deprecate it in favour of my repository where the development still happens?

What do you think about it?

[martinburchell]

Thanks for raising this and sorry for not responding to your pull requests. Thank you for your contributions.

It's not dead. We are still using this plugin in an active CKAN instance for one of our clients. Unfortunately our paid work has to take priority and we have little time for maintaining our open source projects.

[frafra]

Ok, thanks for your reply, I did not want to be rude.

I am using a patched version with the various pull requests in a couple of catalogs that will go into production.

If there is anything I can do to help with that, just say it.

[martinburchell]

@frafra I think it's fair to say that we're not able to maintain this anymore. Are you still interested in taking it over?

My preference would be either for us to transfer the repository to you or for us to add you as maintainers to this repository. We'd need to give you access to PyPi as well.

[jqnatividad]

@martinburchell @frafra you may want to check out https://github.com/datopian/ckanext-versioning.

We investigated using ckanext-datasetversions last year for a project (for which I'm no longer involved), but the client's reqts were quite rigorous, so they ended up developing one from scratch that uses git as a backend.

[martinburchell]

@jqnatividad Interesting. I've not looked at this in detail. It would be good not to duplicate effort. The main use case for our client is to support "daily situation report" maps where each dataset is different to the previous one, but the old one isn't necessarily wrong.

[frafra]

@frafra I think it's fair to say that we're not able to maintain this anymore. Are you still interested in taking it over?

My preference would be either for us to transfer the repository to you or for us to add you as maintainers to this repository. We'd need to give you access to PyPi as well.

I am using this extension for a project and it would be nice to be able to help maintaining it. Feel free to add me as maintainer.

[frafra]

We investigated using ckanext-datasetversions last year for a project (for which I'm no longer involved), but the client's reqts were quite rigorous, so they ended up developing one from scratch that uses git as a backend.

Thanks @jqnatividad, very nice :) We considered to rely on git, but we store binary files and we have a linear / append-only workflow.

[frafra]

datopian/ckanext-versioning has been deprecated, and the new datopian/ckanext-versions is not considered stable. I need to continue to use ckanext-datasetversions for existing projects, so I am interested in maintaining it, if no one else is interested.

[frafra]

@martinburchell I reiterate that there is no stable exception for dataset versioning in CKAN except this one, which is mostly unmaintained. There are PRs and fixes. I am ready to support this extension, but I do not want to create useless duplicates.
If aptivate is no more interested in maintaining such repository, I proposed to update the README file to state that this repo is unmaintained, redirect users over https://github.com/NINAnor/ckanext-datasetversions, as we intend to maintain this codebase, and make it read-only.

[martinburchell]

@frafra So I'm hearing that you're still using this and the alternatives won't work for you. That's great. We still need this extension for one of our clients at least until they are able to move off Python 2.7 and CKAN 2.7. We may need it beyond that if they do.

We currently don't have the resources to maintain ckanext-datasetversions and would prefer for it to remain within our organisation. We're also happy for you to continue to be a maintainer and merge in the changes from your fork, so long as we can develop off an earlier version if we need to. Let me know if there is anything that is stopping you from doing this.

Of course there's nothing to stop you carrying on developing on your own fork if you['d prefer to do that.

[frafra]

@martinburchell thank you for your reply. I extended the code and ported to CKAN 2.9, and I was worried about not having feedback on the existing PR. I will polish them further and ask you to merge them again when ready, trying not to bother you too much :)

[martinburchell]

@martinburchell thank you for your reply. I extended the code and ported to CKAN 2.9, and I was worried about not having feedback on the existing PR. I will polish them further and ask you to merge them again when ready, trying not to bother you too much :)

@frafra let me know if there are other people you'd like to add to the project