René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Automate reporting for BROKEN libraries","articleBody":"Right now, broken contributions are only visible in `contributions.yaml` through the `status: BROKEN` flag. \n\nIf a contribution go missing, we have to wait for someone to report that they don't appear in the contribution manager (like [here](https://discourse.processing.org/t/trouble-in-downloading-the-geomerative-library-processing/46287) for example)\n\nIt would be helpful to automate the reporting process when a library is first marked as `BROKEN`.\n\nFor example, we could open an issue automatically when a library is reported as `BROKEN` for the first time.\n\nOn a related note, we could add optional fields in `contributions.yaml` and submission issue template for the repository URL and GitHub username(s) of the author(s). This would make it easier to tag maintainers when their contribution goes down.\n\nWould love to hear thoughts on this. Happy to help if we decide to move forward!","author":{"url":"https://github.com/SableRaf","@type":"Person","name":"SableRaf"},"datePublished":"2025-04-28T17:52:14.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/70/processing-contributions/issues/70"}