Hi Andreas, sorry for second email, I originally did not want to react to this part, but hey, I changed my mind. :)
Andreas Enge <[email protected]> writes: >> > The procedure for notifying channel maintainers (and interested users) >> > is not fully thought out yet. >> A simple bot that looks for issues with deprecation tag, and sends an >> email to guix-deprecation mailing list? Interested parties can then >> subscribe to that list. > > That sounds good. I would not know how to write such a bot. Or integrate > some kind of hook with forgejo when an issue with a given tag is opened. > I will try to enquire with Codeberg what we can do. The "proper" way would be to write a HTTP server, that would listen for the events sent to registered webhook. Well, we do not have to do it the proper way. And we do not need to react to the issue creation immediately. I would suggest to make a script executed twice a day, that would use https://codeberg.org/api/swagger#/issue/issueListIssues to list issues with the deprecation label. --8<---------------cut here---------------start------------->8--- curl -X 'GET' \ 'https://codeberg.org/api/v1/repos/guix/guix/issues?state=open&labels=deprecation&page=1&sort=latest' \ -H 'accept: application/json' --8<---------------cut here---------------end--------------->8--- Get all pages and send emails for not-yet-sent issues. Low effort, yet working. ¯\_(ツ)_/¯ If we would go this way, I am offering to do my part and write the script, if it would be of help. Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
