First of all, thank you for including me on replies. Regarding the subject, I think that the best way to proceed would be to, essentially, create a task force to maintain chromium properly.
I don't think that I have the computational means to compile chromium frequently (I hope that using ccache and/or distcc can be used), but I may be interested in, participating in the effort. That being said, I think that inviting other people would be the way to go, including the maintainers from Linux Mint, and other distributions. There are other people maintaining chromium forks out there, IIRC, like a project called de-googled chromium, or something like that. Inviting all those people in a task force and working openly (and with redundant human resources) is, IMVHO, something desired, not only for chromium, but for other software. Since you mentioned armhf, Riku, we may try to get people from raspbian and other downstreams to also take part. Also, given enough hands, splitting components/vendored libraries that chromium quite possibly includes (like the last time that I checked) could be something desired for, say, security purposes and, also, for other teams (IIRC, there is a bunch of multimedia libraries that were vendored). (Of course, the "de-vendoring" should occur only when feasible). That is my vision of how the packaging could go forward. Thanks, Rogério Brito. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
