Google Summer of Code Ideas 2013

Introduction

This page is the Idea List suggested by the Dolibarr core team or Dolibarr users for the Google Summer Of Code (please, read this introduction to complete).

Information for Students

If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at. Being accepted as a Google Summer of Code student is quite competitive. Accepted students typically have thoroughly researched the technologies of their proposed project and have been in frequent contact with potential mentors. Simply copying and pasting an idea here will not work. On the other hand, creating a completely new idea without first consulting potential mentors is unlikely to work out. When writing your proposal or asking for help from the general Dolibarr community don't assume people are familiar with the ideas here. If there is no specific contact given you can ask questions on the Doliberr development mailing list dolibarr-dev@nongnu.org. See page https://savannah.nongnu.org/mail/?group=dolibarr for information on available mailing lists and how to subscribe. Also, for information of possible mentors, take a look at page Dolibarr_Project#Developers_roles. Any developer with grade level "Yoda" or "Jedi" are possible mentors.

Follow the template of other proposals!

If you want to add other proposals, just follow the following template. All information are mandatory, even the Mentor name. If you don't have a mentor, you probably not read the beginning of this notice. Only the Backup mentor field is option (as it will be fill later by the Mentor itself).

• Project/Idea:
• Brief explanation:
• Expected results:
• Knowledge Prerequisite:
• Mentor:
• Backup mentor:

When adding an idea to this section, please try to include the following data: if the application is not widely known, a description of what it does and where its code lives a brief explanation the expected results pre-requisites for working on your project if applicable, links to more information or discussions mailing list or IRC channel for your application/library/module your name and email address for contact (if you're willing to be a mentor) If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first.

Idea 1 : REST interfaces/API

• Project/Idea title: REST interfaces/API
• Brief explanation: Develop a system to provides APIs using REST protocol.
• Knowledge Prerequisite: Eclipse + GIT + PHP 5.3+
• Mentor: Laurent Destailleur
• Backup mentor: Régis Houssin
• Why: Be more ready to cloud or mobile usage that need such API (preferred to SOAP) to exchange data.
• Expected results: Having 100% of services actually covered by SOAP, covered by REST and unit tests.
• Difficulty/time to achieve (Low/Medium/High): Low
• Risk on project stability (Low/Medium/High): Low
• Long description:

Idea 2 : An android frontend for Dolibarr ERP-CRM

• Project/Idea title: An android frontend for Dolibarr ERP-CRM
• Brief explanation: Develop an application for android optimized for using Dolibarr on a smartphone.
• Expected results: Having a software we can use on a smartphone with a resolution of 640 x 240 (no fields cuts by screen size, easy navigation into menus).
• Knowledge Prerequisite: Eclipse + GIT + PHP 5.3+ for server pages to develop + (JQuery mobile xor Android SDK, it depends on technology choice)
• Mentor: Régis Houssin
• Backup mentor: Juanjo Menent
• Why: Dolibarr is a web software. Using it with a smartphone works in the same way as using it from a browser desktop. However, screens are very rich with information and often too rich for a friendly usage with a small screen. Goal is to provide an interface with the most possible features that is optimized for smartphone screens.
• Difficulty/time to achieve (Low/Medium/High): High
• Risk on project stability (Low/Medium/High): Medium
• Long description:

Idea 3 : System to reports/analyze Dolibarr usage

• Project/Idea title: System to reports/analyze Dolibarr usage
• Brief explanation: Develop a system (external tools, frontend, integrated API) to allow users to send reports on their Dolibarr usage (statistics, most often activated modules, etc...). Add backend to analyze results into graphical reports.
• Expected results: Having the report feature integrated into Dolibarr core code. Having a frontend application to analyze reports.
• Knowledge Prerequisite: Eclipse + GIT + PHP 5.3+
• Mentor: Philippe Grand
• Backup mentor: Laurent Destailleur
• Why: Dolibarr community is growing quickly. But as many opensource software, it is very difficult to know how download, who use and how, as users are often anonymous. The Dolibarr foundation however needs such information to help to promote software according to countries, kind of users, ...
• Difficulty/time to achieve (Low/Medium/High): Low
• Risk on project stability (Low/Medium/High): Medium
• Long description:

Idea 4 : Create a system to build a Dolibarr module using MDA generator

• Project/Idea title: Create a system to build a Dolibarr module using MDA generator
• Brief explanation: Dolibarr framework allow any Develop modules that modify Dolibarr features by adding code, triggers, hooks, menus, data, etc. Goal of a system is to allow a developer to define its module specification suing MDA XML design and code should be generated.
• Expected results:
• Knowledge Prerequisite: Eclipse + GIT + PHP + MDA Knowledges
• Mentor: Cyrille De Lambert
• Backup mentor: Régis Houssin
• Why: Increase speed of developing business modules.
• Difficulty/time to achieve (Low/Medium/High): High
• Risk on project stability (Low/Medium/High): Low
• Long description:

More idea to add

Note: feedbacks from GSOC 2012: - +idea (10 small, 20 large org, recommanded: 15): My feedback: - Better english - Add picto to make page beautifull - Add link to mentors (photo) - Add logo of GSOC