On Mon, Mar 31, 2003 at 08:42:06AM -0800, Eric C. Weaver wrote: > Tim Bunce wrote: > >On Mon, Mar 31, 2003 at 07:24:55AM -0800, Eric C. Weaver wrote: > > > >>Tim Bunce wrote: > >> > >>>We have Oracle::* and others. An Informix::* namespace seems > >>>best for this. > >> > >>Too late. Besides, I *already* renamed it from DBIx::Perform to make > >>AURIJUS happy. > >> > >> > >>>The DBIx::* space is best for modules that are not database specific. > >> > >>Actually, this is not database specific. I've been using it on Postgres > >>during development. > > > > > >Putting Informix in the name will mean most non-Informix users > >will ignore the module. > > > Would you care to take it back out again? I'll give you developer and > admin access on Sourceforge and Freshmeat. > > > >>The only reason AURIJUS wanted it called DBIx::Informix::Perform was that > >>"PERFORM" was a trademark of Informix and he wanted to be clear of > >>trademark issues. > > > > > >I didn't see that discussion (sadly have have little time to read > >[EMAIL PROTECTED] these days). > > Actually I don't think it made it onto <modules>; he responded to my > indexing/namespace request. > > > >I believe there is no need to "clarify" trademark issues in module > >names. (In the same way that domain names that include a tradename > >don't have to include the owner of the trademark.) All that's > >needed is for the module *documentation* to clarify this (README + pod). > > Look, you and AURIJUS fight that out, okay? I have to be on to other > things now. I've already changed the name twice and I'm not going to > change it again just now. > > Sorry I'm being so grumpy, but I have a lot of other things to do at this > point.
I quite understand. My comments were as much directed towards [EMAIL PROTECTED] [CC'd] as to you. I wasn't suggesting that you had to change the name. Naturally now the name has been approved we'll all live with it if you can't find the time to change it. No problem. It's up to [EMAIL PROTECTED] to avoid it setting any precedents. Tim.
