Re: Need help with GitHub Issues migration

On Sat, Feb 22, 2025 at 07:38:49PM +0100, Yury V. Zaytsev via mc-devel wrote:
>Hi there, [...]
>
if you had posted this as a project discussion on github, i could click
"like" now. :-D

(the serious question behind this is: do we want to phase out the list
in favor of github discussions? it's obviously a separate thing, but in
this context it kind of suggests itself.)

>Unfortunately, the authorship of the posts cannot be transferred.
>
yeah ...

i wonder whether you could automatically set the watchers on issues
based on inferred participants, though? filtering by mentions would also
work, but only for the old issues, while new ones won't necessarily have
them. being able to filter by "watcher:..." would catch both.

>* Component (labels)
>  - adm: "area: adm"
>
maybe put it in a separate repo instead? depends on whether you want to
create a separate repo for issues or want to attach them to the main
repo (i'd go with the latter).

>  - translates: "area: i18n"
>  - locale: "area: i18n"
>  - translations: "area: i18n"
>
pedantically, translations are l10n.
from experience i can say that users get this almost always wrong, but
assigning components is mostly a maintainer thing in mc anyway.

>* Resolution (partly labels, partly status)
>
a bit of a mess, but i wouldn't know how to fix it.
i know that issue types can be configured at the organization level, but
i have no idea what else.

-- 
mc-devel mailing list
mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org
https://lists.midnight-commander.org/mailman/listinfo/mc-devel