On Wed, Jul 23, 2008 at 03:29, Gal Aviel <galaviel_at_yahoo.com> wrote:
> (1) Enabling this feature in TSVN only on a per-URL basis would
> solve "all repositories are the same" problem suggested before. You would
> only enter a list of URL on your local LAN to poll. If you don't
> enter a SF URL, your SF WC would not generate polling traffic.
That doesn't stop someone else from abusing it.
> (2) If Icon overlays are not technically possible (too few Windows slots) I'll
> settle for remote status to show in Windows Explorer's 'SVN Status' column.
> Just give me some sort of solution that I can use and that is integrated with
> TSVN. A 'Needs Update' text in the 'SVN Status' column is all I basically
> need (that's what we had with our previous VC tool).
You say you're against needing "additional configuration" but enabling
this column in Windows is additional configuration too.
> (3) CommitMonitor is a great tool however it is not integrated with TSVN, and
> requires a separate installation and post-install configuration. Installing
> it x15 times for each member of my team and configuring it is not a fun task.
> Also users don't understand why they need to install more than 1 program
> to do version control.
CommitMonitor isn't *needed* to do version control. *You want* it (or
something like it) so that people get notified, to make your
installation a push configuration instead of a pull. Most of my users
would consider it an annoyance to have icons changing so frequently.
Have you considered publishing RSS feeds and/or sending notification
emails in your post-commit to inform people that an update has been
made in the repository?
> (4) About the 2 seconds polling interval .. it was just an exaggeration
> in order to make the point that you don't need TSVN in order to kill the server.
No, but this sort of feature sure would make it easier.
> (5) Please understand that some users who use TSVN are not programmers,
> they are not proficient with VC tools and their methodology, they just
> want things to work ... they won't go out of their way to install a second
> product (CommitMonitor) and config. it and they don't understand
> and don't care about many points raised here which are implementation related.
This I don't get. The end-user doesn't have to understand everything
about Subversion and VC methodologies. But they do have to understand
how to use the tools required to do their jobs. I don't understand
desktop publishing, but I'm required to use MS Word to do my job. I
don't understand 90% of what Excel does, but I'm required to use that
to do my job.
If TSVN is required to do your job, I expect a basic level of
competence. Since it's not a "common" piece of software, an hour or
two of training and a user guide/manual with instructions for basic
daily tasks would go a long way. 90% of the time, users will not be
doing complex merges, conflict resolution (assuming you've got a sane
policy for svn:needs-lock), etc. They'll be doing update, commit, add,
delete and lock.
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-07-23 13:59:26 CEST