On Thu, Nov 26, 2009 at 3:08 AM, Željko Filipin < [email protected]> wrote:
> The more I think about it, the more I see Watir is not a typical Openqa > project. For example, Jira admins are the people for commit access to svn > repository. That makes no sense for us, since our code is no Github. > Open QA is an odd thing. The only "typical" OpenQA project is Selenium. Everything else is kinda an afterthought. But I don't think we have any Jira admins. I was talking to Jeff about this yesterday and he was going to talk to Patrick. I think the Selenium people have more access to administer and customize Jira than we do, simply by virtue of the fact that Patrick is part of the Selenium team. But I think that's something we can work on. For example, someone, presumably Patrick, recently made "environment" a required field. I assume this was done because of a decision made by the Selenium team. (This policy makes sense for tickets, but is annoying because I can't retarget a ticket for a different release without changing this field.) Should I ask Patrick to create ChromeWatir and SafariWatir Jira projects? > I think that's the right direction, but I think the people who are running these projects should have a say. Sai? Tom? One thing that we will be able to do, with all the projects on OpenQA, is easily forward tickets between projects. Bret -- Bret Pettichord Lead Developer, Watir, www.watir.com Blog, www.io.com/~wazmo/blog Twitter, www.twitter.com/bpettichord
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
