Inactive or needs documentation?

[maxlinc]

I've got some simple MAB I'd like to do for a non-critical project.

Whiplash still says not to use yet, and there's been no activity for a few months. Is there a beta in the near future or have you guys abandoned it?

[bguthrie]

The project was created and maintained by Aaron Swartz's team at
ThoughtWorks. Since his passing, that team has been dissolved, I've left
the firm, and the project doesn't have a formal maintainer. I'd still like
to work on it, but I might need to coordinate contributions with them.
Anyone else have any insight?

On Tue, Mar 26, 2013 at 1:07 AM, maxlinc notifications@github.com wrote:

I've got some simple MAB I'd like to do for a non-critical project.

Whiplash still says not to use yet, and there's been no activity for a few
months. Is there a beta in the near future or have you guys abandoned it?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1
.

[manderdev]

I too have left the firm and haven't been involved in it for quite a while.
But I don't think the README is saying not to use it. My guess it "don't
usage yet" was a note to the team not to bother writing up usage notes yet,
since it would have been in flux at that point.
We were using it quite happily with the victorykit project, though -- I
don't see any reason you couldn't use it if you don't mind it being
unsupported.

Bear in mind it was written to support and was extracted from the
github.com/victorykit/victorykit project, so it could still be tied to some
assumptions emanating from there (though I think we weeded those out).
Similarly, I know we'd discussed pulling some of the admin dashboard views
out of victorykit and white-labelling them to support use with other
projects that might want to use whiplash.
See github.com/victorykit/victorykit/tree/master/app/views/admin for
current implementation of that.

On Tue, Mar 26, 2013 at 4:39 PM, Brian Guthrie notifications@github.comwrote:

The project was created and maintained by Aaron Swartz's team at
ThoughtWorks. Since his passing, that team has been dissolved, I've left
the firm, and the project doesn't have a formal maintainer. I'd still like
to work on it, but I might need to coordinate contributions with them.
Anyone else have any insight?

On Tue, Mar 26, 2013 at 1:07 AM, maxlinc notifications@github.com
wrote:

I've got some simple MAB I'd like to do for a non-critical project.

Whiplash still says not to use yet, and there's been no activity for a
few
months. Is there a beta in the near future or have you guys abandoned
it?

—
Reply to this email directly or view it on GitHub<
https://github.com/victorykit/whiplash/issues/1>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-15493429
.

[maxlinc]

Good to know.

I noticed that split (popular split testing framework including a dashboard) has added a whiplash algorithm inspired by this project:
https://github.com/andrew/split/blob/master/lib/split/algorithms/whiplash.rb

So I'm gonna go with split for now. Unfortunately the first time I tried whiplash in split it crashed. After that it worked but the report looked off. So I'm still sticking with split but I'm assuming the whiplash support isn't production-ready yet.

I'll keep an eye here to see if someone decides to push this project forward. If not, perhaps you could integrate or merge with split?

[bguthrie]

I believe @woodhull is responsible for porting the Whiplash algorithm into Split but I haven't done any testing of it there myself. Split is definitely more polished, so I'd start there.

[woodhull]

I did initial work to port it and make Split more generic, but am not actively using yet (although intend to).

It was a thing I hacked on when I had some free time over the holidays.

I'm very much interested in there being a good MAB implementation somewhere in ruby, and split seemed to be the place with the most momentum in the community for a/b testing.