On 3 March 2013 17:47, Andrea Pescetti <[email protected]> wrote: > On 01/03/2013 janI wrote: > >> We need to wait for the release of pootle, last I checked it was still not >> official. Once 2.5 is released I will update translate-vm. >> Please consider the translate-vm, is currently NOT configured for a higher >> online volume (about 3 users and mysql is strugling). Infra has agreed >> that >> I do performance tuning after installing the new release. >> It should be possible to configure 2.5 to use both ldap and local db. >> > > OK, thanks for the detailed explanations. So the steps would be: > > 1) Check on the Pootle 2.5 release date and features. Indeed I can't find > information easily at > http://translate.sourceforge.**net/<http://translate.sourceforge.net/>so we > will have to bother the developers. If you need any help in > contacting them, just ask. > I would like to see it running on other sites the translate itself, but I am just a negative (have been too long in support). My rule of thumb is release date + 1 month, in order not to fight fight with start problems.
> 2) Check that policy-wise it's fine to authenticate committers on LDAP and > all other volunteers on a local backend. I believe it's fine (and actually > very helpful for our use case), but I'm prepared to raise the issue > properly at due time. > You might need to, infra (gmcdonald) was not positive, but I still think we have a case and should go for it...I do however think a compromise could be a signed ICLA. > > 3) Optimize performance so that Pootle is actually usable by several users. > That is something on my list of todos, and infra ask me regulary when I do it. > > Am I missing any other steps? > Not really, apart from a bottle of good italian wine when if finally works, together with genLang. > > Regards, > Andrea. >
