Hello,

Unfortunately, we, at the Nuxeo organization, are no more maintaining this repository, unless for critical security fixes.
Maybe @peter-kehl, the other repository owner, could help?

Otherwise, don't hesitate to check the project's forks to find a potential maintainer or to fork it yourself.

Besides, @peter-kehl, we're thinking about archiving this repository to make it read-only and disable any future comments.
The repository could then still be forked, or unarchived if needed.
What do you think?

Regards,

Hi @ataillefer,
What's the benefit of archiving/freezing this? Is it so that Nuxeo software doesn't break due to DaisyDiff changes? If so, couldn't you create a tag and point at it instead?

Hi @jbraybrook and @ataillefer,
Unfortunately, due to permanent overload I can't maintain this. Any ideas other than telling people to fork (and increase confusion/entropy)?

Hi @peter-kehl,
We were thinking about archiving the repository to prevent people from opening issues and pull requests that would never be handled, since neither you nor us are willing to maintain it.

We are already relying on the latest release-1.2-NX4 tag so that's not really an issue.

Indeed, multiplying the forks might not the best idea.
We could, if some people are willing to maintain this repository, grant them Owner/Administrator access.
Then, at Nuxeo, we would probably do our own fork and rely on it to be sure we're working on a "frozen" master branch from which we could perform additional releases if needed...