Perforce

Welcome to the Perforce Public Depot




About Perforce and the Public Depot

Back to
Table of
Contents

  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 depot, 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.
If you haven't heard about Perforce, the Fast Software Configuration Management System, head over to our home page and read all about it.

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 WebKeeper, an Apache Web Server module for accessing files in a Perforce depot, and Jam/MR, a fully portable alternative to make(1).

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.

The Depot Roadmap

Back to
Table of
Contents

public
 perforce Perforce
 utils Conversion scripts, browsers, daemons, and other supporting programs.
 faq Frequently-asked questions and other user-contributed documentation.
 webkeeper Perforce WebKeeper module for the Apache HTTP server
 jam Jam/MR
guest
your_name_here Guest branches

How to Browse the Public Depot

Back to
Table of
Contents

If you're simply curious about our Public Depot, please browse freely. Here's how:

How to Contribute to the Public Depot

Back to
Table of
Contents

Registering

  • To contribute to the Public Depot, you'll need to become a registered user. To apply, please send email to info@perforce.com, 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 sammy_davis_jr.)

 

Client Setup

  • If you're not already using Perforce, you'll need a Perforce client program for your development platform. Go to our downloads page and download the client for your platform.

  • Follow the instructions in the tutorial to set up a client workspace with a guest branch view for yourself.

 

Submitting Files

  • You are free to submit any files or changes to your guest branch. If you're new to Perforce, see the tutorial for a guided example of how to work on files.

  • 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 index.html 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.

 

Notes on Access Permissions

  • There are two depots in the Public Depot: //public and //guest. All users, registered or not, have read access to all files in both depots.

  • All users have read access to all changelist descriptions, user specs, client specs, etc.

  • 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 //guest/your_name path.)

  • Only Perforce staff, and "curators" designated by Perforce staff, have write access to files in the //public depot.

 

More Information




Copyright 1998
Perforce Software
info@perforce.com
You're browsing a file stored as
$Id: //public/index.html#12 $
in the Perforce Public Depot.
Back to
Table of
Contents