René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Make OSS Project More Resillient","articleBody":"As maintainer I want to be able to maintain the project, even if I left iteratec.\n\nBackground: This project was initially founded at [iteratec](https://www.iteratec.com) and some years ago published OSS. For historical reasons we have some things tightly coupled to that company (e.g. website on Netlify, Credentials in companies password manager etc. If there would be no maintainer hired at iteratc for some resons, maintain the project would be difficult for some aspects.\n\n### Thins to do\n\n- [x] #2897\n- [x] Add @J12934 and @Weltraumschaf as _project leads_ at OWASP (suggested by their guidelines).\n  - opened pul request: https://github.com/OWASP/www-project-securecodebox/pull/7\n- [x] Schedule an initial meeting with all core maintainers.\n- [x] #3052\n- [ ] #3051\n- [ ] #3092\n  - [ ] Fix https://github.com/secureCodeBox/secureCodeBox/issues/1904\n- [x] #3091\n- [ ] Write blog post about this (see. [Juice-Shop](https://owasp.org/blog/2025/01/29/juice-shop-leadership.html) as example).\n- [x] find a communication channel for meetings/discussion w/ maintainers outside iteratec organization.\n  - We use our old GSoC channel in Slack \"#project-securecodebox\".\n- [x] DockerHub images shlould not be published by \"iteratec GmbH\" but by \"OWASP\" or \"secureCodeBox\".\n- [ ] @Ilyesbdlala makes OWASP membership\n- [x] #3128\n- [ ]  Invite @rseedorff \u0026 @Ilyesbdlala to https://central.sonatype.com/\n\n### Resources\n\n- https://owasp.org/www-committee-project/","author":{"url":"https://github.com/Weltraumschaf","@type":"Person","name":"Weltraumschaf"},"datePublished":"2025-02-07T15:10:43.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/2896/secureCodeBox/issues/2896"}