We are getting less than 1 update per month, while we have very fast release cycles. This result in huggle localizations being less and less reliable as what is now on translatewiki is usually outdated by order of weeks.
Can we get some automatic sync, especially from repo to translatewiki, like every second day and sync from translatewiki to repo once a week?
Version: unspecified
Severity: enhancement
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T67950 Make Huggle 3 interface fully localizable | |||
| Invalid | None | T70853 Set up automatic sync for Huggle with translatewiki.net |
You can always poke us via IRC and email. Rewriting our repository handling is on our roadmap, and that will allow us to automate syncing further, but getting there will take a while.
so if I programmed a bot that would poke you on IRC every second day, would it work? :P
(In reply to Peter Bena from comment #4)
@Nemo by assigning this to me are you suggesting to write the bot?
No, I reset assignees to default because what currently in bug summary ("Set up automatic sync with translatewiki.net") is not something any translatewiki.net staff will do. This is in "Huggle" product, your call.
product is irrelevant, this is something to be handled by translatewiki people and according to comment from Niklas "Rewriting our repository handling is on our roadmap" I don't think that this is something they wouldn't ever do as you say. So I think assignee was right, if there is translatewiki product you can move this bug there.
(In reply to Peter Bena from comment #6)
product is irrelevant
[Citation needed]. Maybe for you. In fact your "approach" might just make this ticket get ignored because it won't be seen in the right basket (product) by that basket's developers. *shrug*
Petr: Also, why did you assign this to Siebrand? Did you talk to him via email/IRC and did he say that he specifically would set this up?
@Andre: because siebrand is the guy who is doing this sync, regarding product, of course I can see your point, but there is no other product that would suit better and we need to track things that need to be done on some, preferably one, place
@Nemo: please stop messing up with this ticket, thank you
by "not mess up" this ticket I meant not doing just what you did... when there is something what needs to be fixed we create a ticket for it, which gets closed when it is actually fixed, not when some excuse why not to fix it is invented.
In this case Niklas himself said this is on their roadmap, so why can't you just close this when it's fixed? I don't care how long it's going it take, but it's not fixed yet, so keep it open.
Per comment 1 this is not WONTFIX (see https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle ) as nobody is against doing this, but simply pretty low priority. However if there's nothing to change in the Huggle code, it's "Translate" territory.
but this has nothing to do with mediawiki extension, it's about translatewiki infrastructure, there are shell scrips used on translatewiki servers, that are being used for this sync and these are the subject of this bug, not the extension. This product is not correct for this request, we don't need any change in translate extension.
This depends on automatic change processing. That code is currently being tested in InTense and it will eventually land in Translate extension.
(I am not working on this right now). My guess is that the blockers might be resolved in Q2 or Q3 of 2015.
It was set to declined because the export isn't automated; it's still human supervised.