Report board meeting 20141204 teleconf: Difference between revisions

From Dolibarr ERP CRM Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 21: Line 21:
= Subject =
= Subject =
* New Dolibarr Prefered Partner Request  
* New Dolibarr Prefered Partner Request  
** Kreiz IT : Accepted
    Kreiz IT : Accepted
** From now on, new application for preferred partner will be validated by a poll and send to the board members
    From now on, new application for preferred partner will be validated by a poll and send to the board members





Revision as of 20:16, 4 December 2014



Title/Date/Location

  • Title: Board meeting
  • Date: 04/12/2014
  • Location: Hangout

Presents

Valid members of the board (subscription up to date), present: Laurent Destailleur Juanjo Menent Philippe Grand Maxime Kohlhaas


Subject

  • New Dolibarr Prefered Partner Request
   Kreiz IT : Accepted
   From now on, new application for preferred partner will be validated by a poll and send to the board members



  • Dolistore prestashop upgrade
    • Philippe ask to Régis Houssin to study the prestashop upgade and ask for a proposal for prestashop migration to the latest version, the specific module to manage resellers and have the payment working with paypal and Caisse d'Épargne.
    • Have the Dolibarr Foundation convention signed by him


  • Use GitBug as maintenance tools (
  Take task and bug from doliforge to github
  Advantage : fully integrated to devtools
  Disadvantage:

=> May be one day github will be a paid system per bug or task ... => Question: Is there a way to migrate existing content into github ? => GitHub contains a bug tracker but no tracker feature => GitHub does not contain important features into tracker like priority/module/criticality, task opened to external developer, ... => What about DoliForge/Tuleap Partner ship ?

    • Where are we on the project to migrate on SaaS Tuleap solution ?
    • Waiting for JFF to make a decision to move to GitHub

In asso.dolibarr.org/dolibarr :

  • A) Before working on any other service/enhancement that the foundation can do/offer, we should enhance automation of already existing tool.

For example, we should: - create a module to sync permission of unix account onto dolibarr foundation servers from dolibarr foundation manager. - upgrade tools on server (joomla, doliforge, ...) - automation of payment when a subscription is renewed - automationof sending pdf for subscription

   Tools spécifications :
   Members validated (payment ok) into Dolibarr of Dolibarr fundation :
   => Create wiki account=> plugin media wiki
   => Create Doliforge account => plugin Tuleap
   => Create DoliStore account => plugin Prestashop
   => Create dolibarr.org, dolibarr.fr account => Plugin Joomla
   => Link paypal members paiement to members status
   => Mailing list => Plugin MailMan done => to test
   => Create unix account
   If members is pass to resiliated =>  remove all acccess
   Désactivé Dans les outils si membre résilié

=> Why not use a LDAP directory?

   Progress ? 


  • Dolibarr ERP & CRM trademark.

=> Some news about mark deposit process ?

  • C) Draft of Dolibarr integrator label
   Task to do by Florian henry => Resend CGV to DoliStore sellers, with motivation letters to keep module up to date and new Dolistore module validation rules (done ?)
   => Florian HENRY : Really difficult to find sellers ! Need real sellers process in this prestahop and upgrade it to 1.6 !
   => New GCV with obligation of support if module is not free
  • D) Doliforge "Demande de promotion d'annonce sur Doliforge" process
   To discuss 
  • E) Vendre 1-2 espaces annonces pub sur sites Dolibarr pour des services autour de Dolibarr en plus de la pub google (qui promeut les autres ERP...)
  To discuss next time (part solved by point on advertising budget)

=> This need to develop tools to manage this: following advertisers, payments, documentations, juridical rules, etc.

=> LDR: I did some tests to use joomla to add and follow banners. Seems to works correctly.