Update roadmap document.

src/docs/roadmap.diviner

@@ -2,80 +2,35 @@
 @group intro
 
 Insight into the direction and progress of Phabricator. This document was last
-updated **June 29, 2011**.
+updated **July 22, 2011**.
 
 = Status =
 
 Phabricator is in an early release stage, but quite usable. The project is under
-active development, with around 200 commits from a dozen contributors in the
-last 30 days. Morale is high. A few people are tweeting about it. Someone wrote
-a Wikipedia page. There are a handful of questions on Quora. As far as we know,
-the product has a perfect safety record and has not caused anyone violent
-physical harm.
+active development.
 
 = Current Development =
 
-Phabricator was released about two months ago. Since then, the focus has been
-on two major areas:
+The current focus on Phabricator is primarily feature buildout, particularly in
+these applications:
 
-  - **Setup/Install Process**: There was barely any install/setup documentation
-    when we released.
-  - **Pilot Installs**: Facebook was the only install when we released. We
-    wanted to get some early adopters to do installs and give us feedback.
-
-The setup/install process is much better now (there's still room for work, of
-course) and we've gotten a bunch of great feedback from pilot installs (and
-implemented a lot of it).
-
-We've also been focusing a lot on things that are mostly feature buildout:
-
-  - **Maniphest**: I wrote Maniphest in about 20 hours in January to track bugs
-    in Phabricator itself, but it seems to be getting a lot of traction. We're
-    doing a lot of feature buildout for it to make it more full-fledged, more
-    scalable, better integrated, and more useful.
-  - **Maturing New Applications**: Generally, there are a lot of apps
-    which landed recently in Phabricator's history (Maniphest, Projects, Search,
-    and Paste are all less than 6 months old; Herald and Diffusion are about
-    a year old; Differential is about 4 years old) which are missing obvious
-    features. We're fixing this stuff.
-  - **Roles and Permissions**: At Facebook, everyone basically had access to
-    everything but this doesn't work everywhere, especially for open source
-    projects. We're working on making this more granular and auditable.
-  - **Version 1.0**: At some point we probably need to bite the bullet, figure
-    out release management, and cut a release. We should probably build some
-    kind of update notifier before we do this. We can probably put this off for
-    a while longer by just declaring trunk a "kind of okay now release" since
-    the balance of feedback for this model has been positive (we've been able to
-    respond quick to a lot of bug reports and get fixes out in a few hours),
-    it's just off-putting to have the documentation caveating the project's
-    readiness so heavily.
-  - **Performance and Quality**: These are permanent priorities for the project,
-    and we're doing a lot of work to continue improving both.
+  - **Maniphest**: A lot of early adopters are getting into the suite because
+    of this tool, and we're continuing to improve it.
+  - **Phriction**: We just landed a wiki application, which basically works but
+    needs a bunch of improvements.
+  - **Feed**: A rough cut of feed landed recently but needs a ton of work.
+  - **Projects**: Projects are getting a bit more useful, but we want to
+    continue adding features.
 
 = Future Development =
 
-Most of the future work involves feature buildout. These are projects we're
+Most of the future work also involves feature buildout. These are projects we're
 thinking about in a very early stage, and may not happen or may look completely
 different when we implement them:
 
-  - **Activity Streams / News Feed**: It can be difficult to get a sense of
-    project activity right now. Some sort of news feed is the obvious approach,
-    but a lot of the models for this aren't great (Google Code, GitHub,
-    Facebook's internal news feed) and we can probably build a more useful
-    product if we spend some time on it. This dataset has a pretty good mapping
-    to "importance" (a review is more important than a comment) which isn't as
-    strong in social data. Stressing that might get us somewhere useful.
-  - **Projects**: This is a feature which existed with a very basic
-    implementation at Facebook, called "tags". It had a lot of product problems
-    that we're experimenting with addressing by making projects more heavyweight
-    and structured. This feature is really bare-bones right now but seems to
-    be getting some traction in pilot installs and there are a lot of obvious
-    ways to build it out, integrate it, and make it more useful.
-  - **Wiki**: We're probably going to build something like a Wiki since it's
-    the biggest hole in the "complete package" that Phabricator presents. We
-    have a lot of the infrastructure we need to do this quickly and some product
-    ideas which could fix a lot of the problems we had with Facebook's wiki.
-    Biggest blocker here is coming up with a totally awesome name for it.
+  - **Hosted/Managed Repositories**: We're starting to develop some features to
+    let Phabricator host or manage repositories, since this simplifies and
+    unblocks some stuff we'd like to eventually build.
   - **Drydock**: Build infrastructure to let Phabricator manage working copies
     in a scalable way. This is a general piece of infrastructure which enables
     us to build a lot of features, like: sandcastle (your changes are
@@ -104,3 +59,4 @@ different when we implement them:
     the many other products in this space? For now, improving the software is
     probably the most important thing we can do to achieve any of these goals,
     but we don't currently have a clear long-term vision.
+