About a month ago, I've spent some time in Nuremberg and took few night pictures there.
As usual, downloading them from my camera took quite long, but nevertheless now there are online:
About month ago, I wrote that there were over 20000 translations done using Weblate in three months. It looks like I was too pessimistic with future as in slightly more than month l10n.cihar.com has reached 30000 translations.
This is quite great achievement and shows big user base. Especially together with rising number of third-party installations of Weblate (still some of the big ones do not want to be mentioned).
On the other side, there have already been around 100 issues open, out of which most were fixed (1.2 release already includes 30 fixed issues). Still I'm sure there is lot of place for improvements :-).
Anyway if you are looking for more numbers, you can find them on Ohloh :-).
More and more people seem to be interested in Weblate and it is becoming less and less comfortable to handle all this communication privately in my mailbox.
That's why I've decided to open up mailing list for Weblate. It is now available at firstname.lastname@example.org, you can subscribe at https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate (request to add this list to Gmane is pending).
I hope this will attract more interested people and open up wider discussion about some features.
PS: Now there is also #weblate on freenode if you are interested in chatting about Weblate.
Today I continued to analyzing performance and did few optimizations of some frequently used code paths. There is still lot of area for improvement, but I think Weblate is now fast enough for daily usage on even quite big projects.
Rest of the day was spend by looking at various questions which people have asked me and distilling that into documentation. The most extended part were frequently asked questions, which now includes some hints for setup.
First task was to add support for django-registration 0.8. Originally my plan was to support both 0.7 and 0.8, but that proven to be too complicated so Weblate now requires 0.8, which brings quite a lot of differences in API.
Later I've installed django-debug-toolbar and looked at some bottlenecks in some hot paths. This resulted in few optimizations of translations merging and new caching for translation stats. This turned out to be too expensive for bigger translations and caching these can save few seconds on page load.
I will probably focus more on performance tuning tomorrow as I don't plan to add any new features to 1.2 release.
As you can see on github, there are currently no open issues for Weblate's 1.2 milestone. Looks like I've done most of my Hackweek VIII project faster than expected, but I might add some more improvements.
Everything went quite smoothly, but anyway I've decided to postpone some issues. The major reason is that I'm not really sure whether these are good ideas and won't implement something until I'll get more feedback. You can find such issues labeled "needs decision". Comments there are especially welcome :-).
On the code side, I've improved support for po file headers, did various improvements on maintenance scripts and improved about page.
Also current code from git is now deployed at demo.weblate.org, so feel free to test it. I'm especially curious how the simple and stupid spam protection will work in reality.
Now it's time for ice cream and then I'll think what to implement next :-).
Then I've focused on handling languages as there were some things which I did not like. Most importantly, Weblate will now try to use existing languages even if used code does not 100% match (eg. cs_CZ and cs-CZ are treated equal). Also with help of locale aliases, some specific variants won't be created and generic one used instead (eg. cs_CZ will use cs, as these are actually same). If there will be need to differentiate them, you still can create language manually and Weblate will use matched one.
Last thing is translation locking - translator can now lock translation for exclusive use and nobody else will be able to work on that. This will help in situations where more people started to work on same translation and basically duplicated the effort.
There are 3 open issues targeted for 1.2 release, but I'm not sure if some of these are good ideas, let's keep the decision for next days.
The first day of Hackweek VIII is about to end for me and it's time to share some of the results.
As planned, I've started hacking on Weblate. The most prominent feature from today are email notifications. You can now monitor the translation in various ways - be informed about new strings to translate, new contributor, added suggestion or simply watch all translations.
Another bigger change is rearranging of main page, which now provides instant access to per language stats, which were quite hidden before.
Rest of time was spent on adding some sort of spam protection (need to deploy this to demo to see how successful it is) and one more promoting widget (88x31 pixels).
There are 6 open issues targeted for 1.2 release, so there is still something to do in next days :-).
Time to time we've received offers for sponsoring, but we never got to point where we could easily handle these. In the past we were limited by sf.net requirements for no advertisement on website, but it got leveraged over the time and we did not change our policy much.
For now the only benefit we are providing to our sponsors (besides good feeling that they are supporting good project) is logo and link on our website. In the future we might add some more, but at first we want to see how it works in this scale.
For some time I thought it is not effective to use polling to get latest changes from GitHub into Jenkins, which we use for continuous integration, but II was always too lazy to investigate.
Today I finally took a look at it and it turns out to be quite easy:
Try testing the hook and check "GitHub Hook Log" in Jenkins if it really works and you're done.