Projects homepage

Do you want to involve yourself in a project? Want to know which are our concrete projects? You're at the right place.

Projects Proposals

⚠ FOLLOWING PROJECTS SHOULD HAVE THEIR OWN PAGE (to migrate)

Owned by User:Teolemon; with the participation of User:Stephane, @VaiTon, @Aleene, ...
Provide a score to decrypt environmental impacts of products.
Status: 2021-01: launched a first version on OFF website and apps (for more than 240,000 products)
Needs: ...
How to join: see #eco-score channel on slack.

Owned by User:Stephane; with the participation of ...
This project will allow users of the Open Food Facts website, mobile app and our 100+ mobile apps ecosystem, to get highly personalized search results without sacrificing their privacy.
Status: 2021-01: 8 months ongoing project, near finished.
Needs: ...
How to join: see its dedicated wiki page and #personal-search slack channel

Owned by User:Charlesnepote; with the participation of @jolesh, @aleene
Every week, Open Food Facts is receiving many questions from the general public. The goal of the project is to let contributors join the effort to answer different kind of questions, and different languages.
Status: 2021-01: the platform is installed and running, but needs more work to have a fluent process.
How to join: ask User:Charlesnepote.

Owned by User:Charlesnepote; with the participation of @cquest.
The goal of Folksonomy engine is to unleash an ocean of new usages regarding food knowledge. Folksonomy engine allows all kind of people — citizens, researchers, journalists, professionals, artists, communities, innovators... — to enrich and use Open Food Facts, thanks to free tags and properties of their own, for their own use or to enrich the shared knowledge. Open Food Facts, as the biggest open-food database in the world, already feeds hundreds of data reuses. It will allow thousands of new apps and new usages.
Status: 2022-03: in production for moderators; needs to be published as beta for registered users.
How to join: ...

Owned by User:Alexfauquette; with the participation of User:Teolemon.
The goal of Hunger Games is to bring gaminfication to the data annotation. Allows people that have 5-10min to products instead of playing candy crush.
Status: live at https://hunger.openfoodfacts.org/
How to join: slack channel hungergame

We want to change our blog platform to allow more features (such as responsive design), and open contributions to more people.
Needs: install the new platform; migrate old blogposts to the new platform; design the website; add features depending on users' needs.
Status: done
How to join: ask User:Charlesnepote.

Slack is cool, but it's only a chat. It does not allow structured discussions. Many users ask for a more convenient way to discuss the project.
Needs: gather our needs; choose a tool (Discourse, Odoo...); install it; design the website.
Status: done
How to join: ask User:Charlesnepote.

Started by a team from Wild Code School, initially mentored by @stephane and @teolemon
Goal: Set up a contributor tracking tool
Documents

 * Presentation Demo Day
 * Client & server requests
 * Contributor Analysis Installation Guide
 * Improvements

No owner yet.
1. Communicate what we are doing for science (data reuses for studies), and with scientists. 2. Explain how we can collaborate and suggest to scientists to contact us.
Needs: list main scientific articles based on our data; explain how we can collaborate; write a dedicated page on OFF website; maybe: write blog posts.
Status: 2021-01: 2 months projects.
How to join: ask User:Charlesnepote.

No owner yet.
Open Food Facts API usage is free and will remain free for all users. Though, it is made for reasonable usages: 1 API call = 1 real scan by a user. Our resources are not sized for dozens of requests at a time. For example, while building dashboards with Google Spreadsheet is feasible via Open Food Facts API, we tend to block this kind of request as it consumes too many resources. The goal of OFF API Proxy is to allow dozens of requests at a time, the proxy queuing requests passing them to the API at a reasonable rate (2 requests/s). The proxy is also using caches, allowing a more sustainable usage of the API.
Needs: If you do have Nginx skills, your contribution would be appreciated.
Status: 2021-01: 1-month project.
How to join: ask User:Charlesnepote.