
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38774#comment-38774 ] Greg Sheremeta commented on OVIRT-2643: --------------------------------------- It is the description box at the top. But gerrit maintainers can't edit it on github -- only if they are set as admins on github for the project. For example, I don't have access to edit the description for any synced projects under /ovirt and I am maintainer for several projects. I am an admin/maintainer of both ovirt-web-ui and ovirt-site (which don't exist in gerrit) and I can edit those descriptions. Sounds ovirt admins can change them all manually, though, as long as they wouldn't be overwritten by the sync tool. (Even then, the sync tool could be enhanced.)
make the github headers a little more user friendly for our gerrit -> github synced projects --------------------------------------------------------------------------------------------
Key: OVIRT-2643 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2643 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra Attachments: Selection_297.png, Selection_298.png, Selection_299.png
For our gerrit -> github synced projects, can we make the github headers a little more user friendly? This is a usability problem because google searches don't find gerrit -- they find github. So if people google search for "ovirt-engine-api-explorer" for example, it's quite difficult for someone not familiar with gerrit to find the gerrit clone link for their desired repo -- and many clicks even if you are familiar. Before: [image: Selection_298.png] Proposal: [image: Selection_297.png] And, can we somehow auto-fill the description boxes in gerrit with the README contents so users are reassured? [image: Selection_299.png] -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme@redhat.com IRC: gshereme <https://red.ht/sig>
-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)