Closed (outdated)
Project:
Salesforce Webform Integration
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 May 2010 at 16:57 UTC
Updated:
10 Sep 2021 at 21:32 UTC
Jump to comment: Most recent
Comments
Comment #1
aaronbaumanHave you tried contacting openbook about becoming a maintainer?
renamed per dealing with abandoned projects guidelines.
Comment #2
stella commentedI'd also like to help maintain or co-maintain the module. We're using it extensively and have some improvements we'd like to contribute back.
Comment #3
andybrace commentedHi Stella.
I've added you to the maintainers list.
Comment #4
stella commentedgreat, thanks! openbook++
Comment #5
EvanDonovan commented@stella: There have not been any commits in over a year and #969306: sf_webform Abandoned/Outdated? Alternative available as sandbox project is still unresolved. I have a new working version of this module for 6.x, and would like to commit it to the official project.
Could you add me as a co-maintainer for the project? If you do not respond within 2 weeks, I will go through the process to get access via the Webmasters queue.
Thanks.
Comment #6
stella commented@EvanDonovan - I'd welcome your involvement in the module. Unfortunately, I only have commit access and do not have the necessary permissions to grant you Git access. However, if you upload your patches to the queue, I'd be happy to review and commit them.
Comment #7
EvanDonovan commentedAh, I see. Who does have the ability to grant me Git access, then?
I think that would be simpler at this point, since the new version isn't really a patch. It had to be a total reworking in order to bring this module back into compatibility with the upstream changes in Salesforce Suite for 6.x. Let me know if you need me to explain in more detail.
Comment #8
stella commentedI imagine openbook, as the project owner, would have the necessary access. In any case, I would encourage you to upload your patch (or rewrite) to the issue queue so you can get more eyes on it and get it tested some more.
Comment #9
aaronbaumanAt this point it probably makes the most sense to roll webform functionality into the suite.
sf_webform hasn't been updated in over a year, and Evan has a somewhat newer sandbox version.
I think sf_webform will receive more attention in the salesforce suite issue queue, and potentially have greater reach.
Comment #10
EvanDonovan commentedLinking to related issue on the Salesforce module queue: #1101632: Include webform support.
Comment #11
stella commentedLet me know if I can help with this, either the move to Salesforce Suite or reviewing and committing patches to sf_webform. I'm recently back from an extended leave so should have time for this again now.
Comment #12
EvanDonovan commentedSorry, I have not been involved much with Salesforce for Drupal myself in the past few months. But the updated version of this module for Drupal 6.x + Salesforce Suite is here: http://drupal.org/sandbox/evandonovan/1198324. It would be great if you wanted to test that out. Maybe we could eventually move into the Salesforce module.
However, there are also two alternatives now: http://drupal.org/project/salesforcewebform & http://drupal.org/project/sfweb2lead_webform. I'm not sure which is better. It appears that both have 7.x versions, but the latter only works with Leads, so might not be a good universal solution. I think the UIs are quite different too.
Neither one probably uses the typical Salesforce Suite mapping screen, since neither actually depends on Salesforce Suite currently, according to the .info file. Perhaps there is still room for one that relies on the Suite, especially given that Springboard for 7.x may use the Suite?
Comment #13
avpadernoI am closing this issue since it has been created for a release that is now not supported. The project itself is marked as unsupported.