Skip to content

Home

Jump to bottom
Leif Gaebler edited this page Jan 30, 2026 · 29 revisions

Get Started in DevSecOps

Welcome to the DevSecOps team at Saayam For All!
This page is here to answer common questions new members have and guide you through your first steps.

🛠️ Step 1: Complete the Beginner Task

Before contributing, every new member needs to set up and understand the existing system architecture.
Follow these links in order:

  1. Assign yourself to the Getting Started task for tracking purposes (such as timesheets).
  2. New Volunteer Onboarding (starting point)
  3. Project Documentation (what the project is trying to achieve)
  4. System Architecture (overall architecture)
  5. DevSecOps CI/CD Proposal (DevSecOps branch-specific architecture)
  6. AWS Access Request Form (get access to our AWS instances)

✅ After going through these, you should understand:

  • The overall project goals
  • The system architecture and where DevSecOps fits in
  • How to access and interact with our AWS environments

🔎 Step 2: Choose What You’d Like to Work On

Once you’ve finished the beginner task, think about:

  • Which areas interest you most
  • Where your past experience fits in
  • What new skills you’d like to learn

Then, check our open issues here:
DevSecOps Open Issues

Please note: Specifically check out the To-Do and Backlog section of our Kanban Board to identify the issues we are prioritizing. They will be P0 or P1 issues (again marked on the task itself).

👥 Step 3: Connect With the Team

  • If an issue is already assigned, reach out to the member(s) working on it to coordinate. It's likely that if no progress updates are being seen on the GitHub comments for more than 3 weeks the volunteer might be unavailable and you can still work on the same task.
  • If an issue is unassigned, feel free to take it up after letting the Project Managers (PjMs) or Product Managers (PMs) know.
  • If you’re not sure which issue to start with, contact the PjMs/PMs and share:
    • Technologies you’ve worked with before, or
    • Technologies you’re interested in learning.
      They’ll help align you with the right issue.
  • As a DevSecOps team member, you will also help other teams with possible build support/security issues if something goes wrong due to a non-dev reason. You must thus be aligned with a particular repository at all times. Please check our DevSecOps Dashboard to know it's current status and where availability is needed.

Frequently Asked Questions

Q: Where do I start if I know nothing about DevSecOps?
Start with the beginner task (Step 1). It’s designed to get you familiar with our system quickly.

Q: Do I need prior experience in security or DevOps?
Not at all! Many members are learning as they go. Just let us know what you want to work on.

Q: Who do I reach out to if I’m stuck?
Your first points of contact are the members assigned to the issue you are working on. If there's no movement there then reach out to Project Managers (PjMs) and Product Managers (PMs). Weekly meetings are scheduled to bring alignment between members.

Q: Can I switch to a different task later?
Yes! If you find something else more aligned with your interests, just let the PjM/PM know.

Q: How do I track my progress?
Use the Kanban board in GitHub Projects:

  • In Progress → Tasks you’re actively working on (including pre-readings).
  • Blocked → Tasks where you need support.
  • To Do → Leave tasks here if you haven’t started.

Welcome aboard — we’re glad to have you here! 💡

Clone this wiki locally