I'm interested in shutting down
openqa.org similar to the gradual shut down I did for open
symphony.com (see the page there now if you want to see where I think openqa should end up).
In looking at the projects, I can confirm that pyWinAuto and Bromine have found new homes and have been using an alternative to the wiki for some time. We can remove them safely.
Jave Testing Commons doesn't have a new home, but it doesn't look like there has been any activity in 5+ years. I think we can drop it.
Selenium on Rails doesn't have a new home, but it appears the website has been broken for years and no one even noticed. Let's drop it.
Session Tester doesn't have a new home either and there hasn't been a release in almost 4 years and no post to the forums in almost just as long. I think we can drop it.
Frankenstein looks like it sort of moved to Github and hasn't been worked on it a couple years, but it still links to the wiki too (
https://github.com/vivekprahlad/frankenstein). The project seems pretty much inactive, but we should check with some ThoughtWorkers since I am finding more recent references to it around their Twist produt.
CubicTest does not have a new home and still links to the wiki, but the project is claimed to be dead and not actively worked out. Not sure what we should do here…
Probably the easiest thing to do is to email the owners of all these projects and tell them we're shutting down OpenQA in 3 months and see if anyone objects. Sound like a plan?