Changes

Jump to navigation Jump to search
460 bytes added ,  17:36, 12 January 2019
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. Our code is on GitHub.
+
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 ==
   −
* We firstly need resources that work on issues. There is many issues, categorized by topics, see:
+
There is many issues, categorized by topics, see:
** [https://github.com/openfoodfacts/openfoodfacts-server/issues Website and server issues]
+
* [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
** [https://github.com/openfoodfacts/ All the repositories]
+
** 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 ==
   −
* You have to discuss the topics or issues or functionalities you want to work on. Slack is the best choice for it.
+
# 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.
* You should open an issue on Github to explain the problem you want to solve or the functionnality you want to work on.
+
# open an issue on Github to explain the problem you want to solve or the functionality you want to work on.
* You fork the project and create one branche per issue or functionality you want to work on. When you're ready to propose something, you send a "pull request".
+
# 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
+
# coding style is defined in the .editorconfig file, see https://github.com/openfoodfacts/openfoodfacts-server/blob/master/.editorconfig

Navigation menu