Difference between revisions of "Tech Team"
Jump to navigation
Jump to search
(links to issues) |
(refactor) |
||
| Line 1: | Line 1: | ||
| − | We have a lot of development work to do: on the Open Food Facts backend (Perl and MongoDB), API (JSON), web site (HTML5, JS, Foundation), iOS / Android / Windows Phone / FirefoxOS apps (currently developed in HTML and JS with Apache Cordova / Phonegap), to build new cool reuses etc. | + | We have a lot of development work to do: on the Open Food Facts backend (Perl and MongoDB), API (JSON), web site (HTML5, JS, Foundation), iOS / Android / Windows Phone / FirefoxOS apps (currently developed in HTML and JS with Apache Cordova / Phonegap), to build new cool reuses etc. |
| + | |||
| + | All our code is on GitHub : [https://github.com/openfoodfacts/ https://github.com/openfoodfacts/] | ||
== Needs == | == Needs == | ||
| − | + | There is many issues, categorized by topics, see: | |
| − | + | * [https://github.com/openfoodfacts/openfoodfacts-server/issues Website, backend and API issues] | |
| − | ** [https://github.com/openfoodfacts/openfoodfacts-androidapp Android app issues] | + | ** For beginners see [https://github.com/openfoodfacts/openfoodfacts-server/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22 First Good Issue] category |
| − | + | ** For those who love i18n see [https://github.com/openfoodfacts/openfoodfacts-server/issues?q=is%3Aopen+is%3Aissue+label%3Atranslations translations] category | |
| + | ** See [https://github.com/openfoodfacts/openfoodfacts-server/labels all the categories] | ||
| + | * [https://github.com/openfoodfacts/openfoodfacts-androidapp Android app issues] | ||
| + | * [https://github.com/openfoodfacts/ All the repositories] | ||
== Principles == | == Principles == | ||
| − | + | # discuss the topics or issues or functionalities you want to work on. The [http://slack.openfoodfacts.org/ slack workspace] is the best choice for it. | |
| − | + | # open an issue on Github to explain the problem you want to solve or the functionality you want to work on. | |
| − | + | # fork the project and create one branch per issue or functionality you want to work on. When you're ready to propose something, send a "pull request". | |
| − | + | # coding style is defined in the .editorconfig file, see https://github.com/openfoodfacts/openfoodfacts-server/blob/master/.editorconfig | |
Revision as of 17:36, 12 January 2019
We have a lot of development work to do: on the Open Food Facts backend (Perl and MongoDB), API (JSON), web site (HTML5, JS, Foundation), iOS / Android / Windows Phone / FirefoxOS apps (currently developed in HTML and JS with Apache Cordova / Phonegap), to build new cool reuses etc.
All our code is on GitHub : https://github.com/openfoodfacts/
Needs
There is many issues, categorized by topics, see:
- Website, backend and API issues
- For beginners see First Good Issue category
- For those who love i18n see translations category
- See all the categories
- Android app issues
- All the repositories
Principles
- discuss the topics or issues or functionalities you want to work on. The slack workspace is the best choice for it.
- open an issue on Github to explain the problem you want to solve or the functionality you want to work on.
- fork the project and create one branch per issue or functionality you want to work on. When you're ready to propose something, send a "pull request".
- coding style is defined in the .editorconfig file, see https://github.com/openfoodfacts/openfoodfacts-server/blob/master/.editorconfig