Manual code management practices

[Peter Bateman]

This along Brian's idea.

The script could change the owner of file ( see chown command ) to be the 
person checking
out the code.
then a ls -l of the repository would show you who has the file.
Of course, there would have to be a reversal process when
the user checks it backin.

Regards,
Peter


>many thanks all for the 31 file limit replies ( I forgot to include and not 
>views/cursors ).
>
>as for the repository approach, simply write a script that appends the 
>userid and timestamp to the original source code file name after a copy is 
>made in the users directory; this way a complete history is preserved - if 
>anyone bypasses using the script to log out source code - SACK THEM ! :)
>
>P.S. ideally, regular meetings to discuss who will be working on what 
>source code helps.
>
>regards Bri,
>
>
>
>
>>From: "Olmos, Fernando (Sericon at Alcoa)" <Fernando.Olmos@alcoa.com.au>
>>To: <powerh-l@lists.sowder.com>
>>Subject: Manual code management practices
>>Date: Thu, 19 May 2005 09:36:25 +1000
>>
>>Hi everyone.
>>
>>I recently re-joined the PH list due to a larger than expected volume of
>>work requiring my PH skills.
>>
>>Just one question, which is baffling a lot of my clients at the moment.
>>
>>Code management:
>>
>>*	What practices are being used?
>>*	What tools are being used?
>>*	Any DOs and DONTs?
>>
>>My client is running Powerhouse, in a HP9000 Unix box, and has recently
>>hired a few contractors and myself to do some work which will require us
>>to share code, and keep it all seamless without people overwriting other
>>people's work.
>>
>>Currently we use a "repository" method which is to keep the code in a
>>central location and ONLY pull it out of there if the file is not listed
>>in a "holding location" elsewhere. If the code is in the holding
>>location then it means someone is using it, and so the developer has to
>>email/communicate with the team to find out who is using it, why and
>>discuss how to "share" the program.
>>
>>Unfortunately with this system, as you all know, it's heavily reliant on
>>human "good will" and control. If someone forgets to pull out the source
>>code from the holding area or at least comment it to say this is no
>>longer required, then other developers will be wasting time chasing
>>people or making assumptions (because some people just don't like to
>>talk!) and start using the program anyway.
>>
>>Is there a manual system that is better than the above? We are trying to
>>stay away from using specific code management tools like CM or VSS due
>>to cost and timing spent on installation, training, management, etc.
>>
>>Thanks guys.
>>
>> > Fernando J. Olmos
>> > Melbourne
>> > +61 3 9629-9444
>> > Software Consultant (Information Services - Alcoa Australia)
>> >
>> >
>
>_________________________________________________________________
>It's fast, it's easy and it's free. Get MSN Messenger 7.0 today! 
>http://messenger.msn.co.uk
>
>--
>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Mailing list: powerh-l@lists.sowder.com
>Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
>Unsubscribe: "unsubscribe &lt;password&gt;" in message body to 
>powerh-l-request@lists.sowder.com
>http://lists.sowder.com/mailman/listinfo/powerh-l
>This list is closed, thus to post to the list you must be a subscriber.

_________________________________________________________________
Take advantage of powerful junk e-mail filters built on patented Microsoft® 
SmartScreen Technology. 
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines 
  Start enjoying all the benefits of MSN® Premium right now and get the 
first two months FREE*.