This seems like the proper place to have this discussion :)
What are the steps that we'll need to do to roll WebDriver into the Selenium codebase? Right now, there seem to be a few practical and logistical things that need doing (in no particular order):
* Change the package name. What should this be? "org.openqa.selenium"? "org.openqa.selenium.webdriver"?
* Decide where to host the code, wiki and forums. The obvious answer is here on OpenQA, but I do enjoy the lightweight environment of Google Code, particularly the wiki and the issue tracking
* Complete the WebDriver-backed Selenium implementation. This implies fixing at least three things in webdriver: handling alerts, allowing timeouts and providing a mechanism to inject javascript into a page
* Create a Selenium-backed WebDriver implementation. This may need some work on Selenium Core
* Create WebDriver bindings for ruby, python and .net (at least) Those are the ones I can manage (in that I know the language) but other bindings would be nice too
* Roll some of the webdriver features into the existing selenium rc. Suggestions include the new Firefox profile management "stuff" and the firefox socket listener
As we discuss this, I propose continuing development on google code, but to do the package rename ASAP (since that's the most disruptive thing for users)
Is there anything else that people think should be done? And is anyone interested in helping? :)
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.openqa.org/thread.jspa?threadID=13064&messageID=41320#41320---------------------------------------------------------------------
To unsubscribe, e-mail:
selenium-dev-unsubscribe@...
For additional commands, e-mail:
selenium-dev-help@...
