Contribo
ProgramsOrganizationsProjectsProposal StudioResourcesOrbit AIDashboard
Login
Login
Contribov1.0

Your premium companion for discovering, matching, and tracking paid open-source mentorship programs and verified starter issues.

Product

  • Programs Directory
  • Orbit AI
  • User Dashboard

Resources

  • Guides & Resources
  • Proposal Studio

Community

  • GitHub Repository
  • Code of Conduct

Legal

  • Privacy Policy
  • Terms & Conditions
  • Cookie Policy
  • Accessibility Statement

Made with love bySubhranshu Sekhar Dash

© 2026 Contribo. Built for the global open-source community.

PlatformProjects

Explore Projects

Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.

Confused which project to choose or don't know which one you are most suitable to work on?

Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.

Match with Orbit AI
Filters Clear
2933 Projects Found
Sort by

Using Formal Methods for Comprehensive Malformed Packet Handling in BGP Implementations Mentorship Project

Intermediate
•Varies

Ready to Apply?

Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.

Start Proposal
Proposal Status
0% ProgressNot Started
Accepted Proposals
3 SimilarView →
Proposal Guide
Tailored DocsOpen →
Checklist & Review
Readiness AuditCheck →
175h (Medium)

<p><strong>*APPLICATION ONLY ACCEPTING US BASED COLLEGE STUDENTS*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>As an Internet-facing networking protocol, BGP is one of the most critical components of cloud-scale networks. It enables routing information exchanges between a cloud network and the broad Internet, and incorrect behavior could devastate the connectivity of entire regions. Among many vulnerabilities, the proper handling of malformed packets is particularly important due to the propagation mechanisms of BGP. In real production network, a single mis-handling could result in cascading BGP message floodings across entire regions, degrading services or even causing network outages.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>Currently, high-level BGP behaviors are well-defined through various RFCs. However, low-level details, such as the validation and handling of malformed packets, are often under-specified. Current testing relies on ad-hoc fuzzing or manual test cases, which may miss subtle state-machine interactions that require specific input combinations.</p><p><br></p><p>The objective of this mentorship is to apply formal methods to systematically validate the handling of malformed packets by concrete BGP software implementations. Unlike traditional approaches, formal methods use mathematical logic to systematically explore diverse behaviors triggered by different input combinations, providing comprehensive validation coverage.</p><p><br></p><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>A formal specification that describes high-level BGP interactions.</li><li>A set of implementation-agnostic safety invariants derived from the above high-level model. They ensure that invariant-abiding interactions will not cause cascading effects on neighboring BGP devices.</li><li>A reusable framework that applies off-the-shelf formal methods tools to systematically test concrete BGP implementations against the above invariants.</li><li>A benchmark suite of validated malformed packet scenarios with coverage metrics.</li><li><strong>SUMMER / FALL TERM (20~ HOURS OF WORK EACH WEEK)</strong></li></ul><p><br></p><p><br></p><p>Recommended Qualifications</p><p><br></p><ul><li>Familiarity with Python and C/C++</li><li>Basic understanding of networks and routing</li><li>Good analytical skills</li></ul><p><br></p>

TBA
Proposal

Mirror Serial Console Traffic in SONiC Mentorship Project

Intermediate
•Varies175h (Medium)

<p><strong>*APPLICATIONS ONLY OPEN TO STUDENTS LOCATED IN CHINA*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>SONiC supports serial console management using console switch functions, enabling it to act as a terminal server and control devices through the serial console. Diagnosing issues with the serial console can be challenging because the connection is exclusive, so only the user on that line knows what’s happening. For Ethernet, SONiC users can leverage the Everflow feature to mirror data plane traffic or use tcpdump to monitor control plane traffic. In the context of serial consoles, however, a new feature is needed to mirror serial console traffic, which would greatly assist with diagnosing console problems.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>The goal of this project is to create and implement a new SONiC feature that lets users start or stop recording for a specific console line whenever needed.</p><p>Key features include:</p><ul><li>Designing a file format to store the serial console data stream, with configurable time resolution.</li><li>Mirroring incoming (RX) data streams to a local file.</li><li>Mirroring outgoing (TX) data streams to a local file.</li><li>Adding CLI support to start or stop recording for any serial console line.</li><li>Additional desired features are:</li><li>Mirroring the CTS flow control signal to a local file.</li><li>Mirroring the RTS flow control signal to a local file.</li><li>Providing encryption for recordings.</li><li>Implementing gNOI APIs to enable start/stop recording for specific serial console lines.</li><li>The feature will be implemented in Python based on existing serial console infrastructure which allows developer to manipulate serial console data stream.</li></ul><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>HLD document for console mirroring feature</li><li>Implementation details of console mirroring</li><li>Test plan for console mirroring</li><li>Test cases for console mirroring</li></ul><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li>Familiarity with a common programming language (Python, Java, C, C++, Rust, etc.)</li><li>Basic Linux knowledge</li><li>Basic SONiC knowledge (preferred)</li><li>AI or vibe coding experience (preferred)</li></ul>

TBA
Proposal

Secret-Sourced HTTP Headers and CRD-Based Config Management (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>KubeVela's workflow engine and config management layer have two long-standing production gaps that this mentorship will close together. First, the `request` workflow step has no native way to source HTTP headers (bearer tokens, API keys, basic auth) from Kubernetes Secrets — users wanting to call authenticated APIs are forced to hardcode credentials directly in the workflow definition, where they end up visible in `kubectl get` output and Git history. On top of that, attempts to interpolate values into the `header` map using Go templates or CUE string interpolation regularly conflict with native CUE syntax, producing un-rendered strings or silent execution failures. Second, KubeVela's Config Management today stores `ConfigTemplate`s as labeled ConfigMaps (`config-template-*` prefix) and `Config`s as labeled Secrets — there are no proper Kubernetes API types (`kubectl get configs` returns nothing meaningful), and all CUE schema and `validation.$returns` checks run client-side in the `vela` CLI. Configs created through any other path (workflow steps, VelaUX, direct `kubectl apply`) bypass validation entirely, so the same template enforces different rules depending on the entry point. The mentee will tackle both. The first deliverable extends the HTTP provider in `kubevela/workflow` with a `headerFromSecret` field that resolves values from Kubernetes Secrets natively in Go (mirroring how the same provider already handles Secrets for `tlsConfig`), and exposes it as a first-class CUE parameter — bypassing the templating layer entirely. The second introduces a proper Kubernetes API group, `config.oam.dev/v1alpha1`, with `ConfigTemplate` and `Config` CRDs, event-driven controllers built on controller-runtime, and validating admission webhooks that move CUE validation server-side. Sensitive properties never live in the CRD — they sit in a separate Secret referenced via `propertiesFrom.secretRef`. A dual-read controller preserves full backward compatibility: legacy ConfigMap templates, old CLI versions, and existing Secret-based configs continue to work without disruption. Together, the two deliverables harden KubeVela's HTTP integration surface and modernize its configuration layer into a Kubernetes-native, GitOps-friendly API.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- New `HeaderFromSecret` field on the `Request` struct in `pkg/providers/http/http.go` (kubevela/workflow), with native Secret resolution inside `runHTTP()` mirroring the existing `getTransport()` TLS pattern</p><p>&nbsp;- Updated `request.cue` definition in kubevela/kubevela exposing `headerFromSecret` as a parameter, with namespace defaulting to `context.namespace`</p><p>&nbsp;- New `config.oam.dev/v1alpha1` API group with `ConfigTemplate` and `Config` CRDs, DeepCopy, and scheme registration</p><p>&nbsp;- `ConfigTemplateReconciler` that parses CUE templates and writes the generated OpenAPI schema to `status.schema`</p>

TBA
Proposal

SONiC Test Runtime Optimization Mentorship Project

Intermediate
•Varies175h (Medium)

<p>*APPLICATIONS ONLY OPEN TO STUDENTS BASED IN CHINA*</p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>The sonic-mgmt test framework is a critical component of PR validation and continuous integration. However, over time, several inefficiencies have accumulated:</p><ul><li>Some individual test scripts run longer than 30 minutes, and some individual test cases exceed 10 minutes, PR pipelines retry failed test scripts up to two additional times, amplifying runtime cost.</li><li>Long-running scripts disproportionately consume KVM CPU resources.</li><li>Excessive runtime increases PR turnaround time and reduces CI throughput.</li></ul><p><br></p><p>Currently, there is no formal runtime governance framework, no enforcement threshold, and limited visibility into runtime regressions across scripts, test cases, topology types, and branches.</p><p><br></p><p>As SONiC continues to scale, unmanaged test runtime growth will:</p><ul><li>Increase infrastructure cost</li><li>Slow down PR validation</li><li>Reduce contributor productivity</li><li>Impact overall CI system stability</li></ul><p>This project aims to establish a data-driven runtime governance and optimization framework for sonic-mgmt.</p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>The mentee(s) will work on designing and implementing a structured runtime optimization initiative that includes:</p><ul><li>Refactor selected high-impact long-running test scripts</li><li>Propose test case optimization strategies:</li><li class="ql-indent-1">Reduce loop/iteration counts</li><li class="ql-indent-1">Reduce coverage where representative sampling is sufficient</li><li class="ql-indent-1">Optimize setup/teardown overhead</li><li class="ql-indent-1">Remove redundant waits</li></ul><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><p>By the end of the mentorship program, the following deliverables are expected:</p><ul><li>Refactored high-impact test scripts demonstrating measurable improvement</li><li>A structured runtime dataset and analysis report</li><li>A documented SONiC Test Runtime Best Practices guide</li></ul><p><br></p><p><strong>Recommended Qualifications</strong></p><ul><li>Python programming skills</li><li>Familiarity with pytest framework</li><li>Basic understanding of CI/CD systems</li><li>Ability to analyze data (Kusto / SQL / Pandas experience preferred)</li><li>Understanding of networking fundamentals (basic SONiC knowledge preferred)</li></ul>

TBA
Proposal

SONiC OS Profiling Mentorship Project

Intermediate
•Varies175h (Medium)

<p>*APPLICATIONS ONLY OPEN TO US BASED COLLEGE STUDENTS*</p><p><br></p><p>1. Problem Statement</p><p><br></p><p>Today, SONiC KVM-based PR testing validates functional correctness (test pass/fail) but does not track resource consumption or performance characteristics over time. This creates several blind spots:</p><p><br></p><ul><li>Performance regressions (CPU spikes, memory leaks, excessive I/O) introduced by PRs go undetected until they reach production or nightly pipelines.</li><li>There is no historical baseline of resource utilization per feature branch, making it impossible to distinguish normal variance from genuine degradation.</li><li>Nightly test environments lack systematic profiling, so gradual performance erosion across releases is invisible until a tipping point is reached.</li><li>Root-cause analysis of production incidents is hampered by the absence of correlated profiling data from the CI/CD stage where the regression was introduced.</li></ul><p><br></p><p>Without a structured profiling database and automated anomaly detection, the team operates reactively—discovering performance issues in production rather than catching them at the PR gate.</p><p><br></p><p>2. Proposed Solution</p><p><br></p><p>Build an end-to-end performance profiling pipeline that runs alongside SONiC KVM-based test execution, stores results in a centralized database, and automatically flags regressions at the PR gate.</p><p><br></p><p>2.1 High-Level Architecture</p><p><br></p><p>The solution is composed of four core components that integrate into the existing CI/CD and nightly test workflows:</p><p><br></p><ul><li>Profiler Container – A lightweight Docker container packaging the community profiler (e.g., py-spy, perf, cProfile) that runs in sidecar mode alongside the SONiC KVM during test execution.</li><li>Profiling Database – A remote time-series/relational database (e.g., PostgreSQL + TimescaleDB or InfluxDB) that stores per-run profiling snapshots keyed by feature branch, commit SHA, test case, and timestamp.</li><li>Analysis Engine – A statistical analysis module that performs comparative, clustering, and outlier detection on profiling data to identify spikes against historical baselines.</li><li>PR Gate Integration – A CI pipeline step that queries the analysis engine after test completion and fails the PR if any metric exceeds the configured threshold.</li></ul><p><br></p><p>3. Mentorship Objectives</p><p><br></p><ul><li>Help the mentee learn about SONiC OS architecture, container ecosystem, and KVM-based testing infrastructure.</li><li>Help the mentee gain hands-on experience with performance profiling tools (py-spy, perf, pidstat) and statistical analysis techniques.</li><li>Help the mentee understand CI/CD pipeline integration and automated quality gates.</li><li>Work with virtual SONiC testbeds (vsonic) to develop and validate the profiling pipeline without physical hardware.</li><li><strong>This is a summer term program, Mentees are expected to work 40~ hours a week</strong></li></ul>

TBA
Proposal
Showing 2929 - 2933 of 2933 Projects
121122123