> On Thu, Mar 3, 2011 at 16:12, Andreas Stieger
> <andreas.stieger_at_gmx.de> wrote:
> > Hi,
> >
> > On 03/03/2011 15:04, Karl Falconer wrote:
> >
> >> Is the problem with the name is that it is too similar to the
> >> TortoiseSVN name or a semantic meaning of the name and what the
> plugin
> >> does? Is there a reason why TortoiseMantis (which is currently
> featured)
> >> is acceptable and TortoiseSV1 not?
> >
> >
> > I am the developer of TortoiseMantis (although it's on hold right
> now
> > due to other project commitments). If there is an issue with that
> name
> > as well I would certainly rectify it.
>
> Well, I would prefer if you would not name it 'tortoise'. Because
> people referring to "tortoise clients" usually mean a version
> control
> client integrated into the windows shell. Not a plugin for a
> tortoise
> client.
>
> For example:
> TortoiseCVS
> TortoiseSVN
> TortoiseHg
> TortoiseGit
> TortoiseBzr
> ...
>
> are all 'real' tortoise clients.
> TortoiseMantis is not. That only adds to confusion. Doesn't help
> your
> plugin nor the tortoise clients.
>
> Of course we don't own the right for the name "tortoise", not even
> for
> "TortoiseSVN" legally so all we can do is ask...
It certainly seems a reasonable request since this is a nice naming conversion.
Perhaps you can suggest a naming convention for source control plug ins so people...
1. Know it is a source control plug in
2. know is it a plug in for tortoise.
Can the same source control plugin be used for TortoiseSVN and TortioseGit for example?
Do all the tortoise clients share a common code base wrt dealing with the shell, etc?
BOb
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2709330
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-03-03 16:44:25 CET