Google Summer of Code Ideas 2013

From Dolibarr ERP CRM Wiki
Jump to navigation Jump to search


Back to home page of
the Dolibarr foundation

Gsoc.jpg

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#Developers_roles. 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).

  • 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):

Students already interested in working on this task:

  • 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

  • Project/Idea title: REST interfaces/API
  • Brief explanation: Develop a system to provides APIs using REST protocol.
  • Knowledge Prerequisite: Eclipse + GIT + REST protocol + PHP 5.3+
  • Mentor: Laurent Destailleur
  • Backup mentor: Florian Henry
  • 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, including REST unit tests.
  • Difficulty/time to achieve (Low/Medium/High): Medium
  • Risk on project stability (Low/Medium/High): Low

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

  • Project/Idea title: An android frontend for Dolibarr ERP-CRM
  • Brief explanation: Develop an application for android optimized for using Dolibarr on a smartphone.
  • Knowledge Prerequisite: Eclipse + GIT + PHP 5.3+ for server pages to develop + (JQuery mobile + Android Java SDK.
  • Mentor: Laurent Destailleur
  • Backup mentor: Florian Henry
  • 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.
  • Expected results: Having software we can use on an Android smartphone with a resolution of 640 x 240 (no fields cuts by screen size, easy navigation into menus).
  • Difficulty/time to achieve (Low/Medium/High): High
  • Risk on project stability (Low/Medium/High): Medium

More information: To complete

Students already interested in working on this task:

  • ashutosh borkar <ashutosh.borkar@gmail.com>
  • vipin vijay <vipin.vijay.kumar9@gmail.com>
  • Shekhar Kadyan <shekhar.kadyan@gmail.com>
  • Aagam Shah aagam94@gmail.com
  • abhimanyu.gr8@gmail.com

Art.png 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.
  • Knowledge Prerequisite: Eclipse + GIT + PHP 5.3+
  • Mentor: Jean-François Ferry
  • 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, ...
  • Expected results: Having the report feature integrated into Dolibarr core code. Having a frontend application to analyze reports.
  • Difficulty/time to achieve (Low/Medium/High): Low
  • Risk on project stability (Low/Medium/High): Low

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

  • 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.
  • Knowledge Prerequisite: Eclipse + GIT + MDA + PHP 5.3+
  • Mentor: Laurent Destailleur
  • Backup mentor: to define
  • Why: Increase speed of developing business modules.
  • Expected results: Be able to design with a graphical tool, specification of a module to manage an element (create, list, edit, delete) and be able to generate code to get a working Dolibarr module.
  • Difficulty/time to achieve (Low/Medium/High): High
  • Risk on project stability (Low/Medium/High): Low

More information: To complete

Students already interested in working on this task:

  • None yet

Art.png Idea 5 : Improved code coverage

  • Project/Idea title: Improved code coverage
  • Brief explanation: Increase code coverage of classes to reach 50% (currently 25%). It may be by developping tools to generate code coverage scripts that cover:

- method of classes, - web services - command line scripts.

  • Knowledge Prerequisite: Eclipse + PHP 5.3+ + PHPUnit
  • Mentor: Florian Henry
  • Backup mentor: to define
  • Why: Increase speed of developing business modules.
  • Expected results: Code coverage reaching 50% (instead of 25% currently among all classes), 50% of web services (instead of 5%) and 10% of scripts (instead of 0%).
  • Difficulty/time to achieve (Low/Medium/High): Low
  • Risk on project stability (Low/Medium/High): Low

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

  • Project/Idea title: Develop Juju interfaces for Dolibarr
  • Brief explanation: Create charms scripts for Dolibarr, to allow deployment of Dolibarr into Cloud services compatible with juju, using https://juju.ubuntu.com/.

Enhance Dolibarr packaging tool to build the juju package.

  • Knowledge Prerequisite: Eclipse + PHP 5.3+ + Juju
  • Mentor: Laurent Destailleur
  • Backup mentor: to define
  • Why: Allow deployment of Dolibarr into Cloud services compatible.
  • Expected results: Being able to deploy Dolibarr onto with only a juju package.
  • Difficulty/time to achieve (Low/Medium/High): High
  • Risk on project stability (Low/Medium/High): Low

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

  • Project/Idea title: Rewrite of multilangual module for dolibarr wiki
  • Brief explanation: Dolibarr use mediawiki as its wiki documentation. A module not compatible has installed to manage multilanguage (it creates links between pages of same content with different languages). However this module is not compatible with recent version of mediawiki. Goal of task, is to migrate current wiki to new version of media wiki and rewrite the multilanguage module to have same features than old version. Also, old data must be migrated to match new version.
  • Knowledge Prerequisite: PHP 5.3+ + Mediawiki
  • Mentor: Juanjo Menent
  • Backup mentor: Laurent Destailleur
  • Why: Old version of multilangual mediwawiki module is not compatible with new version of mediawiki. We must replace it with a new system.
  • Expected results: Having the Dolibarr mediawiki documentation with last version of mediawiki and a module to manage multilanguage working like the deprecated old one did.
  • Difficulty/time to achieve (Low/Medium/High): High
  • Risk on project stability (Low/Medium/High): Low (if it fails, we keep old system)

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

  • Project/Idea title: Develop a tool to generate a PDF documentation getting sources from wiki
  • Brief explanation: Dolibarr documentation is written into a wiki. To avoid duplicating documentation, we need a tool that is able to take a list of pages from the wiki, find a start and end tag into page and use it as a HTML page to generate PDF.
  • Knowledge Prerequisite: PHP 5.3+ + Mediawiki + PDF library TCPDF
  • Mentor: Laurent Destailleur
  • Backup mentor: Jean-François Ferry
  • Why: Provide a PDF documentation instead of online wiki without duplicating documentation.
  • Expected results: A tool that generate a PDF file
  • Difficulty/time to achieve (Low/Medium/High): Medium
  • Risk on project stability (Low/Medium/High): Low

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

Art.png Idea 9 : Develop a webmail module for Dolibarr

  • Project/Idea title: Develop a webmail module for Dolibarr
  • Brief explanation: Develop a webmail module for Dolibarr from roundcube product, when setup is IMAP.
  • Knowledge Prerequisite: PHP 5.3+ + Roundcube
  • Mentor: Florian Henry
  • Backup mentor: Jean-François Ferry
  • Why: Add an important missing feature (webmail) with a solution that can be later fully integrated with other Dolibarr features (IMAP content can be manipulated by all other features of Dolibarr)
  • Expected results: A module that add a webmail integrated into Dolibarr menu and using same
  • Difficulty/time to achieve (Low/Medium/High): Medium
  • Risk on project stability (Low/Medium/High): Low
Retrieved from "https://wiki.dolibarr.org/index.php?title=Google_Summer_of_Code_Ideas_2013&oldid=34353"