| *** mikal0 is now known as mikal | 08:20 | |
| opendevreview | Monty Taylor proposed openstack/project-config master: Add wandertracks-rail repo https://review.opendev.org/c/openstack/project-config/+/981322 | 16:46 |
|---|---|---|
| opendevreview | Merged openstack/project-config master: Add wandertracks-rail repo https://review.opendev.org/c/openstack/project-config/+/981322 | 17:02 |
| *** vhari_ is now known as vhari | 17:50 | |
| *** elvira1 is now known as elvira | 19:51 | |
| opendevreview | Goutham Pacha Ravi proposed openstack/project-config master: Add Code-Review and Rollcall-Vote to governance dashboard https://review.opendev.org/c/openstack/project-config/+/981404 | 20:07 |
| clarkb | gouthamr: I think gerrit automatically adds columns to change list views if those labels are submit requirements | 20:31 |
| clarkb | I don't know if thati s helpful for ^ but I think it does autoamtically add some stuff based on that criteria | 20:31 |
| gouthamr | yeah :( i didn’t know the unintended consequence of changing those submit requirements based on our process changes | 20:36 |
| fungi | it may be that some projects didn't add certain labels as submit requirements because they didn't want them to block merging | 20:36 |
| gouthamr | yes | 20:36 |
| fungi | so it's more of a "make sure you thought about this" sort of thing | 20:36 |
| clarkb | I do think it would be cool if Gerrit had a better repo level dashboard that could have some configurable rules around some of this stuff eg branches that are important or hashtags to highlight or something | 20:51 |
| clarkb | the existing dashboard feature feels like an attempt to address problems using existing tools when I suspect we really need to reimagine how this is presented to the user in the first place | 20:51 |
| gouthamr | ++ yes | 20:59 |
| fungi | on the other hand, the current polygerrit webui is merely a javascript-based client in the browser communicating with a remote rest api, so building a custom dashboard from scratch may not be overly complicated | 21:14 |
| fungi | especially since it would essentially be a front-end for read-only search queries | 21:15 |
| fungi | format http query -> parse json response -> render (html or other) table | 21:18 |
| clarkb | fungi: ya though I think what may be missing is some project level attributes about what people should be looking at. Maybe that can be stashed somewhere preexisting though | 21:47 |
| clarkb | or in some special ref like the existing project configuration ref | 21:48 |
| fungi | if you want it to be dynamic per-project or something then yes | 21:49 |
| fungi | but a quick-n-dirty implementation could just hard-code those choices | 21:51 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!