2017-06-08 18:51 GMT+02:00 Sasa Ostrouska <cas...@gmail.com>: > Hi Eldy, > > On Thu, Jun 8, 2017 at 4:11 PM, Laurent Destailleur (aka Eldy) < > e...@destailleur.fr> wrote: > >> This is very difficult. >> If we publish a roadmap for future dev, it means someone else is engaged >> to make it at the stated date. But on Dolibarr project, there is no >> salaries, only volunteer. >> > I would sligtly disagree on this. No matter if is paid or not an organized > way of make some job is way better than the non organized one, especially > if you want to do that job in more people. But of course if the job is to > be done by one sole man than that person also can > organize its work but it have not to communicate it to any one else. This > is no matter if you are paid or not to do that job. > Said this, I would really like to see the exact direction the projcet is > going, as this will facilitate a lot of things in my opinion. > > In my thinking a Roadmap does not necessarily need to be done and finished > on certain date. Its like living on the road, immagine, > you start walking without knowing where you want to go or start walking to > arrive to a first defined stop. This does not mean you have to > be there on a defined date. > > So this means a development roadmap in my point of view would be something > like a whish list, we can call it also like this. Where all the involved > people would put their wished features and then contribute to it. By doing > it in that way for sure will it simplify for new people > on how to contribute and where to start. Some even further benefit would > be linking this features with the issues on github for example. > > But none of the above force you to finish it on some predefined date, just > it sits there until it is finished. > > >> And getting a guarantee than a volunteer do a work for a defined date is >> difficult to get. So only contributions that are received can be included. >> You can force a developer to work on a feature if you pay for it, but you >> can't for people that work for free. >> >> I do agree, and it is no sense to force people to do anything they do not > want to do. Especially when they do it for free. > > >> Announcing a roadmap for feature and then say finally, nobody did it so >> roadmap is not what we said is worse than providing a roadmap of future >> features >> > > I dont understand what you mean with this. >
I mean: There is no sense to announce a Roadmap to define content of version A with feature x and y if, at the end of the due date of roadmap (so when version A is released), the feature x and y is not present and instead we have feature z. > > >> The only thing we can decide in advance is a strategic direction, but not >> a roadmap of future development not yet done. This may change in the >> future, the day when developers will be payed to make development. But this >> way of working is not currently the situation. >> >> Ok strategic direction is then what I call a roadmap. Possibly on a wiki > page or place where people can see which features are wished or somebody is > working on and where the develop branch is heading. This would be very > helpful in my opinion to have people not working on the same thing or > joining to contribute on a certain feature being developed. > For the moment strategic direction is only announced during meeting in devcamps. We must find time to have it published differently. ... But well, there is so many other priorities... > > I also understand that this adds another layer of work, but I think there > is plenty of tools out there which could help with this. > > Just my thoughts and for sure I am not trying to push the work in some > direction or other. > > Rgds > Saxa > > >> >> >> >> 2017-06-08 15:09 GMT+02:00 Sasa Ostrouska <cas...@gmail.com>: >> >>> Is there also a roadmap for a development ? I mean, maybe would it be >>> useful to plan in advance what should come into >>> the next development. How is this done today by the dev comunity ? It is >>> something is traced along the time line somewhere >>> in irc or other communication channel or is it simply free and decided >>> by anybody who want to contribute. >>> >>> For example if I want a certain feature I have to do what to make it >>> included in the next development release ? >>> >>> Dont get me wrong I do not want to change the way you work, just would >>> like to understand it better. >>> >>> I have not looked on the wiki deeply to see if there is some kind of >>> page what should come in the next release. >>> >>> Rgds >>> Saxa >>> >>> >>> On Thu, Jun 8, 2017 at 1:03 PM, Sasa Ostrouska <cas...@gmail.com> wrote: >>> >>>> >>>> >>>> On Thu, Jun 8, 2017 at 10:39 AM, Laurent Destailleur (aka Eldy) < >>>> e...@destailleur.fr> wrote: >>>> >>>>> Take a look at bottom of page ;-) >>>>> https://wiki.dolibarr.org/index.php/Category:RoadMap >>>>> >>>>> However, only major version are recorded. >>>>> >>>>> Ops :) nice. >>>> Rgds >>>> Saxa >>>> >>>> >>>>> >>>>> 2017-06-08 12:28 GMT+02:00 Sasa Ostrouska <cas...@gmail.com>: >>>>> >>>>>> >>>>>> >>>>>> On Wed, Jun 7, 2017 at 10:16 PM, Laurent Destailleur (aka Eldy) < >>>>>> e...@destailleur.fr> wrote: >>>>>> >>>>>>> Hi Dolibarr developers. >>>>>>> >>>>>>> A maintenance release has been published for branch 5 (v5.0.3) and 4 >>>>>>> (v4.0.6). >>>>>>> >>>>>>> >>>>>>> Also, the beta of Dolibarr version 6 is officialy started. >>>>>>> No new features will be added from PR. >>>>>>> >>>>>>> As usual, "started development" can be continued to be finished and >>>>>>> stable for final release. Work on not stable modules are also still >>>>>>> opened >>>>>>> because such modules won't be visible by end users. Among works >>>>>>> already started and that are qualified to continue to push non bug fix >>>>>>> PR, >>>>>>> we may find: >>>>>>> >>>>>>> - work on advanced accountancy (double party) module to finish/make >>>>>>> stable changes done during development period, >>>>>>> >>>>>>> - new variant module >>>>>>> >>>>>>> - work on look and feel standardization >>>>>>> >>>>>>> - code to make online payment process standardized (this include >>>>>>> work on module "stripe"). >>>>>>> >>>>>>> - translation changes >>>>>>> >>>>>>> - changes required to allow package generations >>>>>>> >>>>>>> >>>>>>> *Please do not send new feature PR during this beta period, but take >>>>>>> time to test and debug the version 6.0 beta (currently into branch >>>>>>> develop*. >>>>>>> Dedicated branch for v6 will be created when version will be more >>>>>>> stabilized) >>>>>>> >>>>>>> Also, architecture, re-engineering, or best practice code >>>>>>> enhancements will be discarded during this period. Instead any help is >>>>>>> welcome to fix all opened bug: See https://github.com/Dolibar >>>>>>> r/dolibarr/issues >>>>>>> >>>>>>> More information on what a "freeze" mean: https://wiki.dolibarr.or >>>>>>> g/index.php/Category:RoadMap >>>>>>> >>>>>>> >>>>>>> Version 6.0 beta period should be shorter as usual. It has a very >>>>>>> good compatibility behavior with external modules, so you can already >>>>>>> check >>>>>>> your external modules are still working with this version, even if >>>>>>> freeze >>>>>>> is done in few days only. >>>>>>> >>>>>>> The Changelog into develop branch does not contains for the moment >>>>>>> list of new features, but you can read it to get information on what was >>>>>>> changed and may need attention of external developers or upgraders. >>>>>>> >>>>>>> >>>>>>> More information on what a "maintenance version" mean: >>>>>>> https://wiki.dolibarr.org/index.php/Category:RoadMap >>>>>>> >>>>>>> >>>>>>> Laurent Destailleur, aka Eldy >>>>>>> >>>>>>> ------------------------------------------------------------ >>>>>>> ------------------------ >>>>>>> Google+: https://plus.google.com/+LaurentDestailleur-Open-So >>>>>>> urce-Expert/ >>>>>>> Facebook: https://www.facebook.com/Destailleur.Laurent >>>>>>> Twitter: http://www.twitter.com/eldy10 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Dolibarr-dev mailing list >>>>>>> Dolibarr-dev@nongnu.org >>>>>>> https://lists.nongnu.org/mailman/listinfo/dolibarr-dev >>>>>>> >>>>>>> Thanks for the information Eldy, I was thinking why not use the wiki >>>>>> to make the ChangeLog , this is a good practice you can see in the >>>>>> Inkscape >>>>>> community. Something like this http://wiki.inkscape.org/wiki/ >>>>>> index.php/Release_notes >>>>>> >>>>>> >>>>>> Rgds >>>>>> Saxa >>>>>> >>>>>> _______________________________________________ >>>>>> Dolibarr-dev mailing list >>>>>> Dolibarr-dev@nongnu.org >>>>>> https://lists.nongnu.org/mailman/listinfo/dolibarr-dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> EMail: e...@destailleur.fr >>>>> Web: http://www.destailleur.fr >>>>> ------------------------------------------------------------ >>>>> ------------------------ >>>>> Google+: https://plus.google.com/+LaurentDestailleur-Open-So >>>>> urce-Expert/ >>>>> Facebook: https://www.facebook.com/Destailleur.Laurent >>>>> Twitter: http://www.twitter.com/eldy10 >>>>> ------------------------------------------------------------ >>>>> ------------------------ >>>>> * Dolibarr (Project leader): https://www.dolibarr.org (make a >>>>> donation for Dolibarr project via Paypal: cont...@destailleur.fr) >>>>> * AWStats (Author) : http://awstats.sourceforge.net (make a donation >>>>> for AWStats project via Paypal: cont...@destailleur.fr) >>>>> * AWBot (Author) : http://awbot.sourceforge.net >>>>> * CVSChangeLogBuilder (Author) : http://cvschangelogb.sourceforge.net >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dolibarr-dev mailing list >>>>> Dolibarr-dev@nongnu.org >>>>> https://lists.nongnu.org/mailman/listinfo/dolibarr-dev >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Dolibarr-dev mailing list >>> Dolibarr-dev@nongnu.org >>> https://lists.nongnu.org/mailman/listinfo/dolibarr-dev >>> >>> >> >> >> -- >> EMail: e...@destailleur.fr >> Web: http://www.destailleur.fr >> ------------------------------------------------------------ >> ------------------------ >> Google+: https://plus.google.com/+LaurentDestailleur-Open-Source-Expert/ >> Facebook: https://www.facebook.com/Destailleur.Laurent >> Twitter: http://www.twitter.com/eldy10 >> ------------------------------------------------------------ >> ------------------------ >> * Dolibarr (Project leader): https://www.dolibarr.org (make a donation >> for Dolibarr project via Paypal: cont...@destailleur.fr) >> * AWStats (Author) : http://awstats.sourceforge.net (make a donation for >> AWStats project via Paypal: cont...@destailleur.fr) >> * AWBot (Author) : http://awbot.sourceforge.net >> * CVSChangeLogBuilder (Author) : http://cvschangelogb.sourceforge.net >> >> >> >> _______________________________________________ >> Dolibarr-dev mailing list >> Dolibarr-dev@nongnu.org >> https://lists.nongnu.org/mailman/listinfo/dolibarr-dev >> >> > > _______________________________________________ > Dolibarr-dev mailing list > Dolibarr-dev@nongnu.org > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > > -- EMail: e...@destailleur.fr Web: http://www.destailleur.fr ------------------------------------------------------------------------------------ Google+: https://plus.google.com/+LaurentDestailleur-Open-Source-Expert/ Facebook: https://www.facebook.com/Destailleur.Laurent Twitter: http://www.twitter.com/eldy10 ------------------------------------------------------------------------------------ * Dolibarr (Project leader): https://www.dolibarr.org (make a donation for Dolibarr project via Paypal: cont...@destailleur.fr) * AWStats (Author) : http://awstats.sourceforge.net (make a donation for AWStats project via Paypal: cont...@destailleur.fr) * AWBot (Author) : http://awbot.sourceforge.net * CVSChangeLogBuilder (Author) : http://cvschangelogb.sourceforge.net
_______________________________________________ Dolibarr-dev mailing list Dolibarr-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
