<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
</head>
<body>
<div style="font-family: sans-serif;">
<span dir="ltr" style="margin-top:0; margin-bottom:0;">What's the plan for sys admin tickets currently needed to publish releases?</span> <br>
</div>
<div><br>
<div>
<p>May 26, 2023 5:10:43 PM Ben Cooksley <bcooksley@kde.org>:</p>
</div>
<blockquote style="margin:0;border-left:3px solid #ccc; padding-left:10px">
<div dir="ltr">
<div dir="ltr">
On Fri, May 26, 2023 at 9:31 AM Nate Graham <<a href="mailto:nate@kde.org">nate@kde.org</a>> wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On 5/23/23 03:48, Ben Cooksley wrote:> Also, in Phabricator, Tasks <br> have no real "home"; they just have project<br> > tags, and they can have multiple such tags to be able to belong to<br> > multiple projects. For example "VDG" and also "Plasma". Such a Task<br> > shows up in both projects' workboards. But in GitLab, Issues need to<br> > live in one place and only one place. So for such Phab tasks, we would<br> > need a way to determine the single new home of the Task in GitLab, and<br> > perhaps tag them with global-scope labels or something?<br> > <br> > <br> > Yes, we would need to do a deconflicting process there.<br> > Any thoughts on the best approach to that?<br> <br> At least in the case where a Task is tagged with VDG and also something <br> else, it probably makes sense to have it live on GitLab in the <br> "something else" project/group/etc. Back in the Phab days, we used to <br> tag everything VDG-relevant with the VDG tag, but on Gitlab it probably <br> makes more sense to just CC the "@teams/vdg" group instead.<br>
</blockquote>
<div><br>
</div>
<div>
Excellent, sounds like we've got a path forward then.
</div>
<div><br>
</div>
<div>
I will look at publishing a list of projects this weekend (separate thread) so people can nominate the project that should receive those issues.
</div>
<div>
Note that if existing projects don't really fit (because it is for a collection of projects) we may want to consider use of something like was setup for KF6 (<a href="https://invent.kde.org/teams/frameworks-devs/kf6-workboard">https://invent.kde.org/teams/frameworks-devs/kf6-workboard</a> for instance)
</div>
<div>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br> Nate<br>
</blockquote>
<div><br>
</div>
<div>
Cheers,
</div>
<div>
Ben
</div>
</div>
</div>
</blockquote>
</div>
</body>
</html>