← 输入框|github.com|刷新
Skip to content

Make OSS Project More Resillient #2896

New issue
New issue
Open
Task
1 of 2 issues completed
Open
Make OSS Project More Resillient#2896
Task
1 of 2 issues completed
Assignees
WeltraumschafrfelberJ12934Ilyesbdlala
Labels
enhancementNew feature or request

Description

@Weltraumschaf
Weltraumschaf
opened on Feb 7, 2025

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

Resources

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 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

  7. Weltraumschaf commented on Apr 11, 2025

    @Weltraumschaf
    Weltraumschaf
    on Apr 11, 2025
    MemberAuthor

    @J12934 @rseedorff @Ilyesbdlala Poll for initial core maintainer sync: https://nuudel.digitalcourage.de/qreqJtEo2phRpQin

  8. Weltraumschaf commented on May 8, 2025

    @Weltraumschaf
    Weltraumschaf
    on May 8, 2025
    MemberAuthor

    Initial meeting: 26.5. 16:05-17:00.

  9. Weltraumschaf commented on May 26, 2025

    @Weltraumschaf
    Weltraumschaf
    on May 26, 2025
    MemberAuthor

    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
    Weltraumschaf
    on May 26, 2025
    MemberAuthor

    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:

  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
    Weltraumschaf
    on May 26, 2025
    MemberAuthor

    @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
    Weltraumschaf
    on Jun 3, 2025
    MemberAuthor

    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
    Weltraumschaf
    on Jun 11, 2025
    MemberAuthor

    Filed an issue at OWASP to get access to create a Shared Drive in Google Workspace.

  17. Weltraumschaf commented on Jun 16, 2025

    @Weltraumschaf
    Weltraumschaf
    on Jun 16, 2025
    MemberAuthor

    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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

Task

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions