Source codes of RosVyborov are open

In August, there was a post on Habré in which we urgently searched for Rails-developers, and the situation looked almost critical. Nevertheless, although it was not easy, we managed - the coordination system of observers successfully worked during the pre-election stage and directly during the elections, having fulfilled the tasks assigned to it.
Of course, there were overlays, the biggest one - almost an hour downtime of the call center call recording interface on election day, provoked by a large DDoS attack on the FBK “neighboring” projects (our mistake could have been better prepared), but on the whole it did not affect the results.

After the elections, for obvious reasons, the development actually stopped, and the project was slowly prepared for the opening of the code. In my free time I will work on it, but one will not go far, and therefore, of course, we need the hands and heads of those who are willing to donate a little time for the development of the system. The fact that she will be needed, no doubt, is the first big election, where such a scale of coordination of observers is needed - the elections to the Moscow City Duma, which are just around the corner.
')
So, the project repository - github.com/fbkinfo/rosvybory .

If you are not ready to take and begin to write code, but there are some constructive suggestions or criticism, then, of course, do not hesitate, either here or immediately to issues on the github. A whole bunch of great engineers worked on the project, but with different experiences and in very hellish conditions, so the project can be refined a lot, and the specifics would help a lot and I, as maintainer, and probably other developers who will help.

You can try the current version in action on the demo version, see github.com/fbkinfo/rosvybory/wiki/Democ server .
The main task now is the revision in accordance with the existing formulation .
More specific tasks and fixed bugs - github.com/fbkinfo/rosvybory/issues (I still have to figure out how to properly arrange them, we used another tracker during development).
Taking into account that the project will be needed further, it is also necessary to cover with tests - now there are quite a few of them - and refactoring to the best of our ability and desire — many things were written for speed.

At the moment, it seems that there are not very many very important tasks, but I’m sure that the guys from RosVyborov themselves and other observational organizations will also throw feedback and ideas that, as they become available, will be published in the issues.

I have no experience with the content of the public repository, so the advice and criticism on the organization of this process is also welcome.

Join now! As they say, RosVybory will not write themselves. :)

PS
Come to the meeting of IT professionals tomorrow everyone who wants to help the Fund for the fight against corruption. Let's get acquainted, talk about projects and plans for the future. October 9, Wednesday at 19:30, Taganskaya Street, Building 29. www.facebook.com/events/443888772399542