Last Comment Bug 659260 - [pushes] Create network view
: [pushes] Create network view
Product: Webtools
Classification: Server Software
Component: Elmo (show other bugs)
: Trunk
: All All
P3 normal (vote)
: 2.1
Assigned To: Axel Hecht [:Pike]
Depends on: 718051
  Show dependency treegraph
Reported: 2011-05-24 03:46 PDT by Axel Hecht [:Pike]
Modified: 2012-06-25 05:05 PDT (History)
1 user (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Axel Hecht [:Pike] 2011-05-24 03:46:00 PDT
With the increasing amount of cross-repo shuffling we do with the new release cycle, it's becoming more valuable to have a network view ala github.

We have all the data for that, so getting there is basically a three-step process:

- extract the data for a network view from the database. changesets, topology, pushes, repos.
- display that data in a graph
- update the graph based on navigation

The first item is a good excersize to learn more about our hg data, the second involves a good deal of html5 to get graphs going, but also some structured thinking on edge colors etc.
The third one is really tricky, in particular if you don't want to reload the graph (which is fine), but instead feel like morphing an existing graph with more data.

Side notes: This goes beyond what github does in the sense that it should be based on changesets, and not "forks". I.e., fork detection will work automagically. Given that, it's probably good to have some UX to restrict the graph shown only to some repositories. That's looking forward if we'd have this for all hg repos on hg.m.o, including user repos.
Comment 1 User image Axel Hecht [:Pike] 2011-05-30 01:33:18 PDT
Spent a weekend on this, and some protovis learning.

Awesome data. Buggy, but I may want to land it buggy on -dev-.
Comment 2 User image Axel Hecht [:Pike] 2012-01-30 12:13:45 PST
This landed on -dev-, resolving FIXED.

Note You need to log in before you can comment on or make changes to this bug.