Future development on hgweb and blame

[Gregory Szorc]

On Fri, May 13, 2016 at 1:31 AM, Laura Médioni <laura.medioni at logilab.fr>
wrote
>
> Hi everyone,
>
> In the frame of the MOSS funding (https://wiki.mozilla.org/MOSS), we (at
> Logilab) are going to work on Mercurial, mainly on hgweb and blame.
>
> The improvements that will be carried on are not defined yet in the
> details, since the idea is to give priority to the features you will value
> the most.
>
> Here are two plans, written by Pierre-Yves and David (Logilab), that
> contain some high-level features that will be worked on:
> https://www.mercurial-scm.org/wiki/HgwebPlan and
> https://www.mercurial-scm.org/wiki/BlamePlan.
> Feel free to give feedback about these, so that we can choose and refine
> the most important ones.
> We are going to start with hgweb.
>

Speaking for Mozilla, we care about improving the interface to blame most.
It is surprisingly common how often our engineers need to perform "code
archeology" to see how something worked 5+ years ago. The hgweb interface
to blame is used most frequently for that because it is much richer than
the terminal-based interface. The hgweb interface to blame today is very
tedious and requires a lot of extra cursor/mouse movements and clicks to
access information. Making it faster to access data (namely blame data for
previous/next changeset and changeset metadata/diff) would be huge
productivity wins. Most of the improvements on BlamePlan center around this
theme. The "advanced html interface" would be the culmination of that work.
But the smaller scoped improvements would be huge wins on their own.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20160527/f3841ec2/attachment.html>