Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello long-suffering Views Datasource users, it's your module maintainer here. Yes I've been absent for a long time but I'm back and I'm going to clear the issue and make a BETA3 release with requested features like individual configuration for each field, and bugfixes by Monday. Thanks hugely to Joshua Jabbour and others for helping out in the issue queue while I was gone. I'm really sorry for the delay in releasing the new version and I'm going to get things back on track ASAP.
Comments
Comment #1
joshuajabbour CreditAttribution: joshuajabbour commentedGlad to hear you're back! In your absence, I created a fork for my own use at http://github.com/joshuajabbour/views_datasource/commits/master. It mostly adds coding standards fixes, but also rolls in a handful of patches from the queue. I'd be happy to help merge it in if you like...
Comment #2
joshuajabbour CreditAttribution: joshuajabbour commentedAlso, I'll happily help out if you need a co-maintainer...
Comment #3
joshuajabbour CreditAttribution: joshuajabbour commentedSo no chance on becoming co-maintainer? I'd love to fix a bunch of bugs and get a new, stable release out, but can't do it via patches alone.
Comment #4
matsjacobsson CreditAttribution: matsjacobsson commentedWonderful!! Keep up the good work! :)
Comment #5
allisterbeharry CreditAttribution: allisterbeharry commentedSorry again for the delay, I haven't been active on this module for a while. I'm trying to get a new release out with all the bugfixes by the end of this week.
Comment #6
allisterbeharry CreditAttribution: allisterbeharry commentedActually I wouldn't mind a co-maintainer for certain things but right now I'm still trying to finalize how certain things work inside the module and how it interacts with Views, and the code is in a mess formatting and structure wise. Once I hit the 1.0 release I'll have it cleaned up so somebody else can work on it. But thanks hugely for the work and support you've done already, I really appreciate it.
Comment #7
joshuajabbour CreditAttribution: joshuajabbour commentedok, yeah I figured I could do the cleanup since you're right, it's kind of a mess and that's a lot of what I've already done :) but my fork works for me...
Comment #8
Rj-dupe-1 CreditAttribution: Rj-dupe-1 commentedHi Alister, your work is much appreciated... but if you are strapped for time/energy perhaps taking up Joshua's offer might be worthwhile?
Comment #9
seandunaway CreditAttribution: seandunaway commentedPlease consider a co-maintainer. I'm needlessly running forked code as well.
One option is to just open up a new branch and limit your co-maintainer to that branch so it doesn't interfere with your refactoring.
Comment #10
kenorb CreditAttribution: kenorb commented@allisterbeharry: I offer help as well if you need.
Comment #11
kenorb CreditAttribution: kenorb commentedComment #12
PasqualleAllister is inactive for many many years.
Anyone interested helping with maintenance, please read #3032383: Responsible maintainer
this issue is obsolete