Code That Shapes the Global Web
The SOCBB Project welcomes Open Source Engineering Firms and Independent Contractors to bid on SOCBB engineering contracts and deliver funded project work across the Chromium codebase.
Do you have the technical expertise to help us improve Chromium? Stay tuned for upcoming RFPs:
Open RFPs
Get Notified
Join the RFP notifications mailing list to receive emails as new RFPs open for bidding.
Review in-progress RFP reporting and progress
Visit SoCBB Github to learn about ongoing RFPs and the status of those projects.
Closed RFPs
Interoperability
Scope: Improving standards compliance and resolving interoperability issues across CSS features.
Web Tests Cleanup
Scope: The main objective is to improve the state of web tests in Chromium-based browsers. Test failures: Reducing the approximately 7,400 tests currently annotated in the TestExpectations file that are failing, timing out, crashing, or are flaky. Work includes analyzing the current situation, fixing code in the Chromium codebase, or fixing the tests themselves. Internal tests: Reducing the around 32,919 internal Blink tests (excluding external/ and wpt_internal/ subfolders) by migrating them to Web Platform Tests (WPT) or removing them if they are redundant. Work involves identifying areas for analysis, modifying useful tests to follow
WPT rules and exporting them, and removing tests already covered by WPT.
WPT Infra
Scope: Analyzing, triaging, and fixing infrastructure issues in the Web Platform Tests (WPT) repository to enhance cross-platform testing for Chromium features.
Coverage of Browser Implementation Status Metadata
Scope: Code and data changes related to browser implementation status metadata in web-features (tracking all shipped and in-flight features), browser-compat-data (providing the underlying compatibility data) and Chromium.
Tasks: Updates to web-features or browser-compat-data to accurately reflect the implementation status of web features in browser metadata for browsers and WebViews. Fixing issues related to code infrastructure supporting web-features and browser-compat-data proposed by Chromium contributors and approved by the SOCBB Steering Committee.
RFP Guidelines
To maintain a vendor-neutral, fair, and transparent procurement process under Linux Foundation governance, all applicants must meet the following criteria:
- Technical pre-qualification: Proposals must demonstrate verified experience in C++, system architecture, or direct upstream code contributions to Chromium, Blink, V8, or related engines.
- Open source compliance: All deliverables funded by SOCBB must be contributed back to the upstream Chromium project under compliant open-source licensing.
- Milestone-based procurement: Contracts are strictly performance-driven. Capital is allocated and disbursed upon the successful verification and code-review approval of agreed-upon technical milestones.
- Objective governance evaluation: Submissions are evaluated anonymously by the SOCBB Steering Committee based on architectural merit, codebase longevity impact, and execution feasibility.
How to Submit
Before submitting your proposal, please review all RFP Guidelines.
Submissions should be sent to: proposals@socbb.org.
Common Questions
Contracting
What happens if my bid is accepted?
You will receive an email upon bid acceptance containing a form for required contract information. Please allow 7–10 business days for the contract to be sent for signature once information is submitted.
What are the Terms and Conditions?
Contracts are written using the Standard Linux Foundation Paper, with the SOW and payment schedule added as an addendum. Contract language is not negotiable, as the Linux Foundation manages the contracting and payment processing
Execution
How will the project be managed?
The WG will manage the contractor’s progress and technical alignment. You will be required to produce bi-weekly reports to ensure constant visibility into the project’s health. Any technical or timeline challenges must be addressed promptly with the Steering Committee.
Invoicing
How do I invoice?
Please include the PO# listed on your signed agreement and a short description of the work covered. Invoice submissions should include links to your mandatory weekly reporting or a high-level outline of completed tasks. Please DO NOT send invoices directly to Linux Foundation AP; this will delay the approval process
Concluding the work
How will the project conclude?
The WG will monitor you until all tasks are complete per the SOW. The WG will then formally conclude your engagement. All final invoices must be approved by the WG prior to payment.