Weblate 1.6 is already two weeks out without any regressions, so now it's time to think about features for 1.7.
I definitely want to improve support for monolingual translation formats as they currently suffer by various metadata issues (eg. checks not working correctly). This requires quite big change in underlying database, but I think it's quite manageable.
When talking about checks, I want to make them configurable per project as global configuration is quite limiting for shared sites like hosted Weblate.
I will definitely need to touch registration and authentication, either by supporting latest django-registration API or to move some other solution with support for federated login. Which of these approaches will be used depends on my time, what is always the most limiting factor.
This might sound as too few features, but I'd like to make releases more often, so that should fit into this plan. However if you want to push for some feature, you still have two days to fund something on Catincan!
