Outreachy 2022: Difference between revisions
(Created project page) |
(fix mess (wikimedia ate part of my previous content…) !) |
||
Line 1: | Line 1: | ||
===Summary=== | ===Summary=== | ||
[https://www.outreachy.org Outreachy] program provides us two intern for 2022, thanks to the [https://www.perlfoundation.org/ Perlfoundation] | |||
The project title : '''"Improve the code quality of the Perl code of the Open Food Facts backend and website".''' | |||
===Description=== | ===Description=== | ||
'''Status''': {{{status}}} | '''Status''': {{{status}}} | ||
Line 13: | Line 16: | ||
====Expected outcomes (what)==== | ====Expected outcomes (what)==== | ||
{{{expected_outcomes_what}}}- adding unit tests to functions that lack them | Improve code quality by: | ||
* {{{expected_outcomes_what}}}- adding unit tests to functions that lack them | |||
- adding integration tests | |||
- investigating the cause of warnings (e.g. unitialized variables) and fixing them | |||
- possibly refactoring some parts of the code to make it more simple and readable | |||
* {{{expected_outcomes_what}}}- adding unit tests to functions that lack them | |||
- adding integration tests | |||
- investigating the cause of warnings (e.g. unitialized variables) and fixing them | |||
- possibly refactoring some parts of the code to make it more simple and readable | |||
* {{{expected_outcomes_what}}}- adding unit tests to functions that lack them | |||
- adding integration tests | |||
- investigating the cause of warnings (e.g. unitialized variables) and fixing them | |||
- possibly refactoring some parts of the code to make it more simple and readable | |||
* {{{expected_outcomes_what}}}- adding unit tests to functions that lack them | |||
- adding integration tests | - adding integration tests | ||
- investigating the cause of warnings (e.g. unitialized variables) and fixing them | - investigating the cause of warnings (e.g. unitialized variables) and fixing them |
Revision as of 12:52, 23 May 2022
Summary
Outreachy program provides us two intern for 2022, thanks to the Perlfoundation
The project title : "Improve the code quality of the Perl code of the Open Food Facts backend and website".
Description
Status: {{{status}}}
People: {{{who}}}
Impact (why)
Improving Perl code quality and documentation is a great way to help the project move forward at a faster pace in the future.
Having less bugs also greatly improves the user and contributors experience.
Having a cleaner code, may also help having more contributions to the perl code base.
Expected outcomes (what)
Improve code quality by:
- {{{expected_outcomes_what}}}- adding unit tests to functions that lack them
- adding integration tests - investigating the cause of warnings (e.g. unitialized variables) and fixing them - possibly refactoring some parts of the code to make it more simple and readable
- {{{expected_outcomes_what}}}- adding unit tests to functions that lack them
- adding integration tests - investigating the cause of warnings (e.g. unitialized variables) and fixing them - possibly refactoring some parts of the code to make it more simple and readable
- {{{expected_outcomes_what}}}- adding unit tests to functions that lack them
- adding integration tests - investigating the cause of warnings (e.g. unitialized variables) and fixing them - possibly refactoring some parts of the code to make it more simple and readable
- {{{expected_outcomes_what}}}- adding unit tests to functions that lack them
- adding integration tests - investigating the cause of warnings (e.g. unitialized variables) and fixing them - possibly refactoring some parts of the code to make it more simple and readable
Timeline
May 23: start of the internship
FIXME
August 31: end of the internship
Resources / Contributing
Outreachy2022Ideas - a list of possible contributions