<HTML> <HEAD> <TITLE> Perforce Public Depot </TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF"> <CENTER> <P> <A NAME="toc"></A> <A HREF="http://www.perforce.com"> <IMG SRC="http://www.perforce.com/images/logo.gif" alt="Perforce" border=0></A> <H1> Welcome to the Perforce Public Depot </H1> <P> <TABLE BORDER=0><TR><TD> <B> <UL> <LI><A HREF="#aboutPerforce">About Perforce and the Public Depot </A> <LI><A HREF="#roadmap">The Depot Road Map </A> <LI><A HREF="#howtobrowse">How to Browse the Depot </A> <LI><A HREF="#howtocontrib">How to Contribute to the Depot </A> <LI><A HREF="#reviewdaemon">Subscribing to Change Notifications Via Email </A> </UL> </UL> </TABLE> </CENTER> <br> <br> <br> <!-- ------------------------------------------------------------ --> <P> <TABLE CELLSPACING=0 BORDER=0 WIDTH=100%><TR><TD BGCOLOR=FFCC66> <A NAME="aboutPerforce"></A> <H2>About Perforce and the Public Depot </H2> <TD WIDTH=5% BGCOLOR=FFCC66 ALIGN=RIGHT><FONT SIZE="-2"><A HREF="#toc"> Back to<BR>Table of<BR>Contents</A></TD></TR> </TABLE> <P> <TABLE BORDER=0 ALIGN=RIGHT WIDTH=25% CELLPADDING=10 CELLSPACING=5 > <TR> <TD WIDTH=16> </TD> <TD BGCOLOR="#DDDDDD" ALIGN=RIGHT><FONT SIZE=-1> One of Perforce's many distinguishing features is that it can be used over the internet to track shared software development. A Perforce server stores files in a <i>depot</i>, and developers all over the world can submit changes to the depot. The orderly management of file changes and merges is provided by the Perforce SCM system. </FONT> </TD></TR></TABLE> If you haven't heard about <b>Perforce, the Fast Software Configuration Management System</b>, head over to our <a href="http://www.perforce.com">home page</a> and read all about it. <P> We've set up this Public Depot to enable software developers outside of our company to contribute to the growing body of supporting programs and documentation of interest to our users. Among the first open source development projects we've initiated into the Public Depot are <a href="http://www.perforce.com/perforce/webkeeper.html"> WebKeeper</a>, an Apache Web Server module for accessing files in a Perforce depot, and <a href="http://www.perforce.com/jam/jam.html">Jam/MR</a>, a fully portable alternative to <i>make(1)</i>. <P> If you're interested in contributing to any of the software or documentation in the Public Depot, read on to find out how. Or, if you're simply interested in seeing how Perforce works, you'll find the Public Depot to be an accessible model of real, distributed, concurrent source management in action. <!-- ---------------------------------------------------------------- --> <P> <TABLE CELLSPACING=0 BORDER=0 WIDTH=100%><TR><TD BGCOLOR=FFCC66> <A NAME="roadmap"></A> <H2>The Depot Roadmap </H2> <TD WIDTH=5% BGCOLOR=FFCC66 ALIGN=RIGHT><FONT SIZE="-2"><A HREF="#toc"> Back to<BR>Table of<BR>Contents</A></TD></TR> </TABLE> <CENTER> <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0> <TR> <TD WIDTH=41> <TD WIDTH=41> <TD WIDTH=41> <TD WIDTH=41> <TD WIDTH=41> <TD WIDTH=41> <TD> <TR> <TD COLSPAN=2><FONT SIZE=4> <A HREF="http://public.perforce.com:8080/@ra=s@/public/"> public </A> <TD><IMG SRC=http://www.perforce.com/images/diag_bl.gif border=0> <TD> <TD> <TD> <TR> <TD><IMG SRC=http://www.perforce.com/images/diag_tr.gif BORDER=0> <TD><IMG SRC=http://www.perforce.com/images/diag_horiz.gif BORDER=0> <TD COLSPAN=2><FONT SIZE=4> <A HREF="http://public.perforce.com:8080/@ra=s@/public/perforce/"> perforce </A> <TD><IMG SRC=http://www.perforce.com/images/diag_bl.gif border=0> <TD> <TD><B>Perforce <TR> <TD><IMG SRC=http://www.perforce.com/images/diag_vert.gif BORDER=0> <TD> <TD><IMG SRC=http://www.perforce.com/images/diag_tr.gif BORDER=0> <TD><IMG SRC=http://www.perforce.com/images/diag_horiz.gif BORDER=0> <TD><FONT SIZE=4> <A HREF="perforce/utils/index.html"> utils </A> <TD><IMG SRC=http://www.perforce.com/images/diag_bl.gif border=0> <TD>Conversion scripts, browsers, triggers, daemons, and other supporting programs. <TR> <TD><IMG SRC=http://www.perforce.com/images/diag_vert.gif BORDER=0> <TD> <TD><IMG SRC=http://www.perforce.com/images/diag_tr.gif BORDER=0> <TD><IMG SRC=http://www.perforce.com/images/diag_horiz.gif BORDER=0> <TD><FONT SIZE=4> <A HREF="perforce/api/index.html"> api </A> <TD><IMG SRC=http://www.perforce.com/images/diag_bl.gif border=0> <TD>Interfaces to the Perforce API. <TR> <TD><IMG SRC=http://www.perforce.com/images/diag_vert.gif BORDER=0> <TD> <TD><IMG SRC=http://www.perforce.com/images/diag_tr.gif BORDER=0> <TD><IMG SRC=http://www.perforce.com/images/diag_horiz.gif BORDER=0> <TD><FONT SIZE=4> <A HREF="perforce/faq/index.html"> faq </A> <TD><IMG SRC=http://www.perforce.com/images/diag_bl.gif border=0> <TD>Frequently-asked questions and other user-contributed documentation. <TR> <TD><IMG SRC=http://www.perforce.com/images/diag_vert.gif BORDER=0> <TD> <TD><IMG SRC=http://www.perforce.com/images/diag_tr.gif BORDER=0> <TD><IMG SRC=http://www.perforce.com/images/diag_horiz.gif BORDER=0> <TD><FONT SIZE=4> <A HREF="perforce/webkeeper/index.html"> webkeeper </A> <TD><IMG SRC=http://www.perforce.com/images/diag_bl.gif border=0> <TD>Perforce WebKeeper module for the Apache HTTP server <TR> <TD><IMG SRC=http://www.perforce.com/images/diag_vert.gif BORDER=0> <TD> <TD><IMG SRC=http://www.perforce.com/images/diag_tr.gif BORDER=0> <TD><IMG SRC=http://www.perforce.com/images/diag_horiz.gif BORDER=0> <TD><FONT SIZE=4> <A HREF="perforce/p4dti/index.html"> p4dti </A> <TD><IMG SRC=http://www.perforce.com/images/diag_bl.gif border=0> <TD>Integrate Perforce with third-party defect tracking systems <TR> <TD><IMG SRC=http://www.perforce.com/images/diag_vert.gif BORDER=0> <TD> <TD><IMG SRC=http://www.perforce.com/images/diag_tr.gif BORDER=0> <TD><IMG SRC=http://www.perforce.com/images/diag_horiz.gif BORDER=0> <TD><FONT SIZE=4> <A HREF="perforce/cdsp4/index.html"> cdsp4 </A> <TD><IMG SRC=http://www.perforce.com/images/diag_bl.gif border=0> <TD>The Cadence-Perforce Integration <TR> <TD><IMG SRC=http://www.perforce.com/images/diag_vert.gif BORDER=0> <TD> <TD><IMG SRC=http://www.perforce.com/images/diag_llcorner.gif BORDER=0> <TD><IMG SRC=http://www.perforce.com/images/diag_horiz.gif BORDER=0> <TD><FONT SIZE=4> <A HREF="perforce/integrations/index.html"> integrations </A> <TD><IMG SRC=http://www.perforce.com/images/diag_bl.gif border=0> <TD> Integrations of Perforce into various other third party tools and environments. <TR> <TD><IMG SRC=http://www.perforce.com/images/diag_tr.gif BORDER=0> <TD><IMG SRC=http://www.perforce.com/images/diag_horiz.gif BORDER=0> <TD COLSPAN=2><FONT SIZE=4> <A HREF="jam/index.html"> jam </A> <TD><IMG SRC=http://www.perforce.com/images/diag_bl.gif border=0> <TD> <TD><B>Jam/MR <TR> <TD><IMG SRC=http://www.perforce.com/images/diag_llcorner.gif BORDER=0> <TD><IMG SRC=http://www.perforce.com/images/diag_horiz.gif BORDER=0> <TD COLSPAN=2><FONT SIZE=4> <A HREF="revml/index.html"> revml </A> <TD><IMG SRC=http://www.perforce.com/images/diag_bl.gif border=0> <TD> <TD><B>RevML <TR></TR><TD></TD> <TR> <TD COLSPAN=2><FONT SIZE=4> <A HREF="http://public.perforce.com:8080/@ra=s@/guest/"> guest </A> <TD><IMG SRC=http://www.perforce.com/images/diag_bl.gif border=0> <TD> <TD> <TR> <TD><IMG SRC=http://www.perforce.com/images/diag_llcorner.gif BORDER=0> <TD><IMG SRC=http://www.perforce.com/images/diag_horiz.gif BORDER=0> <TD COLSPAN=3><FONT SIZE=4><I>your_name_here</I> <TD><IMG SRC=http://www.perforce.com/images/diag_bl.gif border=0> <TD><B>Guest branches </TABLE> </CENTER> <!-- -------------------------------------------------------------- --> <P> <TABLE CELLSPACING=0 BORDER=0 WIDTH=100%> <TR><TD BGCOLOR=FFCC66> <A NAME="howtobrowse"></A> <H2>How to Browse the Public Depot </H2> <TD WIDTH=5% BGCOLOR=FFCC66 ALIGN=RIGHT> <FONT SIZE="-2"><A HREF="#toc"> Back to<BR>Table of<BR>Contents</A></TD></TR> </TABLE> <!-- -------------------------------------------------------------- --> <p> If you're simply curious about our Public Depot, please browse freely using one of the following products we have set up on this site: <DL> <DT> <A HREF="perforce/webkeeper/README.WEBKEEP">WebKeeper</A> <P> <DD> The web server at <code>public.perforce.com</code> is an <a href="http://www.apache.org">Apache Server</a> with the Perforce Webkeeper module and the Perforce C++ API linked in. When you point your browser to <code>public.perforce.com</code>, you're browsing files in a Perforce depot. For example, the file you're reading now is stored in the Public Depot as "//public/index.html". <P> WebKeeper source files are available in the Perforce Public Depot in the <a href="perforce/webkeeper/">//public/perforce/webkeeper</a> path. For more information about the Perforce C++ API, see the Perforce <A HREF="http://www.perforce.com/perforce/loadsupp.html">Supporting Programs</a> page. <P> <DT><A HREF="http://www.perforce.com/perforce/doc.002/manuals/p4web/index.html">P4Web</A> <P> <DD> The alternate web server on this site is a P4Web Viewer, listening on <code>public.perforce.com:8080</code>. <P> Like P4DB, P4Web lets you navigate a depot hierarchy, observe activity, and browse file content. (The links on this page to Public Depot paths are handled by P4Web.) <a href="http://public.perforce.com:8080/@ra=s@/"><i>Start here</i></a> to try it out. <P> And, like WebKeeper, P4Web sends documents to your web browser directly from a Perforce depot. For example, the page you're reading now is also available through P4Web at: <PRE> <a href="http://public.perforce.com:8080/public/index.html">http://public.perforce.com:8080/public/index.html</A></PRE> <P> Unlike WebKeeper, however, P4Web lets you "go back in time" to browse documents stored in a Perforce depot. For example to see what this page looked like at 1:00 pm back in October 2, 1998, say, you could point your browser to: <PRE> <a href="http://public.perforce.com:8080/public/index.html@1998/10/02:13:00">http://public.perforce.com:8080/public/index.html@1998/10/02:13:00</A></PRE> <P> P4Web is currently available from the <A HREF="http://www.perforce.com/perforce/loadprog.html">Perforce Downloads</A> page. <P> <DT><A HREF="perforce/utils/p4db/README.html">P4DB</A> <P> <DD> P4DB is a suite of CGI scripts in Perl contributed by Perforce user Fredric Fredricson. It lets you navigate a depot hierarchy, observe activity, and browse file content. To browse the Perforce Public Depot with P4DB, <a href="http://public.perforce.com/cgi-bin/p4db/index.cgi"><i>start here</i></a>. The latest P4DB release is available at <a href="ftp://ftp.mydata.se/pub/P4DB/P4DB_2.0.tar.gz">ftp://ftp.mydata.se/pub/P4DB/P4DB_2.0.tar.gz</a> <P> <DT>And... <DD> <P> You can run any of the available Perforce client programs (P4, P4Win, P4Web, etc.) on your own machine to access the Public Depot. Just set your Perforce port (P4PORT) to: <PRE> public.perforce.com:1666</pre> Note that we periodically purge client specs created by unregistered users. You are free to create new clients but unless you're a registered user, don't count on having a persistent client spec in the depot. See below for instructions on becoming a registered user. <p> Perforce client programs are available from the <A HREF="http://www.perforce.com/perforce/loadprog.html">Perforce Downloads</A> page. <P> </DL> <P> <!-- ------------------------------------------------------------ --> <P> <TABLE CELLSPACING=0 BORDER=0 WIDTH=100%> <TR><TD BGCOLOR=FFCC66> <A NAME="howtocontrib"></A> <H2>How to Contribute to the Public Depot </H2> <TD WIDTH=5% BGCOLOR=FFCC66 ALIGN=RIGHT> <FONT SIZE="-2"><A HREF="#toc"> Back to<BR>Table of<BR>Contents</A></TD></TR> </TABLE> <!-- ------------------------------------------------------------ --> <P> <TABLE WIDTH=100%> <TR> <TD VALIGN=TOP WIDTH=20%> <h4>Registering</h4> </TD> <TD VALIGN=TOP> <ul> <P> <li> To contribute to the Public Depot, you'll need to become a registered user. To apply, please send email to <a href="mailto:opensource@perforce.com">opensource@perforce.com</a>, describing the tools, scripts, or documents you'd like to contribute. You must provide your full name, which we will use to assign your Perforce user ID. (E.g., if your name is Sammy Davis, Jr, your user ID in the Perforce Public Depot will be <code><b>sammy_davis_jr</b></code>.) </ul> <p> </TD></TR> <TR><TD COLSPAN=2> </TD></TR> <TR> <TD VALIGN=TOP WIDTH=20%> <h4>Client Setup</h4> </TD> <TD VALIGN=TOP> <ul> <P> <li> If you're not already using Perforce, you'll need a Perforce client program for your development platform. Go to our <A HREF="http://www.perforce.com/perforce/loadprog.html">downloads page</A> and download the client for your platform. <p> <li> Follow the instructions in the <a href="tutorial.html">tutorial</a> to set up a client workspace with a guest branch view for yourself. <p> </ul> </TD></TR> <TR><TD COLSPAN=2> </TD></TR> <TR> <TD VALIGN=TOP WIDTH=20%> <h4>Submitting Files</h4> </TD> <TD VALIGN=TOP> <ul> <li> You are free to submit any files or changes to your guest branch. If you're new to Perforce, see the <a href="tutorial.html">tutorial</a> for a guided example of how to work on files. <p> <li> When you have something in your guest branch that is completed and ready to be integrated into the public branch, please email the curator of the project you're targeting. Curators are listed in the <code><b>index.html</b></code> files at the top level of each project (see the Depot Roadmap, above). The curator will review your files and integrate them into the public branch. </ul> <p> </TD></TR> <TR><TD COLSPAN=2> </TD></TR> <TR> <TD VALIGN=TOP WIDTH=20%> <h4>Notes on Access Permissions</h4> </TD> <TD VALIGN=TOP> <ul> <li> There are two depots in the Public Depot: <code><b>//public</b></code> and <code><b>//guest</b></code>. All users, registered or not, have read access to all files in both depots. <p> <li>All users have read access to all changelist descriptions, user specs, client specs, etc. <p> <li> Only registered users have write access, and only to the files in his/her guest branch. (That is, you can only submit files in the <code><b>//guest/your_name</b></code> path.) <p> <li> Only Perforce staff, and "curators" designated by Perforce staff, have write access to files in the <code><b>//public</b></code> depot. <P> </ul> </TD></TR> <TR><TD COLSPAN=2> </TD></TR> <TR> <TD VALIGN=TOP WIDTH=20%> <h4>More Information</h4> </TD> <TD VALIGN=TOP> <ul> <li> All registered users should read the <a href="tutorial.html">Public Depot Tutorial</a>. <p> <li> Users new to Perforce should visit our <a href="../perforce/technical.html">Technical Documentation</A> page. <p> </ul> </TD> </TR> </TABLE> <P> <!-- ------------------------------------------------------------ --> <P> <TABLE CELLSPACING=0 BORDER=0 WIDTH=100%> <TR><TD BGCOLOR=FFCC66> <A NAME="reviewdaemon"></A> <H2>Subscribing to Change Notifications Via Email </H2> <TD WIDTH=5% BGCOLOR=FFCC66 ALIGN=RIGHT> <FONT SIZE="-2"><A HREF="#toc"> Back to<BR>Table of<BR>Contents</A></TD></TR> </TABLE> <!-- ------------------------------------------------------------ --> <P> There is a Perforce change review daemon for the Public Depot. You can configure your Perforce User Specification so that you will be notified about changes submitted by others to the Public Depot, either for the entire depot, or any subset of files kept here. <P> The basic procedure is to edit your Perforce User Specification, adding a "Reviews:" field, with entries to select the paths within the depot of files you are interested in. When a change affecting such files is submitted, you will be notified via email. You must also have the <tt>Email:</tt> field in your User Specification correctly set to the address where you want notifications to be sent. (You can edit your User Specification using the <tt> p4 user </tt> command from the command line client). <P> For example, to "subscribe" so that you will be notified about all changes affecting anything under <tt> //public </tt>, or any changes that affect any files in directories named "<tt>cvs2p4</tt>" (anywhere in the depot), you would set your User Specification to include: <blockquote><pre> Email: <i>your email address</i> Reviews: //public/... //.../cvs2p4/* </pre></blockquote> <P> The Public Depot review daemon will also allow the person submitting a change to include additional addressees for a particular change notification, by including a one or more lines of the form <blockquote><pre> Description: cc: <i>address</i> [ <i>address</i> ... ] </pre></blockquote> in the Description field of either the Change Specification for a given change, or of the Client Specification of the client from which the change is being submitted. <br><br><br> <!-- ------------------------------------------------------------ --> <P> <TABLE CELLSPACING=0 BORDER=0 WIDTH=100%> <TR> <TD WIDTH=15% BGCOLOR=FFCC66 ALIGN=LEFT VALIGN=CENTER> <FONT SIZE="-2"> Copyright ©<br> 1998, 1999<br> <a href="http://www.perforce.com">Perforce Software</a><br> </FONT> </TD> <TD WIDTH=70% BGCOLOR=FFCC66 ALIGN=CENTER> <FONT SIZE="-2"> You're browsing a file stored as<br> <code>$Id: //public/index.html#28 $</code><br> in the <A HREF=http://public.perforce.com/public/index.html>Perforce Public Depot</A>. </FONT> </TD> <TD WIDTH=15% BGCOLOR=FFCC66 ALIGN=RIGHT> <FONT SIZE="-2"><A HREF="#toc"> Back to<BR>Table of<BR>Contents</A></TD></TR> </FONT> </TD> </TR> </TABLE> <!-- ------------------------------------------------------------ --> </BODY>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#47 | 9981 | laurette | Obsolete, deleting. | ||
#46 | 6276 | Sam Stafford | Change old pages to http://public.perforce.com/wiki/ redirects. | ||
#45 | 6026 | rlo |
Public depot fixes: * Titles formatted similarly * Navbar changed and shortened * Change review taken out of navbar * Links fixed |
||
#44 | 6025 | rlo |
Public Depot Redesign goes live * Skin matches KB and latest WWW skin * Rudimentary search mechanism based on google * did this already, but made some big mistakes and it was easier to obliterate and start over * about the above: yikes! |
||
#43 | 5660 | michael | Fix links to P4DB. | ||
#42 | 5416 | michael |
Provide pointers to P4DB in //guest branch and remove from //public. Provide link to security notice in Bugtraq. |
||
#41 | 4266 | michael | Update link to P4DB. | ||
#40 | 4262 | michael | Note that browsing via P4DB is currently disabled. | ||
#39 | 2726 | Perforce maintenance | Fix typo in index page. | ||
#38 | 2442 | rmg |
Add blanket disclaimer of warranty to the top of the "How to Browse the Public Depot" section. |
||
#37 | 2244 | rmg | Fix for job009083 [in computer:1666!] (poorly rendered sidebar). | ||
#36 | 2142 | rmg |
Starting to do the "Jam M/R" -> "Jam" rename, in the top-level places. |
||
#35 | 2123 | rmg | Supporting Programs -> Related Software | ||
#34 | 2031 | rmg |
Add information to go with the newly-installed p4ftpd access to the Public Depot. http://public.perforce.com/public/index.html#howtobrowse cc: tony@perforce.com, laura@perforce.com |
||
#33 | 1958 | rmg | Fix three broken links reported by reb | ||
#32 | 1882 | rmg | Fix the link to p4db distribution directory | ||
#31 | 1551 | rmg |
Add the official "Back-in-Time Browsing (R)" incantation, per Laura's suggestion. |
||
#30 | 1196 | rmg | Change to new logo on the main index page. | ||
#29 | 1123 | Perforce staff |
Resubmit as type ktext so (I think) webkeeper will display the correct MIME type. |
||
#28 | 968 | rmg |
Change mail addresses from "info@perforce.com" to "opensource@perforce.com" (now that the "opensource" address exists). |
||
#27 | 955 | rmg | Remind about the EMail: field, too! | ||
#26 | 954 | rmg |
Add a section "Subscribing to Change Notifications Via Email". This may want to move into the Tutorial at some point, but I don't want to bury it there while it's a new feature. cc: rmg@perforce.com |
||
#25 | 949 | rmg | Add the new "integrations" directory, and the link to p4ot. | ||
#24 | 776 | rmg |
Adjust the revml index (per feedback from barries and others) and point the top level index link at it. |
||
#23 | 757 | rmg |
add the link to cdsp4 tighten up the vertical spacing a bit |
||
#22 | 735 | rlo |
Rev ML on index page. Still no description of what it does, but it's now at least visible |
||
#21 | 569 | rlo | Public depot pointer to p4dti source | ||
#20 | 485 | Laura Wingerd | Update references to P4Web. | ||
#19 | 465 | Laura Wingerd | Reorganize "How to Browse", add P4Web links. | ||
#18 | 156 | Laura Wingerd | Publish Mike Meyer's Python interface to Perforce API. | ||
#17 | 114 | Laura Wingerd | Fix typos in links. | ||
#16 | 94 | Laura Wingerd |
Re-org "triggers" directory -- it's now part of the "Perforce Utilities" project. |
||
#15 | 52 | Laura Wingerd | Minor web page format changes. | ||
#14 | 51 | Laura Wingerd | Update copyright year. | ||
#13 | 50 | Laura Wingerd | Minor PD doc changes. | ||
#12 | 46 | Perforce maintenance | Add WebKeeper source. | ||
#11 | 42 | Laura Wingerd | Fix links in index pages, add one for jam. | ||
#10 | 28 | Perforce maintenance | Reword intro, fix typos, fix navbars | ||
#9 | 26 | Perforce maintenance | Fleshed out "how to contribute". | ||
#8 | 22 | Perforce maintenance | Added "About the depot" section. | ||
#7 | 19 | Perforce maintenance | Fix browser links, add lost trailer back in. | ||
#6 | 15 | Perforce maintenance | Added browser links to index. | ||
#5 | 10 | Perforce maintenance | Added "How to Browse". | ||
#4 | 9 | Perforce maintenance | Add road map & nicer formatting. | ||
#3 | 8 | Perforce maintenance | Change to ktext. | ||
#2 | 7 | Perforce maintenance | Test links in index page. | ||
#1 | 6 | Perforce maintenance | Open source depot index. |