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 has been approved by Housekeeping Robot <nm@debian.org>
3 weeks, 6 days ago.
Signed statements
| Statement |
Uploaded by |
Upload date |
Actions |
For nm.debian.org, at 2026-05-25:
I would like to apply to change my status in Debian to Debian Developer, uploading.
I have been contributing across several Debian packaging teams: the Chromium team,
Debian JavaScript Team, the Debian Rust Packaging Team, and the Debian Go Packaging Team.
My focus has been unblocking the newer Chromium build ecosystem in Debian and the dependency
chains around it.
The piece of this work I am most proud of so far has been packaging the CEF,
the Chromium Embedded Framework, the original ITP dates back to 2019. This took me
several months until the integration became ready into the Debian Chromium
pipeline itself, in direct coordination with the Chromium team and is currently
under final review.
Related contributions include siso (the modern Chromium build tool), and the ongoing
node-rollup v4 update with required pulling in swc and missing Rust creates with the Rust
packaging team. Also, the the ongoing packaging of the OpenTelemetry Collector stack and
its dependency chain, in coordination with other DDs.
I was also recently granted Maintainer access to xwpe on Salsa after addressing some long
standing bugs in the package.
I'd like to become a Debian Developer, uploading, in order to upload independently the packages
I work on and to continue tackling dependency chains that span multiple packaging teams.
I came to this decision after being encouraged by other Debian Developers.
Much of my work involves software with large dependency trees in different ecosystems,
where being able to upload independently would ease my ability to contribute.
I have active merge requests across these teams, and plan to continue maintaining these packages long-term.
Signed with key 2A84 0ED0 0DE6 69F4 219B 8B33 02A7 9E3B 8215 1695
|
mendezr |
2026-05-25 |
[view raw]
|
Log
| Date |
Author |
Action |
Content |
Public |
| 2026-05-25 21:34 |
mendezr |
add_statement |
Added a new statement |
yes |
| 2026-05-25 21:34 |
nm@debian.org |
req_approve |
New statement received, the requirement seems satisfied |
yes |
| 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 |