[Selenium-devel] selenium.thoughtworks.com is back online. Sorry for the outage.

I was out all day today and wasn't free to take care of this myself. I did forward this issue to our internal support queue this morning when I last checked my email... But alas, the issue was kicked back to me (found that out about an hour ago.) Anyway... the good news is I was able to log in t

RE: [Selenium-devel] OpenQA

I agree. There is a wiki space set up at wiki.openqa.org, and since there isn't a ton of content, perhaps we can just copy it over by hand? _ Patrick Lightbody Professional Services Jive Software [EMAIL PROTECTED] www.jivesoftware.com 317 SW Alder, Ste 500 Portland, OR 97204 ph (5

RE: [Selenium-devel] OpenQA

How about the various pages from the current Confluence site for Selenium ()? The Getting Started page has a bunch of links to my tutorials, and I think it would be worth moving it over to OpenQA. Grig --- Patrick Lightbody <[EMAIL PROT

RE: [Selenium-devel] OpenQA

Absolutely. The merged project is called Selenium IDE and the code has been checked in to OpenQA: http://svn.openqa.org/fisheye/viewrep/selenium-ide As for OpenQA as a whole, last night I did the initial push to bring over the JIRA account, user accounts, and website. Next step is to bring over t

RE: [Selenium-devel] Fw: Is the selenium web site down?

I noticed the same thing last night. I don't believe it has anything to do with OpenQA. _ Patrick Lightbody Professional Services Jive Software [EMAIL PROTECTED] www.jivesoftware.com 317 SW Alder, Ste 500 Portland, OR 97204 ph (503) 295-6552 fx (503) 961-1047 -Original Messa

[Selenium-devel] Fw: Is the selenium web site down?

Users see the following at selenium.thoughtworks.com: > > Bad Gateway > The proxy server received an invalid response from an upstream server. > > Apache/2.0.51 (Fedora) Server at selenium.thoughtworks.com Port 80 What's up? Does someone need to go into the server and restart the server... or i

Re: [Selenium-devel] What are we waiting for?

Yes, this problem disturbs me too. I think waiting limitation with timeout is appropriable. It will good if we'll have command like setWaitingTime for case when default timeout is not appropriate. Bret Pettichord wrote: At 04:28 AM 11/29/2005, Mike Williams wrote: Bret Pettichord wrote: