org/process/SetUpProjectMgt.md

-= Set up a Trac-based project-management system for Tor =
+# Set up a Trac-based project-management system for Tor
 
-We're trying to move to a [wiki:org/projects project-management system] to organize our work.  We want our system:
+We're trying to move to a [project-management system](./org/projects) to organize our work.  We want our system:
 
   * To reflect work at a level somewhat more coarse-grained than tasks
-  * To track deliverables that we've promised to [wiki:org/sponsors], and relate them to our products
+  * To track deliverables that we've promised to [org/sponsors](org/sponsors), and relate them to our products
   * To reflect other things we need to enumerate more.
 
 We've made a start of it at the wiki:projects page, but there's more work to do.  We should at least:
 
   * ~~Finish this TODO list; make sure there's nothing missing.~~
-  * ~~Write up a good description of our project-management system at [wiki:org/process/HowWeDoProjectManagement].~~
+  * ~~Write up a good description of our project-management system at [org/process/HowWeDoProjectManagement](org/process/HowWeDoProjectManagement).~~
      * ~~Start writing the page~~
      * ~~Describe the workflow better~~
      * Describe how to indicate the type of a project
@@ -21,7 +21,7 @@ We've made a start of it at the wiki:projects page, but there's more work to do.
       * ~~TODO.future (about 25% done.  Some of it should be a !BlueSkyDesignIdeas wiki page or something)~~
       * TODO.02* (mostly done; some remaining stuff is just echoes of proposals.)
     * Proposals
-  * Add some hierarchy to the [wiki:org/projects] namespace? Instead of projects/ProjectName, let's have projects/ShortProduct/ProjectName.
+  * Add some hierarchy to the [org/projects](org/projects) namespace? Instead of projects/ProjectName, let's have projects/ShortProduct/ProjectName.
      * ~~Move all metrics Project pages~~
      * Figure out what to do with unsorted stuff like [wiki:org/projects/2009FinancialandComplianceAudit], [wiki:org/projects/ExperimentalBridgeBundles]
   * Add links to external TODO lists that won't be maintained with this system.
@@ -30,7 +30,7 @@ We've made a start of it at the wiki:projects page, but there's more work to do.
      * ~~[wiki:org/sponsors/SponsorB]: complete.~~
      * ~~org/sponsors/SponsorC: there is no sponsor C anymore.~~
      * ~~Sponsor D: list of deliverables not yet finalized.~~
-  * Figure out what to do with the existing projects/Product pages for [wiki:org/roadmaps/BridgeDB], [wiki:org/roadmaps/TorCheck], etc.  Most of these are just lists of TODO items, partially converted to trac entries.  We could make an arbitrary project for each TODO item, or we could try to group them up into projects, or such.  When grouping tasks into projects, we might call that project "release version x.y of product z" so that we have a goal to work on.
+  * Figure out what to do with the existing projects/Product pages for [org/roadmaps/BridgeDB](org/roadmaps/BridgeDB), [org/roadmaps/TorCheck](org/roadmaps/TorCheck), etc.  Most of these are just lists of TODO items, partially converted to trac entries.  We could make an arbitrary project for each TODO item, or we could try to group them up into projects, or such.  When grouping tasks into projects, we might call that project "release version x.y of product z" so that we have a goal to work on.
 
   karsten: I'm moving these pages to org/roadmaps/*.  These pages describe what the status of a product is and how we want it to be in the future.  Whenever we start working on an item we should start a project or a task.  When we're done we should update the roadmap.
 
@@ -67,7 +67,7 @@ karsten: Here are a few things that I changed or plan to change:
 > nickm: Adding a new "project" ticket type seems like a great idea, if we can actually distinguish projects from nonprojects.  I bet we can.
 >> karsten: Yes, we can search by ticket type.
 
- - We shouldn't maintain a manual list of active projects in the wiki like the current one on [wiki:org/projects].  Nobody wants to update such a list which is why the current page isn't very useful.  We should rather let Trac generate a list of all tickets starting with "Project: " (or of all tickets of type project).  See the Projects section on [wiki:org] for how such a list of active projects would look like.
+ - We shouldn't maintain a manual list of active projects in the wiki like the current one on [org/projects](org/projects).  Nobody wants to update such a list which is why the current page isn't very useful.  We should rather let Trac generate a list of all tickets starting with "Project: " (or of all tickets of type project).  See the Projects section on [org](org) for how such a list of active projects would look like.
 > nickm: I'm agreed about letting the list of projects be autogenerated.
 
  - If we need to create a wiki page for a really complex project, we should make sure that it disappears once the project is over.  Projects are temporary things and so are the project wiki pages.  We shouldn't accumulate work plans for completed projects in the wiki.  My suggestion would be to copy the wiki page to a text file and attach it to the project ticket when closing it.  If it wasn't just a work plan but something we want to keep, it needs to go somewhere else (code repository, tor-dev mailing list, proposal directory, etc.) anyway.