Jump to:
| Project: | Multivariate |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I played around with the multivariant dev module. I think it's quite a mess in the code and it does not work right away. Also I think mixing A/B tests with mutations is somewhat hard to understand, and it did not work for me right away.
I'm interested in redoing the whole module to bring it on production level. I think there is a big potential in enabling A/B "experiments" inside Drupal, but multivariant is not the best solution right now. Also I think the name of the module is somewhat bumpy.
My suggestion - why don't we create a complete new module, I'd call it "experiments", based on the Lean Startup Methodology. I actually already started to "fork" multivariant, to get most out of it.
What do you think? What do you (the creators) of multivariant think?
Comments
#1
I think I'd like to see a really drop-dead simple A/B + reports module that has a concise API like A/Bingo for Rails.
http://github.com/bryanwoods/ABingo
Perhaps just called "Bingo". (As that project name is available, currently.)
Then you could easily build tiny modules that use that API for site builders to pick between values of fields (perhaps a Bingo field formatter), select between different Contexts (and all that allows), or allow conversions to be set via Rules, etc.
I think I'll put some effort in on this while I'm in Denver.
#2
We became maintainers and started to do a plugin based rewrite on the 6.x branch.
Lukas, if you feel like creating a new module, there's no need to discuss with the current maintainer(s) of multivariate. This only makes sense to me if you ask to participate development and try to join forces.
We're currently about to push our changes.
There will also be a D7 version soon with the new pattern.
lotyrin, I'll be in denver and i'd be happy to discuss the current state with you.
#3
Automatically closed -- issue fixed for 2 weeks with no activity.