Make OSS Project More Resillient #2896
Description
As maintainer I want to be able to maintain the project, even if I left iteratec.
Background: This project was initially founded at iteratec 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.
Thins to do
- Migrate all secrets/credentials needed to maintain the project into a "public" password manager available to the team. #2897
- Add @J12934 and @Weltraumschaf as project leads at OWASP (suggested by their guidelines).
- opened pul request: Add Jannik And Sven As Project Leads OWASP/www-project-securecodebox#7
- Schedule an initial meeting with all core maintainers.
- Schedule monthly meeting in project calendar #3052
- Write an public On-/Off-Boarding. Currently we only have such in iteratec's internal wiki. #3051
- Request securecodebox.owasp.org subdomain #3092
- Who should posses the domain securecodebox.io? #3091
- Write blog post about this (see. Juice-Shop as example).
- find a communication channel for meetings/discussion w/ maintainers outside iteratec organization.
- We use our old GSoC channel in Slack "#project-securecodebox".
- DockerHub images shlould not be published by "iteratec GmbH" but by "OWASP" or "secureCodeBox".
- @Ilyesbdlala makes OWASP membership
- Clarify Access to OWASP Project Repo #3128
- Invite @rseedorff & @Ilyesbdlala to https://central.sonatype.com/
Resources
Sub-issues
Metadata
Metadata
Labels
Type
Projects
Status