[p4] Introduction slides
SBougon at ariba.com
Thu Oct 19 14:52:51 PDT 2006
Thanks David, Teresa, Robert, Jay and all.
From: Weintraub, David [mailto:david.weintraub at bofasecurities.com]
Sent: Thursday, October 19, 2006 2:51 PM
To: Steven Bougon; Perforce Users
Subject: RE: [p4] Introduction slides
I don't want to knock marketing people as "dumb" and "technically
backwards", but these are marketing people...
I once taught computer classes to non-techs. Our *ADVANCED* Microsoft
Word class included:
* How to use tables
* Setting up a Table of Contents
* Using Paragraph Formats
Getting to my point. Leave out "3) How does it work". This is much more
information than they can handle. Besides, my highly technical
developers are barely interested in how Perforce works, so why would
these people care?
Keep things very simple: For the installation, setup one basic client
for each user. This client should be pointing to the root of where all
of their files are stored. Tech Note #68 about configuring automated
<http://www.perforce.com/perforce/technotes/note068.html>. The idea is
they simply double click on the install icon, and everything is setup
for them: The port, client, user ID, etc. No teaching them how to set
P4PORT. No how to create a client.
Make sure that p4win is setup so the "Client View of Depot" is the
default view. To get a particular file, they browse through the tree in
the left-hand pane, find the file, right click on it, and select "Edit".
If need be, p4win will ask if they want to "sync to the head revision"
(hint: click "Yes"), and Perforce will checkout the file and bring it up
in Word or Excel for them.
Forget about changelists. Show them how to right-click on the file in
the left hand pane (Client View of Depot) and select "Submit" from
there. They aren't programmers, and don't need to worry about
In other words, they should be able to find a file in the Client View,
click on edit to edit the file, and click on Submit to submit the file.
That's lesson #1.
Lesson #2 is adding and deleting files from source control
Lesson #3 should be looking at file history, and being able to see who
has what files checked out and how do I know what files are checked out?
That's it. This will take you (with a class of 10 users) about an hour
to go through.
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Steven Bougon
Sent: Thursday, October 19, 2006 2:48 PM
To: Perforce Users
Subject: [p4] Introduction slides
I was asked to hold a brown bag on "Perforce for Dummies" for
non-technical folks are our company. (read: Marketing folks are going to
check in some .xls files)
They need to know how to:
- set up p4win
- what and why SCMS
- how to checkin/checkout
- go through the revision history.
So, it's really a introduction on SCMS, with hands on P4Win
And yes, I already pointed them to the very good
but I still need to produce some slides
So, before writing my own perforce4dummies.ppt, I wanted to ask if one
of you is aware of such material available somewhere in the public area
of the perforce.com site ?
I searched and could not find it. Let me know if you know about
thanks a lot,
PS: I'm thinking about the following
1) What's wrong with Windows Explorer ?
2) Perforce allows you to:
* keep an history of a file change
* retrieve a specific file revision
* lock a file
* knows who is editing the file at the same time
* have permissions set on some directories
* receive an email everytime somebody modifies a certain file
3) How does it work (Perforce server, Metadata in a DB)
4) How to set up Perforce
* request a user id/passwd
* crtl+o to enter the good setting
5) Get started:
* sync some files
* edit one (description)
* receive email notification
* command line :-)
* (internal) http://devweb and //xxx/yyy/... ????
* windord and excel p4 plugin
7) DO and DON't
* never delete a file, or change a file permission via Windows
* always use p4win to delete, edit a file
* don't sync //xxx/yyy/... (couple if Gig) :-)
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user