RDFLib/pyrdfa3

Looking for a new maintainer

iherman opened this issue · 5 comments

iherman commented

Dear all,

many years ago I developed this Python module. The library seems to be fairly solid; the only change I made a while ago was to adapt it to Python3 as well. The library is also what drives an RDFa extraction service at W3C.

However… I have recently retired and, although I still maintain some activities at the W3C, I do it on greatly reduced hours. Maintaining this library, possibly developing it further as RDFLib evolves, etc, is not something I can commit myself to do anymore. I am looking for a person (or persons) who would be willing to take over this responsibility.

Any takers?

Cc @RDFLib/rdflib

jayaddison commented

@prrvchr thanks for reviving this library - I've been looking through the diff from v3.5.2 to v3.6.2 before upgrading and wanted to check that the expected changes are:

  • Dropping Py2.x support (code simplified given Py3+).
  • Removing use of the deprecated Python cgi module, and using the Python html module for escaping instead.
  • Removing the PyrdfaExtras component from the library since recent (5+) rdflib provides all the necessary functionality.
  • Some formatting / stylistic changes, and additional commenting.
  • Enabling TLS verification by default and adding a configuration toggle for this.
  • Removing some build/documentation directories from the source repo.
  • Adding fluidattacks scanning for the repo.

Is there anything else that I've missed? As someone keen to migrate: it would be reassuring to provide a description of the changes.

prrvchr commented

Hi jayaddison,

I think you produced a fairly detailed description of what was done for version 3.6.2.

I don't immediately see what could have been forgotten?
Perhaps the migration of the documentation to pdoc (the adaptation of the source code for pdoc remains to be done)...

​

  • 👍1
jayaddison commented

Ah, thanks - yep, great - the epydoc to pdoc migration would make sense to mention too 👍

And, not so much code changes, but the change of origin repository could be worth noting -- I see that PyPi does show the updated homepage from the newly-published versions already.

Is the plan to continue to develop/publish from your fork of the repository, or might this rdflib one become the 'home' again in future?

prrvchr commented

Is the plan to continue to develop/publish from your fork of the repository, or might this rdflib one become the 'home' again in future?

I have both options since @iherman graciously gave me the administration of this repository.

But I think as long as I'm the only maintainer, I'll leave this repository dormant and do maintenance and support on my repositories.

  • 👍1
jayaddison commented

Ok, thanks @prrvchr. From experience seeing a few projects fork/relocate over the years: it can be a good confidence boost when there are bi-directional links from the original project (e.g. here) to the new project, and vice-versa.

For example: the pg8000 PostgreSQL driver project that was previously developed at https://github.com/mfenniak/pg8000/ and where the README has been updated to link to the current home at https://github.com/tlocke/pg8000/ (that in turn contains the commit history and various mentions of the original author).

(I plan to upgrade some projects I work on to pyrdfa3 v3.6.2 soon, partly as a result of reviewing the changes and chatting here - I thought it could be helpful to explain some of the thought process, and similar experiences with other projects)