#musicbrainz

+1 for weblate. I think it's both better for developers and translators, more features, is open source and the developer is a nice guy. It's also easy to host. Given this is a small project and MB is a comparable big project it would maybe make sense for MB to have their own instance and not relying on their open source hosting offering. But of course this can also directly be discussed with the guy behind

weblate

darwin: And that is how I know you haven't read it.

comradekingu: or that I don't care that much about things like cookie policies.

comradekingu: One of the existing workflows is that a couple of the translation files are used by multiple projects, which is currently handled well by `tx pull`. How would Weblate handle this?

There is an API to engage with

Can use TX memory population across projects

TM*

should we put the weblate idea ting on the meeting agenda?

seems that quite a few people liek this idea. outsidecontext, zas, myself

we can just evaluate it first without needing to take a decision in meeting

I also looked at pontoon and pootle that have been mentioned too in the past

but pootle’s development seems to be inactive