Story

As a new developer discovering Open Food Facts I see a lot of project and I would like to understand how they articulate together. Some kind of figure would be awesome.

Who for

This is for everyone contributing to the Google Fellowship, and more specifically to the full time team.

What

All activities and documents to organise ourselves, stay connected, improve our way of working together, and anything else to make the Fellowship team an awesome one.

Why

Effective teams don't just happen - it takes intentional work to develop this effectiveness. This is especially true when the team is big, brand new and distributed.

Problem

We use Github secrets just for variable that are environment specific but not secrets.
That makes it hard to understand where a product is deployed and various parameter that should not be hidden, also it's not versioned.

Proposed solution

Use an initial step to set specific variables using the $GITHUB_ENV file and guarding the step with a if.

What

Right now we have different CONTRIBUTE.md in our repository.

I think we should have a common one in this repository.
Every repository can then send back to this one and add specific stuff.

Contribute should be

• welcoming
• link to project goals
• link to community code of conduct
• explain common things

robotoff is a good example of a contribute.md

Story

As a reader, if I open openfoodfacts.github.io/, I should get a link to every existing project pages and maybe a short introduction to open food facts.

TODO

• create a index.md page
• create a CI action to compile the page and publish it on openfoodfacts.github.io/
• configure for publication