Re: [Wtr-general] Disclaimer
Bret, Energised by the support I am getting from this group, I also would like to contribute in what ever small way I could with the documentation for 1.5 or later. Raghunath From: "Jason Alexander" [EMAIL PROTECTED]Reply-To: wtr-general@rubyforge.orgTo: wtr-general@rubyforge.orgSubject: Re: [Wtr-general] DisclaimerDate: Tue, 19 Sep 2006 15:51:48 -0400Bret,I'd love to volunteer with documentation efforts. While I'm not quiteadept enough, yet, to help sling code within the main codebranch, I canwrite documentation and I realize that this is probably one of thebigger needs.What are your plans for 1.5? How can I help? :)Thanks,-JasonJason L. Alexander Chief Technology Officer Telligent Systems, Inc. http://telligent.com w: 214.420.1333 http://JasonA.net-Original Message-From: [EMAIL PROTECTED][mailto:[EMAIL PROTECTED] On Behalf Of Bret PettichordSent: Tuesday, September 19, 2006 1:17 PMTo: wtr-general@rubyforge.orgSubject: Re: [Wtr-general] DisclaimerI just realized that i didn't write what i meant to write. No wonder somany people were agreeing with me.What I meant to say was that 1.4 is ALSO incompletely documented, etc.We've seen a fair amount of sarcasm and indignation on this list latelyand it seems to be directed at the difficulty of using Watir 1.4. Atfirst i was offended, but with time, i realized that it is coming fromenough different people that i have to assume that what we are seeinghere is only the tip of an iceberg -- that lots of people start usingWatir with expectations that it will be far easier than it actually is.I want to proactively reset these expectations.I think i also want to say something about this being a 100% Volunteereffort.I'll draft a new blurb shortly. Thanks for the comments. I also haveplans to significantly improve Watir documentation, but i plan to havethis be based on Watir 1.5 and therefore the 1.5 project needs to moveforward first.BretCharley Baker wrote: I completely agree. People have to understand that while there are a lot of great reasons to use 1.5, it is still a work in progress and does take a higher level of skill and for lack of better terms, personal discovery, to use. -Charley On 9/18/06, Bret Pettichord [EMAIL PROTECTED] wrote: Based on recent feedback, i am thinking that we need to add the following information to the main Watir webpage at wtr.rubyforge.org: Watir 1.5 is currently under active development. However, it remains poorly documented. Users often have to read through a confusing email archive to find solutions to commonproblems. They also should understand HTML. Although developers understand it easily enough, testers are often confused and frustrated by it. If you decide to use it anyway, you've been warned. Don't complainto us about it. Comments please. I'm not joking. Bret ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general ___Wtr-general mailing listWtr-general@rubyforge.orghttp://rubyforge.org/mailman/listinfo/wtr-general___Wtr-general mailing listWtr-general@rubyforge.orghttp://rubyforge.org/mailman/listinfo/wtr-general ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] Disclaimer
+1 Zeljko On 9/19/06, Matt Johnson [EMAIL PROTECTED] wrote: Bret, this seems like a reasonable message to put on that page. ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] Disclaimer
I completely agree. People have to understand that while there are a lot of great reasons to use 1.5, it is still a work in progress and does take a higher level of skill and for lack of better terms, personal discovery, to use. -Charley On 9/18/06, Bret Pettichord [EMAIL PROTECTED] wrote: Based on recent feedback, i am thinking that we need to add the following information to the main Watir webpage at wtr.rubyforge.org: Watir 1.5 is currently under active development. However, it remains poorly documented. Users often have to read through a confusing email archive to find solutions to common problems. They also should understand HTML. Although developers understand it easily enough, testers are often confused and frustrated by it. If you decide to use it anyway, you've been warned. Don't complain to us about it. Comments please. I'm not joking. Bret ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] Disclaimer
I think that this is reasonable. People should be aware that nothing come free out of the box with Watir. The richer the background, the more one can reap from it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bret Pettichord Sent: Monday, September 18, 2006 4:58 PM To: wtr-general@rubyforge.org Subject: [Wtr-general] Disclaimer Based on recent feedback, i am thinking that we need to add the following information to the main Watir webpage at wtr.rubyforge.org: Watir 1.5 is currently under active development. However, it remains poorly documented. Users often have to read through a confusing email archive to find solutions to common problems. They also should understand HTML. Although developers understand it easily enough, testers are often confused and frustrated by it. If you decide to use it anyway, you've been warned. Don't complain to us about it. Comments please. I'm not joking. Bret ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.12.4/449 - Release Date: 9/15/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.12.5/450 - Release Date: 9/18/2006 ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] Disclaimer
I just realized that i didn't write what i meant to write. No wonder so many people were agreeing with me. What I meant to say was that 1.4 is ALSO incompletely documented, etc. We've seen a fair amount of sarcasm and indignation on this list lately and it seems to be directed at the difficulty of using Watir 1.4. At first i was offended, but with time, i realized that it is coming from enough different people that i have to assume that what we are seeing here is only the tip of an iceberg -- that lots of people start using Watir with expectations that it will be far easier than it actually is. I want to proactively reset these expectations. I think i also want to say something about this being a 100% Volunteer effort. I'll draft a new blurb shortly. Thanks for the comments. I also have plans to significantly improve Watir documentation, but i plan to have this be based on Watir 1.5 and therefore the 1.5 project needs to move forward first. Bret Charley Baker wrote: I completely agree. People have to understand that while there are a lot of great reasons to use 1.5, it is still a work in progress and does take a higher level of skill and for lack of better terms, personal discovery, to use. -Charley On 9/18/06, Bret Pettichord [EMAIL PROTECTED] wrote: Based on recent feedback, i am thinking that we need to add the following information to the main Watir webpage at wtr.rubyforge.org: Watir 1.5 is currently under active development. However, it remains poorly documented. Users often have to read through a confusing email archive to find solutions to common problems. They also should understand HTML. Although developers understand it easily enough, testers are often confused and frustrated by it. If you decide to use it anyway, you've been warned. Don't complain to us about it. Comments please. I'm not joking. Bret ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] Disclaimer
Bret, I'd love to volunteer with documentation efforts. While I'm not quite adept enough, yet, to help sling code within the main codebranch, I can write documentation and I realize that this is probably one of the bigger needs. What are your plans for 1.5? How can I help? :) Thanks, -Jason Jason L. AlexanderChief Technology Officer Telligent Systems, Inc. http://telligent.com w: 214.420.1333 http://JasonA.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bret Pettichord Sent: Tuesday, September 19, 2006 1:17 PM To: wtr-general@rubyforge.org Subject: Re: [Wtr-general] Disclaimer I just realized that i didn't write what i meant to write. No wonder so many people were agreeing with me. What I meant to say was that 1.4 is ALSO incompletely documented, etc. We've seen a fair amount of sarcasm and indignation on this list lately and it seems to be directed at the difficulty of using Watir 1.4. At first i was offended, but with time, i realized that it is coming from enough different people that i have to assume that what we are seeing here is only the tip of an iceberg -- that lots of people start using Watir with expectations that it will be far easier than it actually is. I want to proactively reset these expectations. I think i also want to say something about this being a 100% Volunteer effort. I'll draft a new blurb shortly. Thanks for the comments. I also have plans to significantly improve Watir documentation, but i plan to have this be based on Watir 1.5 and therefore the 1.5 project needs to move forward first. Bret Charley Baker wrote: I completely agree. People have to understand that while there are a lot of great reasons to use 1.5, it is still a work in progress and does take a higher level of skill and for lack of better terms, personal discovery, to use. -Charley On 9/18/06, Bret Pettichord [EMAIL PROTECTED] wrote: Based on recent feedback, i am thinking that we need to add the following information to the main Watir webpage at wtr.rubyforge.org: Watir 1.5 is currently under active development. However, it remains poorly documented. Users often have to read through a confusing email archive to find solutions to common problems. They also should understand HTML. Although developers understand it easily enough, testers are often confused and frustrated by it. If you decide to use it anyway, you've been warned. Don't complain to us about it. Comments please. I'm not joking. Bret ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] Disclaimer
I would be open to helping with the documentation. I think part of the effort is not just upgraded documentation, but the organizational perspective fof the documentation. For a single example -- is the base or root for documentation the http://wtr.rubyforge.org/ site? As it happens, the user guide there recommends accessing the development version by doing Download the Watir tarball from the WTR RubyForge site (click download tarball) -- but that link is dead. Plus, I think we want people to follow the gem installation? Or -- is the root the http://wiki.openqa.org/display/WTR/Project+Home site? So there are two sources for documentation but they are not identical. The user guide talks about IRB, but FreeRIDE is distributed with the standard Ruby one click installer, and people are more likely to be developing WATIR scripts in that than in IRB I think -- the user guide could stand to be upgraded, and not just for WATIR specific material. The FAQ could stand to be strongly expanded, based on the number of questions asked and resolved in the openqa forum or mailing list archives. And so on. I am willing to help with the documentation as time permits. - Posted via Jive Forums http://forums.openqa.org/thread.jspa?threadID=4344messageID=12005#12005 ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
[Wtr-general] Disclaimer
Based on recent feedback, i am thinking that we need to add the following information to the main Watir webpage at wtr.rubyforge.org: Watir 1.5 is currently under active development. However, it remains poorly documented. Users often have to read through a confusing email archive to find solutions to common problems. They also should understand HTML. Although developers understand it easily enough, testers are often confused and frustrated by it. If you decide to use it anyway, you've been warned. Don't complain to us about it. Comments please. I'm not joking. Bret ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] Disclaimer
Bret Pettichord wrote: Based on recent feedback, i am thinking that we need to add the following information to the main Watir webpage at wtr.rubyforge.org: Watir 1.5 is currently under active development. However, it remains poorly documented. Users often have to read through a confusing email archive to find solutions to common problems. They also should understand HTML. Although developers understand it easily enough, testers are often confused and frustrated by it. If you decide to use it anyway, you've been warned. Don't complain to us about it. Comments please. I'm not joking. Bret ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general Bret, this seems like a reasonable message to put on that page. It would help people understand what they are getting into. -- Matt Johnson ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
