@@ -16,17 +16,4 @@ There are different ways you can contribute to MBDyn. For example:
If you feel to go with the second option, please read carefully and follow our [Developers Guidelines](Development/how-to-contribute)
### Google Summer of Code
We have been selected as participating Orgs in the [2015](https://www.mbdyn.org/?News&id=19), [2016](https://www.mbdyn.org/?News&id=28) and [2017](https://www.mbdyn.org/?News&id=31)[Google Summer of Code (GSoC)](https://summerofcode.withgoogle.com). Below, you can find more information if you're interested in participating to the GSoC with us.
#### For Students
If you are interested in participating as a student, please get in touch with us as soon as possible, either here on GitLab or on the [MBDyn users mailing list](http://lists.mbdyn.org/mailman/listinfo/mbdyn-users). We will help you familiarize with the code, in order to prepare a good GSoC application.
We select students weighting in on their ability to produce good code, naturally, but also on their interactions with the MBDyn community. To assess both, we decided to introduce an **entry test**, subdivided in steps of growing complexity. If you want your application to be taken seriously, you should be able to demonstrate to have at least completed the first step.
If you are an experienced MBDyn user/developer, and want to become a mentor, please let us know contacting us here on GitLab or on [MBDyn users mailing list](http://lists.mbdyn.org/mailman/listinfo/mbdyn-users).
We have been selected as participating Orgs in the [2015](https://www.mbdyn.org/?News&id=19), [2016](https://www.mbdyn.org/?News&id=28) and [2017](https://www.mbdyn.org/?News&id=31)[Google Summer of Code (GSoC)](https://summerofcode.withgoogle.com). You can find more information in the [dedicated Wiki page](Google-Summer-of-Code/Google-Summer-of-Code) if you're interested in participating to the GSoC with us.
