Authentication-Results: mail-b.sr.ht; dkim=none 
Received: from DEU01-BE0-obe.outbound.protection.outlook.com (mail-be0deu01lp2171.outbound.protection.outlook.com [104.47.7.171])
	by mail-b.sr.ht (Postfix) with ESMTPS id 9897711EF19
	for <~renerocksai/telekasten.nvim-devel@lists.sr.ht>; Mon,  3 Oct 2022 11:55:12 +0000 (UTC)
Received: from FR2P281MB2655.DEUP281.PROD.OUTLOOK.COM (2603:10a6:d10:64::10)
 by FR0P281MB3017.DEUP281.PROD.OUTLOOK.COM (2603:10a6:d10:51::12) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5676.24; Mon, 3 Oct
 2022 11:55:08 +0000
Received: from FR2P281MB2655.DEUP281.PROD.OUTLOOK.COM
 ([fe80::64fc:ce7d:1454:6945]) by FR2P281MB2655.DEUP281.PROD.OUTLOOK.COM
 ([fe80::64fc:ce7d:1454:6945%7]) with mapi id 15.20.5676.028; Mon, 3 Oct 2022
 11:55:08 +0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Mon, 03 Oct 2022 13:55:07 +0200
Message-Id: <CNC9OCFI19IR.10GQXC0KGPG8C@ryzen>
Subject: Re: Migration status
Cc: <~renerocksai/telekasten.nvim-devel@lists.sr.ht>
To: "Thomas Lambert" <dev@tlambert.be>
From: "Rene Schallner" <rene@renerocks.ai>
X-Mailer: aerc 0.11.0
References: <yNZ0_RIiMrSewIwD9SQqfzKizXV0l07YBBBJZ0Tj65Ket3Ajm_MPdVoBpuqA2mMVljRpKb_EbHc5dcNtCFNVwCJqlzTqaHL40Q1CSB7l_o8=@tlambert.be> <88225a88-742a-42a2-be15-7ac4b5ab6c7c@renerocks.ai> <Dfax95Hz4w82XjtiF4PYUEIe6-uuHKyEK1PVPlso8x7JBfEDUnV2Xi3c_7GxGcz1fCnR8bWREtCLujvB_mDA6pXipwZyjCB0P2Hd6o2mhoY=@tlambert.be>
In-Reply-To: <Dfax95Hz4w82XjtiF4PYUEIe6-uuHKyEK1PVPlso8x7JBfEDUnV2Xi3c_7GxGcz1fCnR8bWREtCLujvB_mDA6pXipwZyjCB0P2Hd6o2mhoY=@tlambert.be>
X-ClientProxiedBy: FR3P281CA0140.DEUP281.PROD.OUTLOOK.COM
 (2603:10a6:d10:95::12) To FR2P281MB2655.DEUP281.PROD.OUTLOOK.COM
 (2603:10a6:d10:64::10)
MIME-Version: 1.0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: FR2P281MB2655:EE_|FR0P281MB3017:EE_
X-MS-Office365-Filtering-Correlation-Id: 0364b777-3caf-4ce8-b5fa-08daa5361e71
X-OriginatorOrg: renerocks.ai
X-MS-Exchange-CrossTenant-Network-Message-Id: 0364b777-3caf-4ce8-b5fa-08daa5361e71
X-MS-Exchange-CrossTenant-AuthSource: FR2P281MB2655.DEUP281.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Oct 2022 11:55:08.5005
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 5a75309b-d711-4d39-954b-a45d6e4f61e7
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: n07zicgjNo2lgQgQjuSfkkOWZA4UaSv6084tsLLPFbrh1pLX7CLXy2/B7hd569MgQ7HuEVYVBAgxgiz71URsPQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FR0P281MB3017

> > Will check out how to give you write access to issues.

I just checked. todo.sr.ht says I gave you access to everything: browse,
submit, comment, edit, triage two months ago. So I don't know why you
can't edit labels. Maybe that's an oversight at SourceHut? I access the
labels in the `labels` tab, next to `closed tickets`. There, on the left
hand side, I can `Add label`, for instance.

This applies to the telekasten.nvim issue tracker which I am sure you
meant...?

However, I planned to migrate the GitHub issues over to SourceHut before
actually using issues on SourceHut. Now that we've been on SourceHut for
a while, it's understandable that you use the tracker there, too.

For a moment I was worried that GH and SH ids would get out of sync if
we start the migration at e.g. #3 because of existing issues on
SourceHut. But that shouldn't worry us too much since GitHub has holes
in the ID space anyway.

The labels, though. They're going to be migrated, too. So maybe we
should think about that. Or we'll just see what happens.

Or: I have just mirrored the labels to the telekasten.nvim issue tracker
on SourceHut. This way you can check them out and add or request (from
me) additional ones.

Best,
Rene