Tootfinder

A Google bug report apparently leaks the planned Android desktop interface, showing a taller status bar, a new mouse cursor, Chrome extensions, and more (Abner Li/9to5Google)
https://9to5google.com/2026/01/27/android-desktop-leak/

Android’s full desktop interface leaks: New status bar, Chrome Extensions, more [Video]
A Google bug report on the Chromium Issue Tracker today has inadvertently leaked the Android desktop interface for the first time.

For a project to be truly #OpenSource (not to mention #FreeSoftware), it really needs to:
1. Have a *public* issue tracker that enables you to browse and search through issue reports *without* having to create an account.
2. Accept issue reports, with no strings attached. Yes, expecting registration is fine. Yes, expecting some effort to file a good bug report is fine. No, expecting people to ask permission, donate or otherwise put a lot of extra work to report a problem is not.
3. Do not close issue reports as "stale". Yes, it's fine to close a report if you really believe it was fixed, or if you asked for something and the user didn't reply for a long time. It's not fine to run a bot expecting users to jump every month so that the issue report that *you are ignoring* doesn't get closed.
If a project doesn't meet these, it's just a glorified throwaway code.

if anyone can help naming more specifically the following type of documents related to the MEP db of the EP website, so my FOIA request gets served:
- all specifications,
- all requirements,
- all bug/issue tracker items
- all budgetary decisions and their justification
- all contracts if this work is outsourced
i'm being stonewalled at