I recently had to do a major refactoring of fields and found Field Rename to be helpful.
However, I had to patch it to get it to work, there was no README and the documentation on the project page was slightly inaccurate.
I think it could to with some love. I hereby offer to step up and maintain the project.
In particular. I would like to see these committed:
If there is no response within two weeks, this issue will be moved to the Drupal.org project ownership issue queue
and escalated to a request for ownership transfer, according to the procedures for Dealing with unsupported (abandoned) projects.
A copy of this notice has been sent the current owner (fizk) via the contact tab on the Drupal.org user profile page.
Comments
Comment #2
gisleTwo weeks has passed. There has been no response.
Transferring issue to he Drupal.org project ownership issue queue and requesting ownership transfer.
Comment #3
gisleComment #4
avpadernoI changed ownership as requested.
I left the previous project owner as maintainer. I will let you decide if removing him entirely, or leaving him as maintainer without permissions. (In the latter case, his commits will still be listed under Maintainers for Field Rename and other places.)
Comment #5
gisleThank you for the transfer of Field Rename. It now has a full 1.0 release, including security coverage.
I always retain previous owner and any maintainers, unless they explicitly request to be dis-associated with the project. My reason for preferring ownership is not to remove their access, but to be able to opt the project into security coverage.