Difference between revisions of "Tech Team"
Jump to navigation
Jump to search
(First draft) |
(links to issues) |
||
| Line 3: | Line 3: | ||
== Needs == | == Needs == | ||
| − | * We firstly need resources that work on issues. There is | + | * We firstly need resources that work on issues. There is many issues, categorized by topics, see: |
| + | ** [https://github.com/openfoodfacts/openfoodfacts-server/issues Website and server issues] | ||
| + | ** [https://github.com/openfoodfacts/openfoodfacts-androidapp Android app issues] | ||
| + | ** [https://github.com/openfoodfacts/ All the repositories] | ||
== Principles == | == Principles == | ||
Revision as of 16:13, 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. Our code is on GitHub.
Needs
- We firstly need resources that work on issues. There is many issues, categorized by topics, see:
Principles
- You have to discuss the topics or issues or functionalities you want to work on. Slack 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.
- 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".
Coding style is defined in the .editorconfig file, see https://github.com/openfoodfacts/openfoodfacts-server/blob/master/.editorconfig