Add a New Webform Maintainer

Hi. Nice one. I'd like to add that I have a fair bit of custom code that does virtually what Webform does but includes a few other things, including CCK Integration, basic multi-lingual support, it has an API for processing the submitted data in basically any way you can think of, and very rough views integration, although not using the same implementation style that is being talked about in the view integration issue, but that's something I'd like to change.

It's currently sitting in a separate project, as I was coding it whilst still using Webform, and the original scope was not Webform, but that has now changed, and I'd be happy to put it up for review as a way of moving forward with a few things, or even helping out. I've got about 2-3weeks of full time work I can put into this project pretty much right away also, although I do have some unique goals that are probably not in line with all of webform in general, but 99% of the unique requirements are in separate modules now thanks to the API.

Is this something you guys might be interested in? If so, perhaps I can provide the code, and the details of my implementation to date, and perhaps we can mix and match?

Whilst not my original intent, it turns out that I've re-written webform just about. :) But I'm happy to contribute my efforts to the community.

The only draw-back to the CCK integration, is that it requires a small patch to CCK (a one liner which adds a new hook), and some of the CCK functionaliy had to be replicated and modified, and support for the separate CCK modules requires extra integration, but I've already got it working with all the core CCK fields (excluding multi-group), filefield, imagefield, there is rough support for fieldgroups, the matrix field is another I've tested, haven't got to Date yet, but I see no reason why it would not work. Most of the customizations are to do with handling the data.

Any way, enough rambling, are you interested? If so, how would you like to proceed? I'm still going to be working to achieve what I need for my company, but I believe a lot of this can be contributed directly into the core of webform, and back into the community.

Good stuff.

@cdale
I would suggest that as development for Webform continues that you monitor the Issues / Feature requests queues, and when you see a relevant place to include some of what you've done that may help it along, then by all means include that code to help fuel the discussion.

Dan's CVS account app approved and also added to the project.