Line 9: |
Line 9: |
| Providing tools is essential to be able to [[Data Contribution Team|grow the database]] as fast as possible and maintain its quality. | | Providing tools is essential to be able to [[Data Contribution Team|grow the database]] as fast as possible and maintain its quality. |
| | | |
− | The mobile app and the main website reaches a large public providing them health and environment information. It also enables crowd sourcing the database at a large scale, there UX is important. | + | The mobile app and the main website reach a large public and provide health and environment information. They also enable crowdsourcing the database at a large scale. Their user experience is very important. |
| | | |
− | The other tools helps tracking data quality, fixing errors, augment contribution through machine learning etc. | + | The other tools help tracking data quality, fixing errors, augmenting contribution through machine learning etc. |
| | | |
| Having qualitative technical documentation helps a lot reaching new contributors that can help us more efficiently. | | Having qualitative technical documentation helps a lot reaching new contributors that can help us more efficiently. |
Line 20: |
Line 20: |
| [https://slack.openfoodfacts.org/ Slack channels]: | | [https://slack.openfoodfacts.org/ Slack channels]: |
| *<nowiki>#dev - is a general channel around development</nowiki> | | *<nowiki>#dev - is a general channel around development</nowiki> |
− | *#infrastructure - is about managing servers, installing software, etc. | + | *#<nowiki>#infrastructure - is about managing servers, installing software, etc.</nowiki> |
− | *#documentation - about documentation | + | *#<nowiki>#documentation - about documentation</nowiki> |
− | *Then software projects have their own channels, for example #product-opener (main server), #mobile_app you may find specific channels in the README of each project | + | *All our software projects have their own channels, for example #product-opener (main server), #mobile_app. You may find specific channels in the README of each project. |
| *There are also channels specific to languages: #perl, #flutter, #python, etc. to ask questions specific to the language or develop the SDK | | *There are also channels specific to languages: #perl, #flutter, #python, etc. to ask questions specific to the language or develop the SDK |
− | All developments happens on '''GitHub''': https://github.com/openfoodfacts/ (even infrastructure has it's repo) | + | All developments happens on '''GitHub''': https://github.com/openfoodfacts/ (even infrastructure has its repo) |
| | | |
− | Some projects have weekly or bimonthly meeting, see README of each projects or [[Events|community calendar.]] | + | Some projects have weekly or bimonthly meeting, see the README of each projects or [[Events|community calendar.]] |
| | | |
− | We have a monthly infrastructure meeting (see [[Events|community calendar)]] | + | We have a monthly infrastructure meeting (see [[Events|community calendar).]] |
| | | |
| === Activities === | | === Activities === |
Line 34: |
Line 34: |
| * Software development | | * Software development |
| ** there is a large variety of projects to develop. see https://github.com/openfoodfacts/ | | ** there is a large variety of projects to develop. see https://github.com/openfoodfacts/ |
− | ** if you want to help with the core of the project, consider learning perl (server) or flutter (mobile app) | + | ** if you want to help with the core of the project, consider learning Perl (server) or Flutter (mobile app) |
| ** new ideas are also welcome | | ** new ideas are also welcome |
| ** after one or two successful merge PR you can ask direct access to a repository | | ** after one or two successful merge PR you can ask direct access to a repository |
Line 48: |
Line 48: |
| * Infrastructure | | * Infrastructure |
| ** if you have a good level of expertise in Linux, ZFS, Proxmox or some specific architecture, we would really welcome your participation. see [https://github.com/openfoodfacts/openfoodfacts-infrastructure/ openfoodfacts-infrastructure repository] | | ** if you have a good level of expertise in Linux, ZFS, Proxmox or some specific architecture, we would really welcome your participation. see [https://github.com/openfoodfacts/openfoodfacts-infrastructure/ openfoodfacts-infrastructure repository] |
− | ** [https://github.com/openfoodfacts/openfoodfacts-monitoring/ monitoring] is also a thing | + | ** [https://github.com/openfoodfacts/openfoodfacts-monitoring/ monitoring] is also important |
| ** contributing in docker in projects, and CI/CD actions is also much appreciated | | ** contributing in docker in projects, and CI/CD actions is also much appreciated |
| * Machine learning | | * Machine learning |
Line 56: |
Line 56: |
| | | |
| === Programs === | | === Programs === |
− | Some year we participated in programs like Google Summer Of Code, Google Season of docs, [https://outreachy.org/ outreachy], [https://dataforgood.fr/ data for good],
| + | We regularly participate in programs like Google Summer Of Code, Google Season of docs, [https://outreachy.org/ outreachy], [https://dataforgood.fr/ data for good], |
| | | |
− | If you are interested in mentoring or participating, or if you propose another program, reach us. | + | If you are interested in mentoring or participating, or if you would like to propose another program, reach out to us. |
| | | |
| == Principles == | | == Principles == |