Changes between Version 16 and Version 17 of UsingPidginMercurial

Timestamp:

Sep 23, 2012, 8:33:30 PM (11 years ago)

Author:

John Bailey

Comment:

Some minor updates and tweaks.

UsingPidginMercurial

@@ -68 +68 @@
 
 === Access Control ===
-Access control on Pidgin's Mercurial server is such that repositories.  The repositories are structured like so (developers/CPW's listed here are for the purpose of example):
+Access control on Pidgin's Mercurial server is such that all developers can write to our master repositories, but each developer and CPW has their own repositories that anyone can read but only they can write to.  The repositories are structured like so (developers/CPW's listed here are for the purpose of example):
 
 {{{
@@ -97 +97 @@
 
 Access control is as follows:
-  * Developers have write access to `pidgin/*`
+  * Developers and CPW's have write access to `pidgin/*`
   * Developers can create and modify repositories in `dev/$NICKNAME/`
   * Crazy Patch Writers can create and modify repositories in `cpw/$NICKNAME/*`
@@ -106 +106 @@
 
 === Adding New Users ===
-The process to allow new users SSH access to the Mercurial repositories is pretty simple, but requires someone with "root" access to mercurial-server.  Currently those people are datallah, rekkanoryo, and lschiere.
+The process to allow new users SSH access to the Mercurial repositories is pretty simple, but requires someone with "root" access to mercurial-server.  Currently those people are datallah, markdoliner, rekkanoryo, elb, and lschiere.
 
   1. Check out the `hgadmin` repo: `hg clone ssh://hg@hg.pidgin.im/hgadmin pidgin-hgadmin`