Offering to co-maintain Prepopulate

I'd be willing to help as well. Although I won't be actively working on development (as I don't foresee future client work requiring this module), I'd be happy to review, commit and cut releases for RTBC issues as I'm doing with all of my other modules (as time permits).

It has been over two weeks (over a month in fact). Per the official guidelines for adopting abandoned modules, you can proceed to the next step to ask the webmasters to grant you access.

Redirecting this to the appropriate issue queue so that it can be taken care of by the webmasters.

This should be addressed: https://www.drupal.org/project/prepopulate/issues/2849432#comment-12606049

Since the issue linked in #6 is marked as fixed, then maybe this issue should be re-opened.

I'd recommend making heddn aware of this issue as he's been committing lately.

The project link is https://www.drupal.org/project/prepopulate.

I sent a message to the project owner and heddn, asking to reply here. Without any reply in the next two weeks, scuba_fly will be made co-maintainer.

Are there specific issues that need to be addressed at this point? The module has a D8 port and is functional in several live sites. The use in D8 is different than in D7 and needs some docs updates. But the functionality is fine.

One of the points given from scuba_fly was See how the Drupal 8 version can be improved. scuba_fly should make clearer what he meant by that.

When this issue was opened, I think there was very much a need for that. But since then the D8 code has been refactored, commits have landed and folks are using it now. (Previously the D8 port was non-existent) I'm interested what is remaining to improve. The lone trend I've seen in the issue queue for the past few months is a request for improved docs on how to use the module. I wonder if that is what we are thinking is still missing?

As always, patches and contributions to issues are welcome.

@heddn: Are you actively maintaining the module now? If so, I believe that solves the problem. At the time, the module owner was unresponsive, and we weren't able to get anything done.

I wasn’t aware of this issue. I’ve corresponded with several potential maintainers and have given access to @heddn with a commitment to maintaining the security patches while moving the project forward. If he wishes I’m happy to fully transfer ownership to @heddn

Is there anything else that needs to be done?

I don't think so. There's a stable release of the project now. I'd say this isn't necessary any more.

@heddn Would you like to become the project owner as jbrauer implicitly asked in #17?

Sure thing

Sounds like we've got a plan.

I changed ownership to heddn as requested. Basing on what he said, there isn't anything more to do, so I am closing this request (which doesn't mean I added other users as co-maintainers).

For other requests, please open a new issue in the project issue queue.

(I meant closed like this.)