Formalize API Backlog meeting time anchor: UTC vs. CET/CEST impact on APAC participants

[albertoramosmonagas]

Problem description
The API Backlog meetings currently follow a CET/CEST time anchor (Central European Time), which includes daylight saving time shifts. While this reflects the current participant preference, it was never formally discussed or agreed upon at the working group level. This creates an implicit assumption that may affect scheduling and participation for attendees in APAC and other regions where DST works differently or not at all.

Shifting from UTC (DST-agnostic) to CET/CEST (DST-dependent) requires consensus from all affected regions to ensure fair scheduling and reduce friction.

Expected action

1. Bring this decision point to the next API Backlog meeting agenda
2. Gather input from APAC, Americas, and other regional participants on time preferences
3. Document the decision and reasoning in the Backlog governance docs
4. If CET/CEST is confirmed as the anchor, document the DST offset rules for clarity

[albertoramosmonagas]

Decision from the last backlog meeting: Shift to UTC anchor

[hdamker]

Decision from the last backlog meeting: Shift to UTC anchor

@albertoramosmonagas just checked: the API Backlog Meeting ARE anchored on UTC - no action needed regarding the setup. You should be able to see it in your calendar that the meetings are bi-weekly either on 08:00 or 15:00 UTC (look for meetings before and after the change from CEST to CET). That is also correctly reflected in https://github.com/camaraproject/APIBacklog/blob/main/README.md.

BTW: also in line with the general policy for meeting setups in CAMARA, as decided here: camaraproject/Governance#164

[albertoramosmonagas]

Closing this PR following the API Backlog WG discussion on #334. The WG confirmed that UTC should remain the meeting time anchor, which is already what the README uses. Since no substantive change is needed, closing this as resolved.