Difference between revisions of "GSOC/2025 ideas list"

From Open Food Facts wiki
Jump to navigation Jump to search
(Created page with "Here are ideas for GSOC There are just ideas, and are non limitative. '''IMPORTANT''': * for an introduction on how to candidate, '''read https://world.openfoodfacts.org/g...")
 
Line 6: Line 6:
 
* take also the time to visit [https://world.openfoodfacts.org our website] to understand the project more in depth.
 
* take also the time to visit [https://world.openfoodfacts.org our website] to understand the project more in depth.
  
 +
== Open Food Facts proposals ==
 +
 +
==== Folksonomy Engine: a one size fit all for any product data ====
 +
 +
==== Description ====
 +
At Open Food Facts we are on a mission to collect any factual data about food products, but also cosmetics, and any products.
 +
Modelling every possible products is a challenging task but also topics can be very different based on usage. For example some researchers are interested in knowing the correlation between sugar in cereals and the presence of a cartoon on the front package.
 +
 +
Faithful to our crowded sourced approach to open data collection, we devised Folksonomy Engine, akin to the way Open Street Map works.
 +
 +
The basics are there, but we need to make it more easy and efficient to use in order to reach a large public. We must introduce better properties suggestion, reusable widgets and
 +
====Expected outcomes====
 +
The project, should deliver new API features, like suggestion based on popularity and categories, a better handling of nested properties values, tools for exploring and merging values.
 +
 +
It should also deliver an improved reusable javascript based web interface for display and edition, with maybe some formalization of properties definition.
 +
 +
The roadmap can be changed while iterating over features, to better achieve the goal of usability by a large variety of contributors.
 +
 +
====Project information====
 +
*repository: https://github.com/openfoodfacts/folksonomy_api (and https://github.com/openfoodfacts/folksonomy_frontend)
 +
*Slack channels: #folksonomy_engine
 +
*Potential mentors: Alex G. (slack: ''Alex G.'', alex -at- openfoodfacts.org, github: [https://github.com/alexgarel/ alexgarel])
 +
*Project duration: 175 hours or 350 hours
 +
*Skills required: Python, Javascript
 +
*Difficulty rating: Medium
 
== Your idea ==
 
== Your idea ==
 
You are a candidate and have a specific project idea, that's really welcome.
 
You are a candidate and have a specific project idea, that's really welcome.
Line 26: Line 51:
 
*Slack channels:  
 
*Slack channels:  
 
*Potential mentors:  
 
*Potential mentors:  
*Project duration:  
+
*Project duration: ( ~90 hour, ~175 hours or ~350 hours)
 
*Skills required:  
 
*Skills required:  
 
*Difficulty rating:
 
*Difficulty rating:

Revision as of 08:56, 10 February 2025

Here are ideas for GSOC There are just ideas, and are non limitative.

IMPORTANT:

Open Food Facts proposals

Folksonomy Engine: a one size fit all for any product data

Description

At Open Food Facts we are on a mission to collect any factual data about food products, but also cosmetics, and any products. Modelling every possible products is a challenging task but also topics can be very different based on usage. For example some researchers are interested in knowing the correlation between sugar in cereals and the presence of a cartoon on the front package.

Faithful to our crowded sourced approach to open data collection, we devised Folksonomy Engine, akin to the way Open Street Map works.

The basics are there, but we need to make it more easy and efficient to use in order to reach a large public. We must introduce better properties suggestion, reusable widgets and

Expected outcomes

The project, should deliver new API features, like suggestion based on popularity and categories, a better handling of nested properties values, tools for exploring and merging values.

It should also deliver an improved reusable javascript based web interface for display and edition, with maybe some formalization of properties definition.

The roadmap can be changed while iterating over features, to better achieve the goal of usability by a large variety of contributors.

Project information

Your idea

You are a candidate and have a specific project idea, that's really welcome.

But to maximize your chances, please:

  • Contribute to the project none the less in the bounding period
  • Check with us that your idea is a good fit and align with our priorities

Project template

<DESCRIPTIVE TITLE>

Description

Explain what, why.

Expected outcomes

Deliverables and KPI / benefits

Project information

  • repository:
  • Slack channels:
  • Potential mentors:
  • Project duration: ( ~90 hour, ~175 hours or ~350 hours)
  • Skills required:
  • Difficulty rating: