Open a page on Dolibarr org, fr, etc... with a "whatever user" of Github and you will transform Github in a forum with trollers (like me) that complain on whatever problem they have :) example : "my wireless mouse has no battery, can I use a wired one with Dolibarr ?"
Yes, Dolibarr should be simple for users, but those users that host Dolibarr on their computers, should know a bit of Dolibarr... or they should take a host... or post on the forum and cross fingers. When i find something free, i try to understand it. When it's a paid one, i expect it to do as much possible out of the box. Doliforge was manageable and quite organised because it had a few reporters (like github will have), but non friendly because it was "closed circle". in Github it's public, i can check code and issues, pull request, etc... with no account. And an enormous majoirty of "silent devs" are on github, checking code, issues, progress of the project. I'm not a dev, but I'm happy to try to read code and post on github when i see a line which could be wrong. *Hubert ANDRIOLO* *Gérant F.M. MEDICAL et NORD HYGIENE* Mobile: +33 (0) 6 23 10 17 31 Fax: +33 (0) 9 56 51 95 71 Site: www.fournisseur-medical.com *FM MEDICAL - NORD HYGIENE* 280, rue berthie Albrecht 62110 Hénin-Beaumont SIRET : 532 788 700 00021 N° de TVA : FR15 532 788 700 2015-03-26 18:54 GMT+01:00 <[email protected]>: > Send Dolibarr-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Dolibarr-dev digest..." > > > Today's Topics: > > 1. Re: New rule to report bug and task (Charles Benke) > 2. Re: New rule to report bug and task (Sasa Ostrouska) > 3. Re: New rule to report bug and task (Sasa Ostrouska) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 26 Mar 2015 18:26:52 +0100 > From: "Charles Benke" <[email protected]> > To: "'Posts about Dolibarr ERP & CRM development and coding'" > <[email protected]> > Subject: Re: [Dolibarr-dev] New rule to report bug and task > Message-ID: <00ae01d067ea$0d747ad0$285d7070$@[email protected]> > Content-Type: text/plain; charset="utf-8" > > Hello,, > > I think we need to simplify the bug report the more as possible and use > github is not simple for simple users > > Please consider that Dolibarr users are not all developer with a github > account > > A good way for reporting bug is a simple form with a feature of attached > picture on the Dolibarr main website (org, fr, ?) > > It?s not the job of an user to make the job of a developper > > > > Bien cordialement, > > Charles-Fran?ois BENKE > > > > De : [email protected] [mailto: > [email protected]] De la part de > Laurent Destailleur (aka Eldy) > Envoy? : jeudi 26 mars 2015 16:08 > ? : ML Dolibarr dev > Objet : [Dolibarr-dev] New rule to report bug and task > > > > Few days ago, we decided to abandon our current bug and request tracker to > follow Dolibarr bugs and features requests. > > > > You must use now the Issue tracker of Github. > > You will find here: https://github.com/Dolibarr/dolibarr (click on link > "Issue" on left of page). > > > > Also don't forget to set tags on your report to qualify your report. > > > > > > > > WHY A NEW TRACKING SYSTEM ? > > > > Using the old tracker was just a pain for several reasons : > > > > * When closing a bug, we had to close the bug manualy into the bug > tracker. It wasn't done or when done, it was a lot of waste ot time. This > is past, now closing a bug into github with "Closed #xxx" into the > description of the change automatically close the bug. > > > > * The id of bug reported into the comment of github was an id into another > system. So switching to code from ticket or to ticket description from code > was just awful. Now, one click is enough. > > > > * The old tracker was not public and not visible. You had to create an > account making the bug and feature tracker difficult to use for "quick > report". > > > > * Our old tracker had a very bad visibility. I hope this will change. > > > > * Our old tracker was maintained by the Dolibarr foundation. This need a > lot of time spent by the core team. Removing completely this tasks should > provide more free time us. > > > > * Integration with IDE tools like eclipse was difficult. You may find > plugins more easily with github. > > > > > > > > WHAT ABOUT OLD TICKETS: > > > > * That is the negative point. But i think we must accept this to progress: > Old tickets still opened, like closed one will just be forgotten. We will > enter them back into new GitHub tracker day by day. > > > > > > > > Enjoy our new tracking system. Who wil be the first to enter one issue ? > > > > > > Laurent Destailleur (aka eldy) > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.nongnu.org/archive/html/dolibarr-dev/attachments/20150326/d1021d65/attachment.html > > > > ------------------------------ > > Message: 2 > Date: Thu, 26 Mar 2015 14:49:20 -0300 > From: Sasa Ostrouska <[email protected]> > To: "Posts about Dolibarr ERP & CRM development and coding" > <[email protected]> > Subject: Re: [Dolibarr-dev] New rule to report bug and task > Message-ID: > < > calferdzk+yegamnj70gjjbe7hc9xp4q8vu21irqod8gvz_f...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Simply great decision ! > Rgds > Saxa > > On Thu, Mar 26, 2015 at 12:08 PM, Laurent Destailleur (aka Eldy) < > [email protected]> wrote: > > > Few days ago, we decided to abandon our current bug and request tracker > to > > follow Dolibarr bugs and features requests. > > > > You must use now the Issue tracker of Github. > > You will find here: https://github.com/Dolibarr/dolibarr (click on link > > "Issue" on left of page). > > > > Also don't forget to set tags on your report to qualify your report. > > > > > > > > WHY A NEW TRACKING SYSTEM ? > > > > Using the old tracker was just a pain for several reasons : > > > > * When closing a bug, we had to close the bug manualy into the bug > > tracker. It wasn't done or when done, it was a lot of waste ot time. This > > is past, now closing a bug into github with "Closed #xxx" into the > > description of the change automatically close the bug. > > > > * The id of bug reported into the comment of github was an id into > another > > system. So switching to code from ticket or to ticket description from > code > > was just awful. Now, one click is enough. > > > > * The old tracker was not public and not visible. You had to create an > > account making the bug and feature tracker difficult to use for "quick > > report". > > > > * Our old tracker had a very bad visibility. I hope this will change. > > > > * Our old tracker was maintained by the Dolibarr foundation. This need a > > lot of time spent by the core team. Removing completely this tasks should > > provide more free time us. > > > > * Integration with IDE tools like eclipse was difficult. You may find > > plugins more easily with github. > > > > > > > > WHAT ABOUT OLD TICKETS: > > > > * That is the negative point. But i think we must accept this to > progress: > > Old tickets still opened, like closed one will just be forgotten. We will > > enter them back into new GitHub tracker day by day. > > > > > > > > Enjoy our new tracking system. Who wil be the first to enter one issue ? > > > > > > Laurent Destailleur (aka eldy) > > > > > > _______________________________________________ > > Dolibarr-dev mailing list > > [email protected] > > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.nongnu.org/archive/html/dolibarr-dev/attachments/20150326/ca6e9c7b/attachment.html > > > > ------------------------------ > > Message: 3 > Date: Thu, 26 Mar 2015 14:54:00 -0300 > From: Sasa Ostrouska <[email protected]> > To: "Posts about Dolibarr ERP & CRM development and coding" > <[email protected]> > Subject: Re: [Dolibarr-dev] New rule to report bug and task > Message-ID: > < > calferdzxhfcegs-txksbzbrgyx_pk7hwsk76dqvwfuicsyk...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Thu, Mar 26, 2015 at 2:26 PM, Charles Benke <[email protected]> > wrote: > > > Hello,, > > > > I think we need to simplify the bug report the more as possible and use > > github is not simple for simple users > > > > Please consider that Dolibarr users are not all developer with a github > > account > > > > A good way for reporting bug is a simple form with a feature of attached > > picture on the Dolibarr main website (org, fr, ?) > > > > It?s not the job of an user to make the job of a developper > > > > > I think this can be solved by makeing available a page in Dolibarr itself. > Which would have the ability to post directly to github as a dolibarr or > whatever user. > Sometimes users which do not have development skills can report something > as a bug but in reality its just a missing functionality or they do not > know how to do it. > > Rgds > Saxa > > > > > > > Bien cordialement, > > > > Charles-Fran?ois BENKE > > > > > > > > *De :* [email protected] [mailto: > > [email protected]] *De la part de* > > Laurent Destailleur (aka Eldy) > > *Envoy? :* jeudi 26 mars 2015 16:08 > > *? :* ML Dolibarr dev > > *Objet :* [Dolibarr-dev] New rule to report bug and task > > > > > > > > Few days ago, we decided to abandon our current bug and request tracker > to > > follow Dolibarr bugs and features requests. > > > > > > > > You must use now the Issue tracker of Github. > > > > You will find here: https://github.com/Dolibarr/dolibarr (click on link > > "Issue" on left of page). > > > > > > > > Also don't forget to set tags on your report to qualify your report. > > > > > > > > > > > > > > > > WHY A NEW TRACKING SYSTEM ? > > > > > > > > Using the old tracker was just a pain for several reasons : > > > > > > > > * When closing a bug, we had to close the bug manualy into the bug > > tracker. It wasn't done or when done, it was a lot of waste ot time. This > > is past, now closing a bug into github with "Closed #xxx" into the > > description of the change automatically close the bug. > > > > > > > > * The id of bug reported into the comment of github was an id into > another > > system. So switching to code from ticket or to ticket description from > code > > was just awful. Now, one click is enough. > > > > > > > > * The old tracker was not public and not visible. You had to create an > > account making the bug and feature tracker difficult to use for "quick > > report". > > > > > > > > * Our old tracker had a very bad visibility. I hope this will change. > > > > > > > > * Our old tracker was maintained by the Dolibarr foundation. This need a > > lot of time spent by the core team. Removing completely this tasks should > > provide more free time us. > > > > > > > > * Integration with IDE tools like eclipse was difficult. You may find > > plugins more easily with github. > > > > > > > > > > > > > > > > WHAT ABOUT OLD TICKETS: > > > > > > > > * That is the negative point. But i think we must accept this to > progress: > > Old tickets still opened, like closed one will just be forgotten. We will > > enter them back into new GitHub tracker day by day. > > > > > > > > > > > > > > > > Enjoy our new tracking system. Who wil be the first to enter one issue ? > > > > > > > > > > > > Laurent Destailleur (aka eldy) > > > > > > > > _______________________________________________ > > Dolibarr-dev mailing list > > [email protected] > > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.nongnu.org/archive/html/dolibarr-dev/attachments/20150326/f8d65902/attachment.html > > > > ------------------------------ > > _______________________________________________ > Dolibarr-dev mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > > > End of Dolibarr-dev Digest, Vol 144, Issue 14 > ********************************************* >
_______________________________________________ Dolibarr-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
