[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: TortoiseSV1 - A New Issue Tracker Plugin

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Fri, 4 Mar 2011 10:53:50 -0500

How about Vurtle One ... "a Tortiose plugin for VersionOne" ;)


From: Karl Falconer [mailto:karl.falconer_at_falconerdevelopment.com]
Sent: Thursday, March 03, 2011 8:22 PM
To: users_at_tortoisesvn.tigris.org
Subject: Re: TortoiseSV1 - A New Issue Tracker Plugin


That name works for me. I'll begin making the changes.


On Thu, Mar 3, 2011 at 1:06 PM, Stefan K√ľng <tortoisesvn_at_gmail.com<mailto:tortoisesvn_at_gmail.com>> wrote:
On 03.03.2011 18:53, Andy Levy wrote:
> On Thu, Mar 3, 2011 at 12:21, Karl Falconer
> <karl.falconer_at_falconerdevelopment.com<mailto:karl.falconer_at_falconerdevelopment.com>> wrote:
>> @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
>> changeset #.
>> @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.
> How about TortoiseVOne then? The "S" in your current name doesn't
> match any of the other naming conventions and only alters TortoiseSVN
> by one character, which will both be sources for confusion. And it'll
> be similar to TortoiseMantis, which serves a similar function.
As I said, I'd rather have the plugins use something else than
"tortoiseXXXX" as the name.

A good base name for plugins would be "Turtle" and variations of that.
For example, "Gurtle" is the plugin for Google Code.

So how about "Murtle" for the Mantis plugin and "SVurtle" for the SV1


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org<mailto:users-unsubscribe_at_tortoisesvn.tigris.org>].
Karl Falconer, Software Engineer
www.falconerdevelopment.com<http://www.falconerdevelopment.com> | karl.falconer@falconerdevelopment.com<mailto:karl.falconer@falconerdevelopment.com>
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-03-04 16:53:57 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.