At Flock 2017, @bex and @mattdm publicly said they'll do there best not to rely anymore on Red Hat's IT team for Zanata's hosting, by hosting Zanata in community infrastructure.
This should enable an upgrade to Zanata 4.x and thus, enabling:
This ticket is for G11N/L10N tracking purposes, other tickets are to expect with the relevant teams.
This may not wound up hosted in the Community infrastructure. What we have committed to working on is getting it into hosting that can be more regularly updated.
@bex, can you please write a tiny update here? We'll have meeting next monday. It would be great to have the status if this.
Metadata Update from @jibecfed: - Issue tagged with: l10n
Metadata Update from @jibecfed: - Issue marked as blocking: #19
Two related updates:
I met a person at Buildstuff.lt who may be interested in becoming a maintainer for our instance if we launch one. He would commit to doing upgrades and fixes on a best-effort basis.
There may be some movement from the team currently maintaining Zanata. @aeng and I are working with them.
with Zanata dead, I doubt this is an option anymore. If killing Zanata went unnoticed from what I know, I doubt Red Hat want the publicity of killing the hosting of the platform Fedora uses without helping to move to another one.
Metadata Update from @jibecfed: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
IMHO Zanata has not been killed. Only it is not in active development anymore. All its sources are still available if someone wants to use it and improve it.
From Fedora community perspective, now community has to decide which Translation platform they want use in long term.
Login to comment on this ticket.