--- Petr Baudis <pasky@xxxxxxx> wrote:
> I was looking into accesslogs of repo.or.cz for something and noticed
> that I see unusually large number of blame requests. That of course
> attracted my curiosity and I came to conclusion that what I'm seeing is
> not just my personal whim but we have serious usability problem here.
>
> I'm unfortunately not sure when the update of repo.or.cz gitweb which
> dropped the blob/tree links happenned, so the following _is_ somewhat
> dubious, but I think it's quite telling anyway.
>
> I have three samples (logfiles) available: #2 almost certainly when the
> blob link was still there, #1 covering the switch and some time before
> and after, and #0 certainly when the blob link was not there anymore,
> but unfortunately spanning only one or two days.
>
> This is the count of actions invoked from the tree, commit and
> commitdiff view (using the referer information):
>
> blame blob total requests containing 'a='
> #2 1 18 264
> #1 31 23 399
> #0 4 6 50
>
> The disparation between #2 and #1,#0 is quite apparent. If we want more
> exact results, I will let #0 accumulate data for a week and then revert
> the removal of the links and start another sample.
Oh, my, oh, my.
Anyone can come up with any "statistic" to convince anyone of
anything. It's the American way! (to financial success)
I mean, I can even give you a mathematical series which I can add
in certain orders to give me any number I want... Which is not at
all intutitive.
Anyway, the "confused" link clearly says "blame". I'm not sure why
your people were trying to think and figure it out, as opposed to
simply clicking on the file name itself. It is the most intuitive
thing to do as I mentioned in my previous email.
Did you do any demographics on your clickers? What is their background?
Did you try to calculate how statistically correct your sample is
and if the clickers represent the general computer population out there?
What is your sampling error?
I can hardly accept this "statistic" as a proof to "reintroduce
the redundant links".
But I give up.
If you guys want the redundant links back in, so be it -- submit
a patch.
Then let's fortify gitweb, because we can. Lets add links and more
redundancy to fortify the user interface so that all and any possibilities
are covered. And as soon as a NEW git facility is introduced, then
we'll add 10 or 20 more links to gitweb for this just one, single
new facility. Then with each new single facility if it is related to
any other, the number of links would grow exponentially. Then after
such and such time has passed, let's look at the code. Then let's
ask if someone has left maintaining the then gitweb jungle. More
importantly, let's ask if someone has left _using_ it. (That would
be the ripe time to start afresh with gitweb2.perl.)
As long as job is being done and the patches are flowing in, and
more and more code is introduced, albeit redundantly, we shouldn't
care what the people who use this every day want or care for.
Hey, let's add more links!
Luben
P.S. I'll go and collect some statistics now.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html