Problem/Motivation
John, long time! I am still working with a team on the OpenScholar software package and we were just beginning to migrate our code to D9. As part of that we were updating purl and purl_group to D9. Wondering if you are interested in help co-maintaining this since we are likely some of the heaviest users of purl and have an ongoing interest in keeping the purl/group integration alive. If not thats fine we can submit the patches for D9 per usual.
Also only partly related to group_purl, are you interested in co-maintaining purl itself, IMO your fork is the most heavily used and forked. With the languishing of the purl Drupal project there has not been as concerted an effort to maintain a single code base. I/we would support you if you went that direction, in either case expect PR's for your forked repo. Thanks Richard.
Project page: https://www.drupal.org/project/group_purl
Steps to reproduce
N/A
Proposed resolution
Submit patches, or D9 branch directly
Remaining tasks
Updating doc comments / info file.
User interface changes
Minor/None
API changes
None proposed
Data model changes
None
Comments
Comment #2
avpadernoComment #3
avpadernoSee Taking over unsupported (abandoned) projects (which isn't just about unsupported or abandoned projects) to understand what the next steps are.
Comment #4
rbrandon commentedThanks apaderno hadn't gotten to that yet. Maybe John will take notice now otherwise I will go that route as we continue to update our fork.
Comment #5
rbrandon commentedStill no replies in the issue queue or via https://www.drupal.org/user/313537/contact, going to move this over to Project ownership queue so we can get our active dev on D9 into this project for the group.
Comment #6
avpadernoI contacted the project owner as site moderator.
I am changing status, since we are waiting for a reply from the project owner.
Comment #7
avpadernoComment #8
rbrandon commentedapaderno,
It has been a couple months since I contacted John and 2 weeks since you did. Can we get some movement on this this weekend? Would like to get our patches in on Monday so we can do our second release with them in place.
Richard
Comment #9
avpadernoI added rbrandon as co-maintainer (user with all permissions on the project but the one to administer co-maintainers/maintainers).
Comment #10
freelockHi,
Ha! was just doing some issue management on group_purl, and then checked on purl to see if anybody had moved that forward (the real blocker here!) That led me to this issue.
@rbrandon - Happy to have more help maintaining stuff, feel free to hit me up on Drupal Slack (@freelock) or (preferably) Matrix (@john:matrix.freelock.com) if you'd like to discuss any details.
Comment #11
freelockNobody has offered to co-maintain Purl yet???