Declaration of intent
The most important requirement for changing status in Debian is to make sure that a person actually intends to do so.
This requirement looks incomplete.
Signed statements
| Statement |
Uploaded by |
Upload date |
Actions |
Log
| Date |
Author |
Action |
Content |
Public |
| 2026-05-23 18:02 |
mendezr |
- |
Adding context that I didn't include in the initial report, it's operational infrastructure rather than packaging work, but it may be relevant for evaluation:
I maintain debian.vejeta.com, an unofficial Debian repository with a CI/CD pipeline that publishes CEF builds and related packages (including CEF clients: stremio-gtk and brow6el) across multiple architectures.
It has been used by downstream users while integration into Debian proceeds. |
yes |
| 2026-05-23 17:55 |
mendezr |
- |
I would like to apply to change my status in Debian to Debian Developer,
uploading.
I have been working on packaging and maintaining software across several Debian
teams, focusing on unblocking the Chromium ecosystem in Debian. My main
contributions include:
- Packaging the Chromium Embedded Framework (CEF) as part of the Debian
Chromium project, currently under review by the Debian Chromium Team as a branch which I am maintaining going forward.
- Getting siso into the Debian archive.
- Driving the node-rollup v4 update within the Debian JavaScript Team, which
required coordinating with the Debian Rust Packaging Team to add missing SWC
ECMAScript crates to rust-swc-core.
- Packaging dependency chains in the Debian Go Packaging Team for
OpenTelemetry, its collector, and related packages.
I'd like to become a Debian Developer, uploading, in order to independently
upload the packages I work on and continue tackling dependency chains that span
multiple packaging teams. Much of my work involves large software with deep
dependency trees — CEF, node-rollup, OpenTelemetry — where being able to
package and upload independently would significantly ease my ability to
contribute. I have open ITPs and ongoing merge requests across the Go, Rust,
and JavaScript teams, and plan to continue maintaining these packages and their
dependencies long-term. |
yes |