Is this our bug, or due to a component used?

No worries, this is a known limitation of vizGrimoire. Álvaro (Bitergia) will work on this when he comes back from holidays next week.

Next week we will incorporate pagination to all repositories listing. Once we have integrated it in korma I will inform in this issue and once checked, we can close it.

Hi!

For all data sources (git, bugzilla, gerrit, irc and mailing lists) all the repositories could be shown using pagination. The pagination UI is not polished yet but you can test it. The number of items per page is 10.

http://korma.wmflabs.org/browser/scm-repos.html (232)

http://korma.wmflabs.org/browser/its-repos.html (4) (The repos here will change once closed https://bugzilla.wikimedia.org/show_bug.cgi?id=54469)

http://korma.wmflabs.org/browser/mls-repos.html (25)

http://korma.wmflabs.org/browser/scr-repos.html (235)

http://korma.wmflabs.org/browser/irc-repos.html (11)

Looking at http://korma.wmflabs.org/browser/scm-repos.html

This UI is realy confusing... It took me a while to see the ">"...

If we have >200 repositories in practice is impractical to click Next maybe 20 times to find your project... Is there a quick way to search/find the data of a specific project?

The current design might be enough for up to 10 repos but beyond that things start getting really ugly (e.g. the column graphs are almost meaningless when they show only the 10 repos listed in that page).

Do you agree with this problem?

One possibility would be to have a text-only table/list with all reports, sorted alphabetically, specifying the basic metrics of every repo and a link to go to the specific page of the repo.

But... maybe it's better to sketch before coding? Currently is not even clear what UI are you after.

(Removing Patch to Review since we use it only when there is an actual patch to review in Gerrit)

Yes, I agree that the UI is not intuitive. We can put a larger and more cute ">" (bootstrap has pagination support UI) and it is the plan to finish the current UI.

But as you have mentioned, we have other problem with the scalability of the pagination. We have thought about adding a search field and also, about your proposal for using a text only list sorted alphabetically. And maybe to have a "A B ... Z" navigation bar.

Our idea is to finish first with the pagination UI issues and then, we can explore other solutions. Is it ok for you?

Makes sense. Trying to untangle the problem in pieces:

• Using the usual, visible and explicit: "previous" / "next" in addition or instead of "<" / ">".

• If we have only 10 results per page then I think we can avoid the long line with the anchors to the 10 repos. Not only is not very useful, it also "camuflages" the previous / next arrows by adding all that extra text.

• If you can add a search box that will be great, yes.

• A-Z bar... I would check again after fixing the three points above, to see whether it's really needed or an overkill.

Quim, take a look to:

http://korma.wmflabs.org/browser/scm-repos.html?page=2

A welcomed improvement, yes!

Are you still planning to implement the search box? Yesterday I tried to find CentralAuth and I just gave up. :(

Quim, take a look to:

http://korma.wmflabs.org/browser/contributors.html

The same concept could be added to repositories. Is it enough?

Yes, that would work. Assuming that "C... e... n... t..." :) would result in a "CentralAuth" suggestion even if such project is not listed in the same page.

Yes Quim, the search field will work on *all* items (orgs, repos, countries) no matter the current page in which you are.

Ok, I will start deploying this feature to all reports. So you can navigate to get a general vision and if you are looking for a specific item, you can just search. The last option could be to have complete lists. But this option, for the future!