It looks as if your *actual* problem is figuring how to motivate one employee to get in the version control loop. Allow me to suggest some possible motivation techniques: - Money talks
- If you are management, or can get management's backing offer to hire an intern who's job it is to simply check his code in for 1/2 the intern's salary. (ie. he's giving up half the intern's salary out of his own salary).
- If you aren't management, offer to check his code in for him at $15 per instance, payable before checkin.
- If he's not going to check things in correctly anyway, make it a process. He FTP's the files to the test server, someone else tests his code, provides feedback and if successful, the tester checks in the code
-Scott
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|