www/user-classifications.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml">
   4 <head>
   5 <style type="text/css"> /* <![CDATA[ */
   6   @import "branding/css/tigris.css";
   7   @import "branding/css/inst.css";
   8   /* ]]> */</style>
   9 <link rel="stylesheet" type="text/css" media="print"
  10   href="branding/css/print.css"/>
  11 <script type="text/javascript" src="branding/scripts/tigris.js"></script>
  12 <title>User Classifications</title>
  13 </head>
  14
  15 <body>
  16 <div class="h2">
  17 <h2>User Classifications</h2>
  18
  19 <p>In use case lingo, the typical <em>actors</em> for our version
  20 control scenarios.  The following list provides rough classifications
  21 for the type of individual users driving our requirements.</p>
  22
  23 <div class="h3" id="novice">
  24 <h3>Novice</h3>
  25
  26 <p>A developer inexperienced with version control, your typical
  27 documentation writer, or non-technical user (e.g. pointy-haired
  28 manager, administrative assistant, etc.).  Able to make commits, but
  29 often lacking enough understanding of version control concepts to
  30 check out or switch to a branch.  Sometimes does creative things like
  31 "delete large chunks of the repository" or "commit a merge
  32 conflict".</p>
  33
  34 </div>  <!-- novice -->
  35
  36 <div class="h3" id="developer">
  37 <h3>Developer</h3>
  38
  39 <p>A software professional familiar with most of the basic concepts
  40 used with a typical version control system (e.g. repositories,
  41 workspaces, etc.), including change management (e.g. commit, revert,
  42 merge, patch, conflict resolution, etc.).</p>
  43
  44 </div>  <!-- developer -->
  45
  46 <div class="h3" id="merge-meister">
  47 <h3>Merge Meister</h3>
  48
  49 <p>A version control master, usually involved in all important
  50 branching/merging activities, and often responsible for release
  51 engineering.  Usually involved in auditing the changes in a branch,
  52 and process enforcement.  Often proficient with multiple version
  53 control systems.</p>
  54
  55 </div>  <!-- merge-meister -->
  56
  57 <div class="h3" id="program">
  58 <h3>Other Program</h3>
  59
  60 <p>Other programs which invoke Subversion's functionality.  These are
  61 often scripts wrapped around the command-line binaries (e.g. for SCM
  62 automation, integration, etc.), which are sometimes APIs in their own
  63 right.  They're also often third party programs built on top of
  64 Subversion, integrated with its core libraries at the API level.</p>
  65
  66 </div>  <!-- program -->
  67
  68 </div>  <!-- h2 -->
  69 </body>
  70 </html>