| | 291 | === Boost+Travis CI integration and Android cross-compilation === |
| | 292 | |
| | 293 | This is project for improvements of Boost's infrastructure. This project can be beaked down to the following parts: |
| | 294 | * Adding automated [http://docs.travis-ci.com/ Travis CI] testing scripts to all the Boost libraries (Knowledge of Ruby language would be an advantage). |
| | 295 | * Finishing the work with running the Boost's [https://github.com/apolukhin/regression_android regression tests] on Android. |
| | 296 | * Write scripts for regression testing and cross-compilation on remote devices and emulators (RaspberyPI/Qemu). |
| | 297 | * Writing a documentation about cross-compiling and running regression test of Boost libraries for different targets. |
| | 298 | |
| | 299 | This project requires basic knowledge of scripting languages and a lot of patience. |
| | 300 | Project could be interesting not only for programmers, but also for system administrators that have the courage to dig into the world of cross-compilations, auto-testings, and build scripts. |
| | 301 | |
| | 302 | This project could be mentored by Antony Polukhin and Niall Douglas |
| | 303 | |
| | 304 | === Boost.Document === |
| | 305 | |
| | 306 | Library for integration with spreadsheet applications Excel/LibreOfficeCalc/OpenOfficeCalc and other [http://en.wikipedia.org/wiki/Office_suite office programs]. |
| | 307 | Idea is to unify APIs of different Office suits and provide a clear header only library that is capable of doing simple tasks with office documents (creation, pdf exporting, file format changes, data extraction and cells manipulations). Such library is essential for banking software, CRMs and many other programs. |
| | 308 | |
| | 309 | This project requires a good C++ knowledge, generic programming. Experience with Office's API would be an advantage. |
| | 310 | |
| | 311 | This project could be mentored by Antony Polukhin |
| | 312 | |
| | 313 | === Boost.Binaries === |
| | 314 | |
| | 315 | Library that provides instruments for a binary to self control. This can be useful for protection against viruses and other attacks; protect programs against reverse engineering; can help post-process binaries (find how a compiled function looks like, put something into the binary after compilation, compute and store checksums of binary). |
| | 316 | |
| | 317 | Basic functionality would be: |
| | 318 | * marking part of code at compilation |
| | 319 | * reserving space for after-compilation data |
| | 320 | * checksumming/encrypting/decrypting marked code at runtime |
| | 321 | |
| | 322 | This project requires a good C++ knowledge. Knowledge of assembly languages would be an advantage. |
| | 323 | |
| | 324 | This project could be mentored by Antony Polukhin |
| | 325 | |
