Description

Weltraumschaf

opened on Feb 7, 2025

Issue body actions

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
  • Fix CNAME for www #1904
• 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 to FOSSA
  • [email protected]
  • [email protected]
  • [email protected]
  • Ilyes OWASP?
• Invite @rseedorff & @Ilyesbdlala to https://central.sonatype.com/
  • Invite to FOSSA
• @rfelber reactivate [email protected]

Resources

• https://owasp.org/www-committee-project/

Activity

1. Weltraumschaf

   added this to secureCodeBoxon Feb 7, 2025
2. Weltraumschaf

   converted this from a draft issue on Feb 7, 2025
3. Weltraumschaf

   self-assigned this

   on Feb 7, 2025
4. Weltraumschaf

   added

   enhancementNew feature or requestNew feature or request

   on Feb 7, 2025
5. Weltraumschaf

   assigned

   J12934

   and

   rfelber

   on Feb 7, 2025
6. Weltraumschaf

   added a sub-issue on Feb 7, 2025

   • Migrate all secrets/credentials needed to maintain the project into a "public" password manager available to the team. #2897
7. Weltraumschaf commented on Apr 11, 2025

   

   Weltraumschaf

   on Apr 11, 2025

   MemberAuthor

   More actions

   @J12934 @rseedorff @Ilyesbdlala Poll for initial core maintainer sync: https://nuudel.digitalcourage.de/qreqJtEo2phRpQin
8. Weltraumschaf commented on May 8, 2025

   

   Weltraumschaf

   on May 8, 2025

   MemberAuthor

   More actions

   Initial meeting: 26.5. 16:05-17:00.
9. Weltraumschaf commented on May 26, 2025

   

   Weltraumschaf

   on May 26, 2025

   MemberAuthor

   More actions

   Agenda for Initial Meeting 26.5. 16:05-17:00

   1. Are all fine with Ilyes becoming Core Maintainer?
   2. Does Ilyes also want to have a picture on the website?
   3. Naming:
      • current Robert -> Inventor, Jannik & Sven -> Core Team
      • Better OWASP-speak: Project Lead?
      • Better Robert -> Inventor, Jannik, Sven & Ilyes Core Maintainer?
   4. How often do we want to do the sync?
      • Which infrastructure? Google Hangout/Calendar from OWASP?
   5. Do we want to make/document the agenda/meeting notes public somewhere?
      • Google Docs from OWASP?
      • We could also write down the results there.
      • How does the Juice-shop do it?
10. Weltraumschaf

    assigned

    Ilyesbdlala

    on May 26, 2025
11. Weltraumschaf commented on May 26, 2025

    

    Weltraumschaf

    on May 26, 2025

    MemberAuthor

    More actions

    Meeting Notes for Initial Meeting 26.5. 16:05-17:00

    Attendees: Robert Felber (@rseedorff), Ilyes Ben Dlala (@Ilyesbdlala), Sven Strittmatter(@Weltraumschaf); on sick-leave Jannik Hollenbach (@J12934), Sven stands in for Jannik.

    Results and decisions from the meeting:

    1. Robert is totally fine that Ilyes becomes a new core maintainer.
    2. Ilyes is totally fine to be published with foto on the website.
    3. We use the OWASP Naming schema: Robert, Jannik, Ilyes and Sven are project leads. To become project lead it is mandatory to be in the GitHub core team. On the other hand, someone in the core team is not automatically project lead.
    4. We begin with a monthly meeting. We use the same time slot. So schedule will be Monday 16:05-17:00 CET every 4 weeks from today on. We use the OWASP infrastructure (Google Meet and Calendar).
    5. We want to use the OWASP infrastructure, but nobody knows how we can get a space in Google Workspace for our project. Idea is to use a shared calendar for scheduling the sync meeting and docs to store agenda and meting notes. Sven will ask Björn from Juice-Shop how to achieve that.
    6. Others
       • We should document a public version of the on-/off-boarding, which resides in iteratec's private wiki at the moment.
       • Verify that Robert and Ilyes have access to the project's 1Password.
       • Who should own the domain securecodebox.io. At the moment iteratec is the owner. Other options are giving it to the OWASP or one of the maintainer owns it. But all of these lead into the problem that this one entity can go rogue and misuse the domain. We have no good solution for that and post pone the problem.

    Todos:

    • Add Ilyes with picture to the website.
    • Rename all persons on the website to project lead.
    • Ask Björn how/where to get project space in Google Workspace.
    • Schedule monthly meeting in project calendar.
    • Add a project management site in the documentation to place on-/off-boarding there.
    • Verify, and invite if necessary, that Robert & Ilyes have access to 1Password.
12. Weltraumschaf

    added 2 commits that reference this issue on May 26, 2025

    secureCodeBox#2896 Add Ilyes As Project Lead

    b1f3406

    secureCodeBox#2896 Add Initial Draft For Project Management Documenta…

    7fcea7e
13. Weltraumschaf commented on May 26, 2025

    

    Weltraumschaf

    on May 26, 2025

    MemberAuthor

    More actions

    @rseedorff @Ilyesbdlala I invited you to !password. Invitation is 5 days valid.
14. Weltraumschaf

    added 2 commits that reference this issue on Jun 2, 2025

    #2896 Add Ilyes As Project Lead

    af4523d

    #2896 Add Initial Draft For Project Management Documentation

    054bf6f
15. Weltraumschaf commented on Jun 3, 2025

    

    Weltraumschaf

    on Jun 3, 2025

    MemberAuthor

    More actions

    I asked Björn from Juice-Shop and Jan from CycloneDX. Both have no idea how this works with Google Workspace. Bjorn told me I should ask Starr Brown. She didn't react in Slack. I try to find out more via Tobias...

    Got some help in Slack:

    The easiest way is to create a Shared Google Drive and give your team r/w rights and r/o to the rest of the OWASP Foundation organisation or (world).
    https://support.google.com/a/users/answer/9310249?hl=en
16. Weltraumschaf commented on Jun 11, 2025

    

    Weltraumschaf

    on Jun 11, 2025

    MemberAuthor

    More actions

    Filed an issue at OWASP to get access to create a Shared Drive in Google Workspace.
17. Weltraumschaf commented on Jun 16, 2025

    

    Weltraumschaf

    on Jun 16, 2025

    MemberAuthor

    More actions

    We have a shared drive for our project. I've moved the meeting notes and a template there.
18. J12934

    added a sub-issue on Aug 7, 2025

    • Request promotion of project to Production Level. #3186

Issue actions