Difference between revisions of "Software Development"

From Open Food Facts EN
Jump to navigation Jump to search
(refactor)
(+ existing issues)
Line 15: Line 15:
 
== 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.
+
# '''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.
+
# if not already done, '''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".
+
# if you want to work on an existing issue, '''tell everyone in the issue's Github comments'''.
# coding style is defined in the .editorconfig file, see https://github.com/openfoodfacts/openfoodfacts-server/blob/master/.editorconfig
+
# 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"; be patient, sometimes it takes time to the core team to review pull request.
 +
# '''coding style''' is defined in the .editorconfig file, see [https://github.com/openfoodfacts/openfoodfacts-server/blob/master/.editorconfig https://github.com/openfoodfacts/openfoodfacts-server/blob/master/.editorconfig]; many editors support EditorConfig, check yours: https://editorconfig.org

Revision as of 09:22, 13 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:

Principles

  1. discuss the topics or issues or functionalities you want to work on. The slack workspace is the best choice for it.
  2. if not already done, open an issue on Github to explain the problem you want to solve or the functionality you want to work on.
  3. if you want to work on an existing issue, tell everyone in the issue's Github comments.
  4. 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"; be patient, sometimes it takes time to the core team to review pull request.
  5. coding style is defined in the .editorconfig file, see https://github.com/openfoodfacts/openfoodfacts-server/blob/master/.editorconfig; many editors support EditorConfig, check yours: https://editorconfig.org