# Introduction
The [radare]( http://rada.re/ ) project started in February of 2006 aiming to provide a free and simple command line interface for an hexadecimal editor supporting 64 bit offsets to make searches and recovering data from hard-disks.
Since then, the project has grown with the aim changed to provide a complete framework for analyzing binaries with some basic \*NIX concepts in mind like everything is a file, small programs that interact together using stdin/out, and keep it simple.
[Radare2](https://github.com/radare/radare2) is a complete [LGPL]( https://opensource.org/licenses/lgpl-license ) rewrite of the original project, to remove design issues of the first iteration, and to make it more modular and easier to script and maintain. It features a testsuite that aims to cover as much cases as possible in order to catch regressions.
Radare2 is composed of an hexadecimal editor as central point, with several assemblers/disassemblers, code analysis capabilities, scripting features, visualization of code and data through graphs and other means, a visual mode, easy unix integration, a diff engine, a shellcode compiler, and much more.
# Previous Years
In Summer of 2014 and 2015, we hosted our own version of Radare Summer of Code (RSoC). These were some of the successful projects:
- FLIRT and YARA signatures support for radare2
- Loading PDB debug information
- Structures support (like in 010 Editor)
- ObjC metadata parsing from Mach-0 to expose classes and symbols
More information can be found in this [RSoC blog post](http://radare.today/posts/the-rsoc-is-over/).
We were also accepted for Google Summer of Code (GSoC) 2015 under the umbrella of [Openwall](http://www.openwall.com/) project and this year (2016) too. Previos Our students finished developing a major part of decompiler (radeco) with radare2 integration (except pseudo-C code emitter). More information is available in the project [repository](https://github.com/radare/radeco) and GSoC’15 pages: [project1](https://www.google-melange.com/gsoc/project/details/google/gsoc2015/dkreuter/5668600916475904), [project2](https://www.google-melange.com/gsoc/project/details/google/gsoc2015/sushant94/5733935958982656). This year GSoC students working on finishing radeco, improving variables and function arguments' analysis, improving WebUI.
If you have questions or comments, visit our IRC channel #radare on Freenode.
# Schedule
- May 25 - Begin applications
- June 13 - End of application acceptance
- June 15 - Announce the selected students
- June 17 - Start coding!
- July 30 - Midterm evaluation
- Sept 16 - "Pencils down" - final term evaluation
- Sept 27 - Hard deadline, all changes should be in master branch and covered by tests
# Donations
You can donate to the crowdfunding program using paypal or bitcoin.
We will use this money to pay contributors for completed tasks. The collected
amounts will be public. Any unused money
will go towards future "Summer of Codes" or other costs to the project.
Contributors will receive their money in their preferred currency. The organizers
will work to convert the donations to your preferred local or digital currency.
We are hoping to raise $20000 , with a goal of providing 4 selected participants with $5000 each.
# Current amounts
Euros: 0 / 20000 USD
Bitcoin: 0 / 0 BTC
# Mentors
Members of radare2 core team have volunteered to guide students for RSoC’16. They were already guiding the students for GSoC’15 (under Openwall umbrella), RSoC’15 and RSoC’14 and continuing to guide during the GSoC'16 as well. Please feel free to reach out to any of them in case you need any help in selecting a project.
- Sergi Alvarez IRC: pancake -- [@trufae](https://twitter.com/trufae)
- Jeffrey Crowell IRC: crowell -- [@jeffreycrowell](https://twitter.com/jeffreycrowell)
- Anton Kochkov IRC: xvilka -- [@akochkov](https://twitter.com/akochkov)
- Julien Voisin IRC: jvoisin -- [dustri.org](http://dustri.org)
- Alvaro Felipe Melchor: alvaro\_fe - [@alvaro\_fe](https://twitter.com/alvaro_fe)
- Maxime Morin IRC: maijin - [@Maijin212](https://twitter.com/Maijin212)
# Development methodology
Currently, all repositories are hosted on [github](https://github.com/radare/) and bugs are tracked on github [issues](https://github.com/radare/radare2/issues). We are mostly using [etherpad](https://pad.nopcode.org/p/r2), IRC and Telegram for communication.
We have a [testsuite](https://github.com/radare/radare2-regressions) (that is running on [Travis CI](https://travis-ci.org/radare/radare2/), [AppVeyor](https://ci.appveyor.com/project/radare/radare2) and our [Jenkins](http://ci.rada.re/) instance) to test and verify that all the features are still working and that a merge or a commit don't break anything, and to find regressions.
We encourage contributors to write test cases and documentation in order to verify the implementation and ensure that everything fits well together. There is also a [Coverity](https://scan.coverity.com/projects/416) instance to catch obvious defects. For the complex bugs and examples we're using our own [asciinema installation](http://radare.tv/)
# License
Radare2 is modular: this means that it aims to make all the elements and features easily reusable from other projects. The choice of [LGPL3](https://www.gnu.org/licenses/lgpl.html) as a license is the minimum requirement to get code merged in r2. Contributors can choose Apache, BSD, MIT, Public Domain, or other similar licenses. The reason to exclude GPL as a valid license for the project is because we aim to support proprietary software that uses r2, while protecting our free codebase.
# Instructions for students
It is almost a requirement that students who want to apply to the radare2 project for the Google Summer of Code 2016 should submit a small pull request accomplishing one of the [microtasks](http://radare.org/rsoc/2016/tasks.html) as part of their application. Though you can also choose any of the Github issues for radare2 if they are big enough to be a qualification task, still small enough to be finished no more than in a couple of weeks.
## Programming languages
Most of radare2 is written in C and hence we expect students to be familiar with C programming language. For the radeco-related tasks, student should know rust or be willing to learn the same.
## Recommended steps
1. Grab any of the project from [list of ideas](http://radare.org/gsoc/2016/ideas.html) that you're interested in (or propose your own).
2. Write a first draft proposal using Google Docs and [our template](https://docs.google.com/document/d/1kDPGgr_D5tQuYLQi_gEGlkuQ-DlU8GH5kDBqZbVSC7I/edit?usp=sharing) and ask one of the mentors or administrators to review it with you.
3. Fix a few bugs and send Pull Requests and link them in your proposal.
3. Submit it to [rsoc@radare.org](mailto:rsoc@radare.org).
## Student proposal guidelines
1. Keep it simple enough to fit not more than a couple of pages. Despite the shortness of the sentences, try to save the clarity of the proposal.
2. Try to split RSoC period into tasks, and the task into subtasks. It really helps us to understand how you want to accomplish your goals, but even more it'll help you - to understand the task deep enough before starting it, and prioritize important things to do first.
3. Please, note, how much time a day/week you are going to spend on this project.
4. Specify your timezone, since so we can assign you a mentor in the same one, to ease communication.
5. Submit your proposal early, not in the last minute
6. You can also choose a “backup” idea (the second task you probably want to do), so that in case of some conflicts (two students for one task) it will be easier to solve.