| Version 7 (modified by , 3 years ago) ( diff ) |
|---|
Work in progress, please help improve this page
Introduction
This is our Sovereign Tech Fund Application creation page.
Information for Developers
Getting Started
Please familiarize yourself with [STF](https://www.sovereigntechfund.de/programs/applications)
Then look over Projects below and add yours or add yourself to an existing one. Do not hesitate to improve the templates if you see issues.
Foobar work
Description: Improve the foo bar
Expected results: a foo bar that has fully thread safe logging
Duration: 350 hours
Payment: 28,000€
Developer: Donald Duck
Barfoo work
Description: Work on improving the bar foo
Expected results: Spend 6 month fulltime work on improving bar foo, fixing bugs and regression people report, refactor the code to make it more maintainable
Duration: 6 Months
Payment: 35,000€
Developer: NA
Resolve Coverity Bugs
Description: Coverity is a static code analysis system that is used to analyze FFmpeg code to find bugs with an emphasis on quality and security issues. There are currently 674 open issues. And only little will from the community to work on resolving them. This project proposes to pay 70 USD per issue resolved.
Expected results: close to 0 remaining issues
Duration: whatever time it takes
Payment: 47,180€ (if all 674 issues are resolved) or proportionally less if its a subset
Developer: michaelni (feel free to replace me with yourself if you want to do it for less) or add yourself if you want to help at the same USD per issue
Fix ossfuzz coverage
Description: ossfuzz coverage testing is important and broken. There seems no will to fix it as it has been broken for years. But its very important to know what areas are covered by the fuzzers. A big problem was that the ossfuzz infra had many restrictions from timeouts, very slow build within docker, and limitations on everything with shared libs not allowed and the requirement of a single binary per test. It may be some of these restrictions are no longer applicable. Fixing this can be done within the ossfuzz infra or also on a newly setup system that is free of restrictions.
Expected results: working, automated and robust ossfuzz coverage testing
Duration: ?
Payment: Choosen by Developer when she adds herself
Developer: NA
Merge FFmpeg Forks
Description: FFmpeg has been forked, it is in the interresst of our users that all improvement and bug fixes are integrated in main FFmpeg
Expected results: bring all changes from a specified fork through the review process on ffmpeg devel. Each change may be accepted or rejected with explanation. Alternatively we could instead specify here the number of hours work and leave it open how much would be merged
Duration: 12 months
Payment: 50,000€
Developer:
The text below is our Application to STF
# FFmpeg Project Description
Department: Program Team, Scoping.
Maintainer: Tara
Purpose: Prepare a project description for review board.
### 1) Describe the technology this effort will support.
The proposed effort aims to support FFmpeg, a leading multimedia framework recognized for its versatile capabilities. FFmpeg serves as a comprehensive solution for decoding, encoding, transcoding, multiplexing, demultiplexing, streaming, filtering, and playback of a wide array of multimedia formats. It stands out by seamlessly handling formats from ancient, obscure standards to cutting-edge ones, making it a cornerstone in the multimedia processing landscape.
### 2) Where is this technology being used? Why is it relevant and critical? How does this technology serve the public interest?
FFmpeg is a ubiquitous technology deeply embedded in the fabric of modern multimedia processing, touching the lives of millions daily. It is an integral component in a vast array of end-user devices, including desktops, laptops, mobile phones, smartwatches, and smart TVs. FFmpeg powers major video distribution and streaming platforms like YouTube, Vimeo, AWS, and Microsoft Azure, shaping the landscape of online content consumption.
The technology extends its influence to TV broadcasts over IP, enabling seamless delivery of multimedia content to a global audience. Beyond mainstream applications, FFmpeg is employed in diverse sectors, from archival projects to the Mars Rover Perseverance, showcasing its adaptability and reliability.
The relevance and criticality of FFmpeg lie in its role as the backbone of multimedia processing. It serves the public interest by facilitating the seamless functioning of everyday technologies, from video playback in web browsers like Firefox and Chromium to applications like Kodi, MPlayer, and OBS Studio. Furthermore, FFmpeg plays a crucial part in public sector uses, website interactions, and even in the transmission of multimedia content within emails. In essence, FFmpeg's impact is far-reaching, touching both private and public spheres, and its reliability is paramount for the secure and efficient functioning of digital multimedia across diverse applications and use cases.
### 3) What are the problems the proposed work is trying to address? What activities do you propose and how do they address the problems described? How do those activities fit into [STF’s mission](https://www.sovereigntechfund.de/mission)?
The proposed work addresses critical challenges in maintaining FFmpeg's sustainability, security, and innovation. Activities include:
- Security Fixes and Hardening: Addressing bugs and enhancing security through improvments of the fuzzing system.
- Administration of FFmpeg Infrastructure: Ensuring robust infrastructure management for reliability and performance.
- User Support: Enhancing user support via TRAC and mailing lists for improved community engagement.
- Improvements in Codecs, Formats, and Filters: Enhancing existing implementations.
These activities align with STF’s mission by supporting the maintenance and security of open source components and strengthening the Open Source ecosystem.
### 4) Who is going to be performing the work and how are they qualified to do so?
The work will be performed by key contributors from the FFmpeg project and other experienced developers. Their qualifications are demonstrated through years of active involvement in FFmpeg development, with expertise in code contributions, code review, user support, and administration.
### 5) How is the technology maintained or governed? Is there a community behind the technology, and do they approve of the work?
FFmpeg's maintenance and governance involve a flat hierarchy, with decisions made transparently through mailing lists. The project boasts a robust community of administrators, maintainers, and contributors who actively engage in decision-making processes. The proposed work aligns with the community's focus on quality, security, and openness, gaining approval through consensus-driven discussions.
### 6) Describe the Milestones Using the Template below
Milestone 1: Ecosystem and Infrastructure Support
Cost:
Duration: Throughout the Project (12 months)
In this initial milestone, the focus is on fortifying FFmpeg's security posture and ensuring the robustness of its infrastructure. It also furthers the enhancement of user support mechanisms through TRAC and mailing lists. Activities include:
- Security Fixes and Hardening (€??.???): Fix the majority of coverity issues (674 issues), fix coverage testing of existing oss-fuzz in some form (possibly on seperate infra)
- Administration of FFmpeg Infrastructure (€??.???): Enhancing the overall administration and reliability of FFmpeg's infrastructure.
- User Support via TRAC and Mailing List (€??.???): Streamlining user support mechanisms through TRAC and the user mailing list.
- Reviewing Code Submissions (€??.???): Ensuring the quality and security of code submissions through a robust review process.
Milestone 2: Enhancing Existing Implementations (€??.???)
This milestone is dedicated to advancing existing codecs, formats, and filters within FFmpeg. Activities include:
- Improving ABCD (€5,000): Enhancing the functionality and efficiency of ABCD. (X Months)
- Improving EFGH (AAAA) Muxer/Demuxer (€7,000): Addressing inefficiencies and improving the handling of EFGH formats. (Y Months)
### 7) Please fill out the following Supplementary Information
- Preferred Mode of Invoicing:
- Contracting Entity (Is it a fiscal host?): SPI
- Total Budget Requested:
- Requested Fully Loaded Hourly Rate (Total cost divided by number of person hours):
- Project Actual Duration: 12 Months
- Earliest possible starting date:


