[18:07:13] may i ask why https://wikitech.wikimedia.org/wiki/Wikimedia_Cloud_Services_team/EnhancementProposals/Toolforge_UI includes several already existing features in the "Features to be included in follow-up iterations" section? [18:09:56] taavi: the best person to discuss that would be sarai, but unfortunately she's not on IRC :/ second best is talk to s.lavina or d.avid but I think they're both away until Jan [18:10:49] my understanding (might be wrong!) is that the design plans are "from scratch" and not "on top of Striker", though reusing Striker is one of the possible technical implementations [18:11:06] :( [18:12:02] I think designing from scratch is probably the right choice, IMHO, more like "what should an ideal Toolforge UI look like?" than "what should we be adding to the existing toolforge UI?" [18:12:24] again this is just my 2c, and I haven't followed much the process, so I might be misreading what the plans actually are [18:13:42] the "low-fidelity mockups" link in that page links to a public figma board [18:15:38] I think your comments on that figma board (either directly on figma or through the talk page) would be very valuable, and I can do my best to bridge any slack-irc communication barrier :) [19:32:46] bd808, hasharAway: I'm hoping that https://gerrit.wikimedia.org/r/c/operations/puppet/+/1105945 will reduce the number of CI failures while we hunt for the real issue. Can you think of any serious downside?