<HTML>
<HEAD>
<TITLE>Jeff A. Bowles, Perforce Consulting Partner</TITLE>
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#FFFFFF">
<a href="http://www.perforce.com/perforce/partners.html">
<img src="http://www.perforce.com/images/pcplogo.gif" border=none></a>
<h3>Jeff A. Bowles</h3>
<p>
Substantial experience in SCM and build environments on many
hardware platforms and software environments.
A subset includes most Unix platforms (Solaris, SunOS, HP-UX),
Windows/NT, and the Apple Macintosh.
Has automated SCM and build environments in those environments.
</p>
<p>
Has had exposure to other SCMs such as ClearCase, RCS/SCCS and SourceSafe,
but prefers to convert projects <u>from</u> other systems <u>to</u> Perforce,
not the other way around!</p>
<h3>Offerings</h3>
<p>
I do training for your development groups that are converting to Perforce<sup>TM</sup>.
Classes include:
<p>
<table border=1>
<tr>
<td>
<b>Introduction to Perforce</b>
<td>
<ul>
<li>
Covers setup of client, getting files ("p4 sync"),
editing/submitting changes;
<li>
Cursory glance at integration and merges, labels (using someone else's and making your own)
<li>
Includes GUI and command-line
</ul>
</tr>
<tr>
<td>
<b>Advanced Perforce Integration</b>
<td>
<ul>
<li>
Many examples of laying out codelines
<li>
examples of 'p4 integrate' in several flavors, with/without branch specifications
<li>
examines "p4 review" (post-submit trigger mechanism) and talks about different
things you can do to use this for varied needs
</ul>
</table>
(These courses run 2-3 hours, and can be tailored to describe your site.)
<h4>Contact Information</h4>
<blockquote>
Jeff A. Bowles<br>
590 Steiner St. #302<br>
San Francisco, CA 94117-2500<br>
<p>
Email: <a href="mailto:jab@pobox.com">jab@pobox.com</a>
<br>
Phone: 1.415.863.7070
</blockquote>
<hr>
Back to the <a href="http://www.perforce.com/perforce/partlist.html">
Perforce Consulting Partners Directory</a>
</body>
</html>