Google Summer of Code Ideas 2013: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 29: Line 29:
* Why:
* Why:
* Expected results:
* Expected results:
* Long description (at least 100 words):
* 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 50: Line 50:
* Why: Be more ready to cloud or mobile usage that need such API (preferred to SOAP) to exchange data.
* 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.
* Expected results: Having 100% of services actually covered by SOAP, covered by REST, including REST unit tests.
* Difficulty/time to achieve (Low/Medium/High): Low
* Difficulty/time to achieve (Low/Medium/High): Medium
* Risk on project stability (Low/Medium/High): Low
* Risk on project stability (Low/Medium/High): Low
* Long description:
* More information:
All main elementsof 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 elements.
 
Students already interested in working on this task:
Students already interested in working on this task:
* Mikołaj Pawlikowski (speak french)
* Mikołaj Pawlikowski (speak french)
Line 69: Line 80:
* Difficulty/time to achieve (Low/Medium/High): High
* Difficulty/time to achieve (Low/Medium/High): High
* Risk on project stability (Low/Medium/High): Medium
* Risk on project stability (Low/Medium/High): Medium
* Long description:
* More information:
To complete


Students already interested in working on this task:
Students already interested in working on this task:
Line 76: Line 88:
* 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 ==
Line 87: Line 100:
* Difficulty/time to achieve (Low/Medium/High): Low
* Difficulty/time to achieve (Low/Medium/High): Low
* Risk on project stability (Low/Medium/High): Medium
* Risk on project stability (Low/Medium/High): Medium
* Long description:
* 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 102: Line 117:
* Difficulty/time to achieve (Low/Medium/High): High
* Difficulty/time to achieve (Low/Medium/High): High
* Risk on project stability (Low/Medium/High): Low
* Risk on project stability (Low/Medium/High): Low
* Long description:
* 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%
* Project/Idea title: Improved code coverage
* Brief explanation: Increase code coverage of classes to reach 50%
* Difficulty/time to achieve (Low/Medium/High): Low
* Risk on project stability (Low/Medium/High): Low
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 6 : Develop Juju interfaces for Dolibarr ==
* Create charms scripts for Dolibarr, to allow deployment of Dolibarr into compatible Cloud services, using https://juju.ubuntu.com/.
* 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/.
* 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
 
== [[File:art.png|link=]] 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.
* 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.
* Knowledge Prerequisite: PHP + Mediawiki
* Mentor: [[Laurent Destailleur]]
* Backup mentor: to define
* Why: Old version of multilangual mediwawiki module is not compatible with new version of mediawiki. We must replace it with a new system.
* Difficulty/time to achieve (Low/Medium/High): Medium
* 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:
Students already interested in working on this task:
* None yet
* None yet

Navigation menu