Then we can disregard my earlier notes about improved statistics exports.
Update on the issues we had in mind to be addressed
| Group | Challenge | Issue nr | Agreement on solution? |
|---|---|---|---|
| Admin | For each file there is one component. While Weblate directly supports markdown files (which we use for the website), importing them all would mean we have tens of components in Weblate. | #14237 | No. ‘Merging’ of MD files into single component not really an option (technically complex). However, we can probably agree to alternative solutions (@ByteHamster?): * UX for user: add a setting for component groups to hide lower levels, although this might not be necessary since other changes to groups would already make individual components less visible (e.g. #11198) * UX for admin: add more settings at component group level (e.g. contributor agreements; #14231) |
| Admin | To mark users as reviewer for a specific language, we need to create a team. | #14233 | Yes: allow to define languages per role per user |
| Admin | There’s no way to post string comments via the API | #14232 | Almost. Alternative API endpoint exists, tbc if that would work. |
| Admin | We can’t give a user the permission to post announcements | #8974 | Unknown |
| UX | The same contributor agreements has to be accepted multiple times | #14231 / #10897 | Almost (General idea to have some settings at project level seems OK, but exact working not specified yet. Also, not sure we would sponsor the full set of possible settings, mainly CLA relevant to us.) |
| UX | When on a component, there’s no clear path/call to action to start translating that component | #11198 | No. Requested UX (single translate button that is smart when possible) doesn’t seem accepted. Maybe this should be discussed in a call, or dropped until the coherent UX review is done (at which point we can sponsor some of those). |