2. Yet Another Call Blocker
3. Store metadata
4. English
5. Translate

@xynngh For old changelogs, auto-populating (however that is done) and using the "strict-same" flag from https://docs.weblate.org/en/latest/user/checks.html#checks would do?

@kingu I'd rather avoid translating changelogs altogether, because I usually write them right before tagging a new version.

@xynngh If you make me a moderator I could do it when I remember to. Posting any new strings triggers updates for translators, but even if not making it into your release, they should get picked up for the F-Droid build I should think.

@kingu I don't want to involve any extra manual tasks. I don't think F-Droid uses untagged metadata, but I'm yet to check it.

@xynngh I think using string name="string_name" translatable="false" for source strings would do. It doesn't even have to be done every release to save a lot of effort.

@kingu That works for Android's strings.xml, but not for metadata which is just a bunch of separate txt files. The changelogs should either be translated (if F-Droid picks them up even untagged) or Weblate people should be consulted.

@xynngh I think just leave an accouncement for the component via the Weblate system works then. How it is set up now isn't different from other projects, and people generally don't translate old changelogs.