I don't think anybody wants to force (or can force) you to use a different name, but it is being pointed out that there exists a piece of work which is already using that name (even if slightly different case). I don't think anybody is implying that you intentionally took an already-in-use name, but the basic fact is that it is in use. Using that name may create confusion amongst people talking about either piece of work, and may conflict if the same name is used in various contexts, including a gem name. It seems to me the polite thing would be to choose a different name and cede the name to the existing, older piece of work. Asking that the existing watirspec change its name in the future to avoid conflict with yours does not seem reasonable. But, ultimately it is your own decision to make I think.
On Wed, Apr 7, 2010 at 11:23, Jarmo Pertman <jarm...@gmail.com> wrote: > Actually i didn't know about WatirCraft either. I know that i have > heard about it, but i thought that it is doing something else... It is > indeed somehow similar to my gem and i have also (maybe) a plan to add > Cucumber support... i mean, there's not much to add as a support > except just an additional dependency and require statement :P Anyway, > ideas seem to be somehow similar indeed. > > But about the name. Since i didn't know anything (i swear!) about the > existence of WatirSpec name and didn't find anything on rubygems.org, > then that's why i decided to pick a name called WatiRspec (notice that > there's also difference in case). Since i didn't steal the name or > didn't do anything else bad intentionally, then i feel that it would > not be fair against me if you or someone else would force me to change > the name because of these reasons. I'm not sure that name conflict can > happen on rubygems... So, if Jari or someone else decides to release a > gem with already existing name, then i guess that they should be the > ones to change their gem's name. I don't see any other solutions here > at the moment unfortunately. > > No hard feelings, i hope. > > Best regards, > Jarmo > > > On Apr 6, 9:47 pm, Charley Baker <charley.ba...@gmail.com> wrote: > > A simple gem might make sense or you can help work on the existing gems, > I > > haven't really thought about it too much but the WatirCraft gem does > > simplify things and add cucumber support. My thought in best to avoid, is > > that watirspec isn't currently gemified, but easily could be. So while > > there's not a name clash right now, the possibility exists that there may > be > > in the future. It makes sense to make Jari's current work into a gem. > > Thoughts? > > > > -c > > > > > > > > On Tue, Apr 6, 2010 at 12:32 PM, Jarmo Pertman <jarm...@gmail.com> > wrote: > > > Well, as i understood, then Taza just offers extra functionality and > > > in deep within Watir and RSpec is used for it. But as i already > > > mentioned, then WatiRspec is not doing much extra except combining > > > both of these tools. And this is enough for my work. > > > > > What did you mean about this "probably best to avoid that name for > > > now" exactly? > > > > > Jarmo > > > > > On Apr 6, 3:23 am, Charley Baker <charley.ba...@gmail.com> wrote: > > > > Hey Jarmo, > > > > > > No worries. Watirspec isn't a gem yet, but may be at some point, > > > > probably best to avoid that name for now. Taza's more complex to some > > > > degree, but the basics are fairly simple. Interested to hear more > about > > > your > > > > point of view and how you see it, or anyone else for that matter. Let > me > > > > know. :) > > > > > > Cheers, > > > > > > Charley Baker > > > > Lead Developer, Watir,http://watir.com > > > > QA Architect, Gap Inc Direct > > > > > > On Mon, Apr 5, 2010 at 7:26 AM, Jarmo Pertman <jarm...@gmail.com> > wrote: > > > > > Hi. > > > > > > > You are correct, i didn't know anything about these projects. But > as > > > > > far as i looked on Taza's documentation right now, then i can say > that > > > > > it is a completely different library. It might have a similar idea > at > > > > > some degree, but Taza seems to be just a lot more complex with all > > > > > those extra features, which are not needed for me. I don't plan to > > > > > make WatiRspec like that. WatiRspec's main idea is that it takes > RSpec > > > > > and Watir and just makes it easier to use both of these tools > together > > > > > by providing some helper methods and that's mainly it. > > > > > > > I haven't been very original in thinking of names, thus i named it > > > > > like Watir + RSpec = WatiRspec > > > > > > > Sorry, if i caused any troubles with that. > > > > > > > Jarmo > > > > > > > On Apr 3, 10:27 pm, Charley Baker <charley.ba...@gmail.com> wrote: > > > > > > How is this different from Taza? > > >http://github.com/charley/tazawhichdoes > > > > > > exactly the same sort of thing. watirspec is the name of Jari's > rspec > > > > > tests > > > > > > for celerity and watir, so despite the fact that it's not a gem > yet, > > > I'd > > > > > > cede that name to him. Let me know if I'm offbase, maybe you > didn't > > > know > > > > > > about these projects. :) I'd be happy to have you involved in > Taza. > > > > > > > > Cheers, > > > > > > > > Charley Baker > > > > > > Lead Developer, Watir,http://watir.com > > > > > > QA Architect, Gap Inc Direct > > > > > > > > On Fri, Apr 2, 2010 at 5:40 PM, Jarmo <jarm...@gmail.com> wrote: > > > > > > > Hello. > > > > > > > > > I just wanted to let you know that I've released my first gem > > > called > > > > > > > WatiRspec. It does combine Watir and RSpec for you so you could > > > start > > > > > > > testing easily and write less code. I created it because i > noticed > > > > > > > that i'm reinventing these things all the time if new > > > client/project > > > > > > > is started. Now it's much easier. Just enter few commands and > i'm > > > > > > > ready to start. I'm going to use it in my everyday work. It is > > > going > > > > > > > to be part of my diploma thesis also. > > > > > > > > > It is very fresh library, so it's possible that something > doesn't > > > work > > > > > > > as it should - although i have written tests for my code :) > > > > > > > > > What do you think? Do you see any shortages? Might it be useful > for > > > you > > > > > at > > > > > > > all? > > > > > > > > > You can read more about it athttp://github.com/jarmo/WatiRspec > > > > > > > > > You can read about some of the principles (haven't had the time > to > > > > > > > update it yet with newest ideas) from my blog too: > > > > > > >http://www.itreallymatters.net > > > > > > > > > Jarmo Pertman > > > > > > > > > -- > > > > > > > Before posting, please readhttp://watir.com/support. In short: > > > search > > > > > > > before you ask, be nice. > > > > > > > > > You received this message because you are subscribed to > > > > > > >http://groups.google.com/group/watir-general > > > > > > > To post: watir-general@googlegroups.com > > > > > > > > > To unsubscribe, reply using "remove me" as the subject. > > > > > > > -- > > > > > Before posting, please readhttp://watir.com/support. In short: > search > > > > > before you ask, be nice. > > > > > > > You received this message because you are subscribed to > > > > >http://groups.google.com/group/watir-general > > > > > To post: watir-general@googlegroups.com > > > > > -- > > > Before posting, please readhttp://watir.com/support. In short: search > > > before you ask, be nice. > > > > > You received this message because you are subscribed to > > >http://groups.google.com/group/watir-general > > > To post: watir-general@googlegroups.com > > -- > Before posting, please read http://watir.com/support. In short: search > before you ask, be nice. > > You received this message because you are subscribed to > http://groups.google.com/group/watir-general > To post: watir-general@googlegroups.com > -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. You received this message because you are subscribed to http://groups.google.com/group/watir-general To post: watir-general@googlegroups.com
