... | ... | @@ -22,7 +22,7 @@ _Should require roughly 2 hours_ |
|
|
- implement a modification to the MBDyn code used by the test case you ran;
|
|
|
- re-run your test case with the modified code;
|
|
|
- describe the effect of your modification on the test case's results;
|
|
|
- issue a merge request as described in the [Developers Guidelines](https://gitlab.polimi.it/Pub/mbdyn/blob/master/CONTRIBUTING.md).
|
|
|
- issue a merge request as described in the [Developers Guidelines](https://public.gitlab.polimi.it/DAER/mbdyn/wikis/Development/Developers-Guidelines).
|
|
|
|
|
|
_Should require roughly 4 hours_
|
|
|
|
... | ... | @@ -37,7 +37,7 @@ _Should require roughly 4 hours_ |
|
|
|
|
|
Some additional tips:
|
|
|
- name the module `module-gsoc-yourname.cc`;
|
|
|
- document the purpose and the implementation of the module, either in the [mailing list](https://gitlab.polimi.it/Pub/mbdyn/wikis/gsoc/faqs) or opening an [issue](https://gitlab.polimi.it/Pub/mbdyn/issues);
|
|
|
- document the purpose and the implementation of the module, either in the [mailing list](https://public.gitlab.polimi.it/DAER/mbdyn/wikis/Google-Summer-of-Code/Frequently-Asked-Questions) or opening an [issue](https://gitlab.polimi.it/Pub/mbdyn/issues);
|
|
|
- look at distributed modules (in the "modules/" folder) as useful working examples;
|
|
|
- non-creative copy’n’paste is ** strongly discouraged**;
|
|
|
- look at the mailing list archive to see past years' module related questions;
|
... | ... | |