Dolibarr ERP CRM Wiki

Changes

Google Summer of Code Ideas 2013 (view source)

Revision as of 20:54, 16 September 2015

5,075 bytes added ,  9 years ago
m
no edit summary
Line 3: Line 3:     
<center>[[File:Gsoc.jpg|120px]]</center>
 
<center>[[File:Gsoc.jpg|120px]]</center>
−
Welcome on the page dedicated to the Idea List (suggested by the Dolibarr core team, Dolibarr users or students) for the Google Summer Of Code (please read the introduction before adding/editing your own idea).
+
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.
      −
NOTE FOR STUDENT: WE MUST FIRST WAIT VALIDATION OF GOOGLE TO BE AN OFFICIAL MENTOR FOR GOOGLE SUMMER OF CODE BEFORE APPLYING FOR AN 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)
 +
'''
 +
 
   −
GOOGLE PUBLISH LIST OF ACCEPTING MENTORING ORGANIZATION THE 8TH OF APRIL, SO PLEASE, COME BACK THE 9TH OF APRIL ON THIS PAGE.
        Line 29: Line 34:  
* Why:
 
* Why:
 
* Expected results:
 
* Expected results:
−
* Long description (at least 100 words):
+
* 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:
 
Students already interested in working on this task:
 
* Name of student (if known)
 
* Name of student (if known)
Line 38: Line 45:  
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)
 
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.
 
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 =
 
= List of already submitted ideas =
    
== [[File:art.png|link=]] Idea 1 : REST interfaces/API ==
 
== [[File:art.png|link=]] Idea 1 : REST interfaces/API ==
−
* Project/Idea title: REST interfaces/API
+
{{GSOCIdea
−
* Brief explanation: Develop a system to provides APIs using REST protocol.
+
|title=REST interfaces/API
−
* Knowledge Prerequisite: Eclipse + GIT + [http://en.wikipedia.org/wiki/REST REST protocol] + PHP 5.3+
+
|briefexplanation=Develop a system to provides APIs using REST protocol.
−
* Mentor: [[Laurent Destailleur]]
+
|knowledge=Eclipse + GIT + [http://en.wikipedia.org/wiki/REST REST protocol] + PHP 5.3+
−
* Backup mentor: To define
+
|mentor=[[Laurent Destailleur]]
−
* Why: Be more ready to cloud or mobile usage that need such API (preferred to SOAP) to exchange data.
+
|mentor_backup=[[Florian Henry]]
−
* Expected results: Having 100% of services actually covered by SOAP, covered by REST, including REST unit tests.
+
|why=Be more ready to cloud or mobile usage that need such API (preferred to SOAP) to exchange data.
−
* Difficulty/time to achieve (Low/Medium/High): Low
+
|expected_results=Having 100% of services actually covered by SOAP, covered by REST, including REST unit tests.
−
* Risk on project stability (Low/Medium/High): Low
+
|difficulty=Medium
−
* Long description:
+
|risk=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:
 
Students already interested in working on this task:
−
* Mikołaj Pawlikowski
+
* Udit Saxena saxena.udit@gmail.com
 +
* Mikołaj Pawlikowski (speak french)
 
* Viraj sinha virajssinha@gmail.com
 
* Viraj sinha virajssinha@gmail.com
 
* Bhuvnesh Joshi bhuvneshonline@gmail.com
 
* Bhuvnesh Joshi bhuvneshonline@gmail.com
 +
* umangkedia1990@gmail.com
 +
* clement.noiville@etu.utc.fr (speak french)
 +
* dchimeno@gmail.com (spanish)
    
== [[File:art.png|link=]] Idea 2 : An android frontend/application ==
 
== [[File:art.png|link=]] Idea 2 : An android frontend/application ==
−
* Project/Idea title: An android frontend for Dolibarr ERP-CRM
+
{{GSOCIdea
−
* Brief explanation: Develop an application for android optimized for using Dolibarr on a smartphone.
+
|title= An android frontend for Dolibarr ERP-CRM
−
* Expected results: Having a 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).
+
|briefexplanation=Develop an application for android optimized for using Dolibarr on a smartphone.
−
* Knowledge Prerequisite: Eclipse + GIT + PHP 5.3+ for server pages to develop + ([http://jquerymobile.com/ JQuery mobile] xor Android SDK, it depends on student technology choice)
+
|knowledge=Eclipse + GIT + PHP 5.3+ for server pages to develop + ([http://jquerymobile.com/ JQuery mobile] + Android Java SDK.
−
* Mentor: To define
+
|mentor=[[Laurent Destailleur]]
−
* Backup mentor: To define
+
|mentor_backup=[[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
+
|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.
−
* Risk on project stability (Low/Medium/High): Medium
+
|difficulty=High
−
* Long description:
+
|risk=Medium
 +
}}
 +
 
 +
More information:
 +
To complete
    
Students already interested in working on this task:
 
Students already interested in working on this task:
Line 75: Line 96:  
* Shekhar Kadyan <shekhar.kadyan@gmail.com>
 
* Shekhar Kadyan <shekhar.kadyan@gmail.com>
 
* Aagam Shah aagam94@gmail.com
 
* Aagam Shah aagam94@gmail.com
 +
* abhimanyu.gr8@gmail.com
    
== [[File:art.png|link=]] Idea 3 : System to reports/analyze Dolibarr usage ==
 
== [[File:art.png|link=]] Idea 3 : System to reports/analyze Dolibarr usage ==
−
* Project/Idea title: System to reports/analyze Dolibarr usage
+
{{GSOCIdea
−
* 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.
+
|title=System to reports/analyze Dolibarr usage
−
* Expected results: Having the report feature integrated into Dolibarr core code. Having a frontend application to analyze reports.
+
|briefexplanation=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+
+
|knowledge=Eclipse + GIT + PHP 5.3+
−
* Mentor: [[Philippe Grand]]
+
|mentor=[[Jean-François Ferry]]
−
* Backup mentor: [[Laurent Destailleur]]
+
|mentor_backup=[[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, ...
+
|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
+
|expected_results=Having the report feature integrated into Dolibarr core code. Having a frontend application to analyze reports.
−
* Risk on project stability (Low/Medium/High): Medium
+
|difficulty=Low
−
* Long description:
+
|risk=Low
 +
}}
 +
 
 +
More information:
 +
To complete
 +
 
 
Students already interested in working on this task:
 
Students already interested in working on this task:
 
* Harsha Kumara harsz89@gmail.com
 
* Harsha Kumara harsz89@gmail.com
Line 92: Line 119:     
== [[File:art.png|link=]] Idea 4 : Create a system to build a Dolibarr module using MDA generator ==
 
== [[File:art.png|link=]] 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
+
{{GSOCIdea
−
* 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.
+
|title=Create a system to build a Dolibarr module using MDA generator
−
* Expected results:
+
|briefexplanation=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 + [http://en.wikipedia.org/wiki/Model-driven_architecture MDA] + PHP 5.3+
+
|knowledge=Eclipse + GIT + [http://en.wikipedia.org/wiki/Model-driven_architecture MDA] + PHP 5.3+
−
* Mentor: To define
+
|mentor=[[Laurent Destailleur]]
−
* Backup mentor: To define
+
|mentor_backup=to define
−
* Why: Increase speed of developing business modules.
+
|why=Increase speed of developing business modules.
−
* Difficulty/time to achieve (Low/Medium/High): High
+
|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.
−
* Risk on project stability (Low/Medium/High): Low
+
|difficulty=High
−
* Long description:
+
|risk=Low
 +
}}
 +
 
 +
More information:
 +
To complete
 +
 
 
Students already interested in working on this task:
 
Students already interested in working on this task:
 
* None yet
 
* None yet
    
== [[File:art.png|link=]] Idea 5 : Improved code coverage ==
 
== [[File:art.png|link=]] Idea 5 : Improved code coverage ==
−
* Increase code coverage of class to reach 50%
+
{{GSOCIdea
 +
|title=Improved code coverage
 +
|briefexplanation=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=Eclipse + PHP 5.3+ + PHPUnit
 +
|mentor=[[Florian Henry]]
 +
|mentor_backup=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=Low
 +
|risk=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
 +
 
 +
== [[File:art.png|link=]] Idea 6 : Develop Juju interfaces for Dolibarr ==
 +
{{GSOCIdea
 +
|title=Develop Juju interfaces for Dolibarr
 +
|briefexplanation=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=Eclipse + PHP 5.3+ + Juju
 +
|mentor=[[Laurent Destailleur]]
 +
|mentor_backup=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=High
 +
|risk=Low
 +
}}
 +
 
 +
More information:
 +
* The Dolibarr foundation can provide platform (virtual servers) to make development and tests.
 +
 
 
Students already interested in working on this task:
 
Students already interested in working on this task:
 
* None yet
 
* None yet
   −
== [[File:art.png|link=]] Idea 6 : Develop Juju interfaces for Dolibarr ==
+
== [[File:art.png|link=]] Idea 7 : Rewrite of multilangual module for Dolibarr wiki ==
−
* Create charms scripts for Dolibarr, to allow deployment of Dolibarr into compatible Cloud services, using https://juju.ubuntu.com/.
+
{{GSOCIdea
 +
|title=Rewrite of multilangual module for dolibarr wiki
 +
|briefexplanation=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.
 +
|mentor=[[Juanjo Menent]]
 +
|mentor_backup=[[Laurent Destailleur]]
 +
|knowledge=PHP 5.3+ + Mediawiki
 +
|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=High
 +
|risk=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:
 
Students already interested in working on this task:
 
* None yet
 
* None yet
    +
== [[File:art.png|link=]] Idea 8 : Build a tool to generate PDF documentation from Dolibarr wiki ==
 +
{{GSOCIdea
 +
|title=Develop a tool to generate a PDF documentation getting sources from wiki
 +
|briefexplanation=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.
 +
|mentor=[[Laurent Destailleur]]
 +
|mentor_backup=[[Jean-François Ferry]]
 +
|knowledge=PHP 5.3+ + Mediawiki + PDF library TCPDF
 +
|why=Provide a PDF documentation instead of online wiki without duplicating documentation.
 +
|expected_results=A tool that generate a PDF file
 +
|difficulty=Medium
 +
|risk=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
   −
= Feedbacks from GSOC 2012 =
+
== [[File:art.png|link=]] Idea 9 : Develop a webmail module for Dolibarr ==
−
- +idea (10 small, 20 large org, recommanded: 15):
+
{{GSOCIdea
−
My feedback:
+
|title=Develop a webmail module for Dolibarr
−
- Better english
+
|briefexplanation=Develop a webmail module for Dolibarr from roundcube product, when setup is IMAP.
−
- Add picto to make page beautifull
+
|mentor=[[Florian Henry]]
−
- Add link to mentors (photo)
+
|mentor_backup=[[Jean-François Ferry]]
−
- Add logo of GSOC
+
|knowledge=PHP 5.3+ + Roundcube
 +
|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=Medium
 +
|risk=Low
 +
}}
Retrieved from "https://wiki.dolibarr.org/index.php?title=Special:MobileDiff/28722...34353"