From: Felipe L. <ff...@gm...> - 2005-09-16 19:10:15
|
I knew Yves would not agree...I think he is right....His arguments make=20 sense...Let's move on and forget it...We should be worried about our code,= =20 not about its (already nice) name. Besides that, we (yves) does have some rights over the name, as he created= =20 it from scratch..Not sure if Firman knows about it, but some time ago we ha= d=20 a problem w/ other project that STILL (I guess) carries the same name of=20 ours. If you check our forum @ sf.net <http://sf.net>, you will see people= =20 asking about the other project...Changing phpSQLiteAdmin name is like if we= =20 give up our rights. And I disagree when Yves says ppl don't mind what language is used by the= =20 project....(I would never run an ASP app.....I might consider run a k* app= =20 sometime in the future though :-P) Anyway....Lets move on Let's focus our time on coding, please Felipe Fontana Lopes On 9/16/05, Firman Wandayandi <fi...@gm...> wrote:=20 >=20 > On 9/16/05, Yves Glodt <yg...@mi...> wrote: > > Firman Wandayandi wrote: > > > On 9/16/05, Felipe Lopes <ff...@gm...> wrote: > > > > > >>We might just cut off the "PHP"....SQLiteAdmin...Or=20 > WebSQLiteAdmin...Well > > >>Don't know actually.... > > >> > > > > > > > > > Here the possibly names: > > > 1. SQLiteAdmin (Felipe) > > > 2. WebSQLiteAdmin (Felipe) > > > 3. SQLiteWorks (Me) > > > > > > > > >> Yves, What you think about it? I mean, about changing your project's > > >>name....You haven't said anything about it yet....Your word is the on= e=20 > that > > >>really matters here ;-) > > >> > > > > > > > > > Yeah, Felipe right. Tell us your comments Yves. > > > > > > Regards, > > > > Hi (and sorry for being late...), > > > > I have been quite busy at work these days and must admit I did not spen= d > > too much time on this yet... > > > > So far, honestly, I can not really share the renaming-enthusiasm... If > > we would apply the same rule than we would apply for the "PHP" part in > > the name, we would also have to remove sqlite from the name... no? > > >=20 > No, we shouldn't remove the "SQLite" part. >=20 > > I understand that for the phpsqliteadmin user it does not matter in wha= t > > language it is written. > > > > But, on the other hand, on unix, traditionally many softwares include > > the name (or parts of) of the tool(kit)s they have been written in > > (qcad, gtkam, gtk-gnutella, qtparted, wxprojman, php*, g*, k*, etc...) > > > > Apart of that, renaming will cause work, which needs time, which whould > > be better invested in coding... (sorry I know I am the least-good place= d > > to speak about...) > > > > > > Comments...? > > > > >=20 > Yeah, I'm right to trust you Yves. I'm even never thought about our > cost if we renaming it and also about invested. >=20 > Now, I'm sure! I think we shouldn't rename this project, let's goes on > the phpSQLiteAdmin and beat the others. Everyone knew, that > phpSQLiteAdmin's bugs aren't PHP bugs anyway :-D. But we play the old > drama like phpMyAdmin, phpPgAdmin, phpOracleAdmin, php-nuke, phpWiki, > phpAuction, uh I don't want to tell all of them here :P, nevermind you > right Yves, I agreed! >=20 > Thanks Yves. > -- > Firman Wandayandi > Never Dreamt Before (http://php.hm/~firman/) >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or your ver= y > own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Phpsqliteadmin-devel mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpsqliteadmin-devel > |