Hi, Bob,

From: Bob Zhu [mailto:b...@fortinet.com]

> We definitely don't wan to do anything client side since that would be a
> nightmare to manage afterwards.
> Upper management essentially wants this reminder everytime they do a
> checkout.  Almost like a disclaimer that they have to agree to before
> continuing.

To be honest, I think your upper management should re-think this detail of 
their decision.

First, anchoring everything at the "checkout" operation is a bit too specific - 
what about operations like "export", "update" or "switch" which can also bring 
in new data which has not been in the local working copy before?

And second, having a high hurdle before a "checkout" will lead to teammates 
exchanging working copies directly, keeping zip-files of those "on stock" in 
case they "need it again later", and other attempts to circumvent it.

One possible solution I could think of is that they need to use a different 
user name for that specific repository - e. G. instead of "foobar", they need 
to enter "foobar-I-know-it-is-confidental" using the same password as for their 
normal account.

Another possibility would be to hide the server behind a proxy, and the proxy 
requires a separate proxy authentication.

But none of them are implemented "out of the box" with stock SVN.

Best regards

Markus Schaber

CODESYS® a trademark of 3S-Smart Software Solutions GmbH

Inspiring Automation Solutions

3S-Smart Software Solutions GmbH
Dipl.-Inf. Markus Schaber | Product Development Core Technology
Memminger Str. 151 | 87439 Kempten | Germany
Tel. +49-831-54031-979 | Fax +49-831-54031-50

E-Mail: m.scha...@codesys.com | Web: http://www.codesys.com | CODESYS store: 
http://store.codesys.com
CODESYS forum: http://forum.codesys.com

Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade 
register: Kempten HRB 6186 | Tax ID No.: DE 167014915

This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received
this e-mail in error) please notify the sender immediately and destroy this 
e-mail. Any unauthorised copying, disclosure
or distribution of the material in this e-mail is strictly forbidden.

Reply via email to