Google Summer of Code Ideas 2013

Welcome on the page dedicated to the Idea List (suggested by the Dolibarr core team, Dolibarr users or students) for the GSOC (Google Summer Of Code). Please read the introduction before adding/editing your own idea.

'''LAST NEWS: WE ARE SORRY, BUT THE DOLIBARR FOUNDATION WAS NOT SELECTED AS A MENTOR FOR GOOGLE SUMMER OF CODE 2013.

SORRY FOR ANY STUDENT THAT WAS INTERESTING BY AN IDEA HERE.

WE HOPE TO HAVE MORE LUCK NEXT YEAR (2014) '''

= Introduction =

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 Dolibarr development mailing list dolibarr-dev@nongnu.org (Subscription to mailing-list is opened to anybody using the form https://lists.nongnu.org/mailman/listinfo/dolibarr-dev).

For information of possible mentors, take a look at page Dolibarr_Project. Any developer with grade level "Yoda", "Jedi" or "Admiral" are possible mentors. You can look for a dedicated mentor for your idea by contacting the Dolibarr development mailing-list dolibarr-dev@nongnu.org (Subscription to mailing-list is opened to anybody using the form https://lists.nongnu.org/mailman/listinfo/dolibarr-dev)

Follow the template for ideas
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). Students already interested in working on this task:
 * Project/Idea title:
 * Brief explanation:
 * Knowledge Prerequisite:
 * Mentor:
 * Backup mentor:
 * Why:
 * Expected results:
 * Difficulty/time to achieve (Low/Medium/High):
 * Risk on project stability (Low/Medium/High):
 * More information/Long description (at least 100 words):
 * Name of student (if known)

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.

= List of already submitted ideas =

art.png Idea 1 : REST interfaces/API
More information: All main elements of Dolibarr must have a REST API to offer CRUD services (Create/Read/Update/Delete). List of elements to support are: Invoices, Proposals, Orders, Users, Members, Thirdparties, Agenda events We recommand building first a generator to generate API from classes of this elements.

Students already interested in working on this task:
 * Udit Saxena saxena.udit@gmail.com
 * Mikołaj Pawlikowski (speak french)
 * Viraj sinha virajssinha@gmail.com
 * Bhuvnesh Joshi bhuvneshonline@gmail.com
 * umangkedia1990@gmail.com
 * clement.noiville@etu.utc.fr (speak french)
 * dchimeno@gmail.com (spanish)

art.png Idea 2 : An android frontend/application
More information: To complete

Students already interested in working on this task:
 * ashutosh borkar 
 * vipin vijay 
 * Shekhar Kadyan 
 * Aagam Shah aagam94@gmail.com
 * abhimanyu.gr8@gmail.com

art.png Idea 3 : System to reports/analyze Dolibarr usage
More information: To complete

Students already interested in working on this task:
 * Harsha Kumara harsz89@gmail.com
 * erangamapa@gmail.com

art.png Idea 4 : Create a system to build a Dolibarr module using MDA generator
More information: To complete

Students already interested in working on this task:
 * None yet

art.png Idea 5 : Improved code coverage
More information:
 * Dolibarr does not provide any continuous integration platform. However, current PHPUnit cases are available into directory /test of Dolibarr github sources. Process to generate HTML code coverage report is described into file test/README.

Students already interested in working on this task:
 * raygsoc2013@gmail.com

art.png Idea 6 : Develop Juju interfaces for Dolibarr
More information:
 * The Dolibarr foundation can provide platform (virtual servers) to make development and tests.

Students already interested in working on this task:
 * None yet

art.png Idea 7 : Rewrite of multilangual module for Dolibarr wiki
More information:
 * The Dolibarr foundation provide platform (virtual server) to make development and tests.
 * The Dolibarr foundation provide data and snapshot of old system.

Students already interested in working on this task:
 * None yet

art.png Idea 8 : Build a tool to generate PDF documentation from Dolibarr wiki
More information:
 * Tool must use a text file that list all wiki page to include. Pages are added one after one into PDF in same order than entry text file.
 * Pages must be spidered by the tool as a PDF file and only part found into a start and end tag (to define) must be kept as the HTML content to add into PDF.
 * Tool must be written with PHP and use TCPDF (and function writeHTMLCell to keep HTML format).
 * Some other rules to clean/format PDF should be added.
 * Tests can be done from official wiki wiki.dolibarr.org
 * This project can become an independant OpenSource project as all project using a wiki need such a tool (existing tool are not able to take only a part of a wiki pages, making them useless to build a professional PDF).

Students already interested in working on this task:
 * shailrishabh@gmail.com