Tech Team: Difference between revisions

From Open Food Facts wiki
No edit summary
No edit summary
Line 10: Line 10:
* Our various SDKs (Python, Ruby, Dart, PHP…)
* Our various SDKs (Python, Ruby, Dart, PHP…)
* Build new cool reuses etc...
* Build new cool reuses etc...
=== Topics you can work on ===
*[https://github.com/openfoodfacts/openfoodfacts-androidapp/issues/4169 Android app (Kotlin)]
*[https://github.com/openfoodfacts/openfoodfacts-ios/issues/912 iPhone app (Swift)]
*[https://github.com/openfoodfacts/smooth-app/issues/525 Flutter app (Dart)]
*[https://github.com/openfoodfacts/openfoodfacts-dart/issues/218 Dart package]
*[https://github.com/openfoodfacts/api-documentation/issues/23 API Documentation (Familiarity with APIs, good pedagogy and writing skills)]
*[https://github.com/openfoodfacts/robotoff/issues/374 Robotoff (Python)]
*[https://github.com/openfoodfacts/openfoodfacts-server/issues/5529 Server (HTML,CSS, JS + Perl)]
*[https://github.com/openfoodfacts/openfoodfacts-hungergames/issues/234 Hunger Games (VueJS)]


All our code is on GitHub : [https://github.com/openfoodfacts/ https://github.com/openfoodfacts/]
All our code is on GitHub : [https://github.com/openfoodfacts/ https://github.com/openfoodfacts/]

Revision as of 09:40, 30 August 2021

The Open Food Facts software is developed collaboratively by hackers from all around the world.

We have a lot of development work to do:

  • Open Food Facts backend (Perl and MongoDB);
  • Web site (HTML5, JS, Foundation, within the backend code as templates);
  • iOS native (Swift);
  • Android native (Java);
  • Robotoff, our machine learning service (Python)
  • Hunger Games, our annotation engine (Javascript)
  • Our various SDKs (Python, Ruby, Dart, PHP…)
  • Build new cool reuses etc...

Topics you can work on

All our code is on GitHub : https://github.com/openfoodfacts/

Software development page on the website: https://world.openfoodfacts.org/development

Needs

There is many issues, categorized by topics, see:

Principles

Our goal is to follow and keep few and simple guidelines.

  1. discuss the topics or issues or functionalities you want to work on. The slack workspace is the best choice for it.
  2. if not already done, open an issue on Github to explain the problem you want to solve or the functionality you want to work on.
  3. if you want to work on an existing issue, tell everyone in the issue's Github comments.
  4. fork the project and create one branch per issue or functionality you want to work on.
    1. It's cool to name a branch: issue/[issue_number]-[name]; ex.: issue/1630-name-of-the-issue
    2. When you're ready to propose something, send a "pull request"; be patient, sometimes it takes time to the core team to review pull request.
  5. coding style is defined in the .editorconfig file, see https://github.com/openfoodfacts/openfoodfacts-server/blob/master/.editorconfig; many editors support EditorConfig, check yours: https://editorconfig.org

Inspirations