| | 4 | This year Boost is looking to fund work on a number of different kinds of proposals: |
| | 5 | |
| | 6 | * toolkit-like extensions to existing libraries, |
| | 7 | * finishing or extend sandbox libraries, |
| | 8 | * new data structures and algorithms, and |
| | 9 | * multiple competing proposals for the same project. |
| | 10 | |
| | 11 | For projects involving new or experimental libraries, the process of getting source code "Boost-branded" can take much longer than a single summer. In many cases, it can take much longer than a single year. Even if a library is accepted, there is an expectation that the original author will continue to maintain it. Building a library as part of Boost can easily entail a multi-year commitment. For this reason, we are willing to //consider// multi-year GSoC projects. However, prospective students //must// limit the scope of their work to a single summer. We //may// invite the most successful students to re-apply in 2012. |
| | 12 | |
| | 13 | == Requirements == |
| | 14 | There are only two requirements of students submitting Boost projects: |
| | 15 | |
| | 16 | * Develop a proposal |
| | 17 | * Complete an aptitude test |
| | 18 | |
| | 19 | These requirements also entail interacting with the Boost community on the development mailing list (http://www.boost.org/community/groups.html), checking source code out of the Boost Subversion repository, programming, and compiling a project. |
| | 20 | |
| | 21 | === Developing a Proposal === |
| | 22 | |
| | 23 | === The Aptitude Test === |
| | 24 | |
