@Andy - To answer your question the short name V1 is in common usage to
refer to VersionOnes Agile Management application. So among the people that
would benefit from this plugin I don't believe there would be any confusion.
@Bob - Currently the work flow allows, the user to select multiple defects
that are assigned to the current user. After the selections are made, the
Defect Id and description is appended to the commit message. I'll be
starting on some of the other features that you've described in the coming
releases. I would definitely like to update the V1 defect/task with the
@Stefan - Thank you for explaining your concern, I was unaware of all the
other "Tortoise" projects in development, and can see your hesitation with
the current name of my project. I like the points that Bob brought up around
defining a naming convention around IssueTracker plugins. Do you have any
ideas around this? Also, it seems like the current Issue Tracker plugins are
compatible with both TortoiseSVN and TortoiseGIT, which would provide more
reason to alter my current naming to something more representative of the
fact that this plugin is Tortoise compatible.
On Thu, Mar 3, 2011 at 10:44 AM, Bob Archer <Bob.Archer_at_amsi.com> wrote:
> > 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
> Perhaps you can suggest a naming convention for source control plug ins so
> 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?
> To unsubscribe from this discussion, e-mail: [
--*Karl Falconer, Software Engineer*www.falconerdevelopment.com |
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-03-03 18:27:00 CET