Last modified: 2013-09-30 09:56:26 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T56740, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 54740 - Make main page of git.wikimedia.org more useful: list of repositories is truncated, recent changes too short
Make main page of git.wikimedia.org more useful: list of repositories is trun...
Status: NEW
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
wmf-deployment
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-28 18:25 UTC by MZMcBride
Modified: 2013-09-30 09:56 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description MZMcBride 2013-09-28 18:25:31 UTC
I'm not sure about others, but every time I visit <https://git.wikimedia.org/>, I find the experience less than satisfying.

Due to the high rate of activity, the "recent activity" feed is never helpful to me. If I wanted that, I'd visit <https://gerrit.wikimedia.org>. What I really want is a list of repositories, so I end up clicking over to <https://git.wikimedia.org/repositories/>.

The main page already contains a list of repositories, but it's a truncated list of the most recently active repos or something. I'd like to give some further thought to whether this overall user experience can be improved. Thoughts:

* perhaps auto-redirect from https://git.wikimedia.org/ to https://git.wikimedia.org/repositories/ (does anyone use the dashboard?)

* perhaps specify a different home page in GitBlit's settings (is this possible?)

* perhaps expand the list of recently active repos to be longer (not sure if there's a setting for this in GitBlit, but if so, this is probably the easiest path to resolution)

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


Navigation
Links