[Vtigercrm-developers] Roadmap 6.5 and 7

Simone Travaglini simonetravaglini at gmail.com
Wed May 4 10:30:14 GMT 2016


Prasad, I think Preexo have all the reason to ask a deep detailed roadmap.
We really need to plan our work for the future.

2016-05-04 11:35 GMT+02:00 Preexo <preexo at googlemail.com>:

> Dear Prasad,
>
> Thank you for your input and participation in this topic. I appreciate it
> very much and I think vtiger should more often take a leading role in this
> kind of discussions, I am sure it would make everyone feel more relaxed
> about the future of vtiger open source. Your answer with the roadmap is a
> great start!
>
> But... you summarized a bit too much, I am missing some important deatails.
> I understand that everyone is busy and you are also fed up with the open
> source community complaining the whole time, but for us it's only possible
> to plan and contribute further if we are being involved with real details
> about the future.
> What defines "less core framework changes" and what features from the on
> demand are on the plan for open source?
> Which features are definitely not going to make it into open source,
> because
> why?
> How much core changes will be merged into vtiger if contributed by us? What
> about library updates across the whole product, what about framework
> replacements across the whole project? What about new features?
>
> It needs more, please... Please don't tell me you don't have more...
> Because
> this is not much since 6.4 and it just gives us the impression you made the
> open source project a weekend hobby for bad weather days.
>
> I really want to contribute, but every time I am scared I just waste my
> time. For me personally it would be a good start if I got some comments on
> !25 (http://code.vtiger.com/vtiger/vtigercrm/merge_requests/25) for
> example... I was only scratching the surface there and had like many more
> plans for replacement and improvements, but those tiny tiny changes already
> ended in a black whole, what kind of impression does that should give me I
> ask you?
>
> Best regards
>
>
>
> Prasad-14 wrote
> > I have summarized the targets that is on the table:
> >
> > *6.5 Release Goal *(Q2 / early Q3 2016)
> >
> >    - More focused on bug-fixes, merge-requests and minor features.
> >    - Features that demands less core-framework changes will be pulled
> from
> >    Ondemand.
> >
> > *7.0 Release Goal *(ETA - tentative 2017)
> >
> >    - Vtiger 7 Layout
> >    - Enabling Multi-layout support need more community evaluation and
> >       feedback.
> >       - Approved Ondemand features + core framework changes that are
> >    compatible to Opensource.
> >
> > What features will be in 7.0?
> >
> >    - To be discussed post 6.5.0 release.
> >    - You are welcome to file requests on code.vtiger.com.
> >
> > *Would there be 6.6 instead of 7.0?*
> >
> >    - Possible.
> >
> > Regards,
> > Prasad
> > Vtiger Team
> >
> > --
> > FB <http://www.facebook.com/vtiger> I Twit
> > <http://twitter.com/vtigercrm> I
> > LIn <https://www.linkedin.com/company/1270573?trk=tyah> I Blog
> > <https://blogs.vtiger.com> I Website <
> https://www.vtiger.com/>
> >
> > On Fri, Apr 29, 2016 at 4:07 PM, Manuel Fernando <
>
> > ptdesigner@
>
> > >
> > wrote:
> >
> >> About create a new fork, speaking for myself, is not necessary because
> >> the
> >> fork is here.
> >>
> >> And even if someone (individual or group) create a new fork some
> problems
> >> still there because the main problem now is not defined what must be
> >> done.
> >> New features, just fixes or improvements etc etc.
> >> A new fork, depending of witch people would drive that fork will always
> >> have a more specific way of thinking for their business cases or their
> >> knowledge areas.
> >>
> >> We have now more tools than ever to contribute.
> >> For that, we should open a discussion like a webform for community put
> >> their needs and vote for improvements or new functionalities so we have
> a
> >> better understanding of what people is looking for.
> >> Vtiger team may have some data collected in the past years when vtiger
> is
> >> installed (selecting the business case).
> >> Community can have some similar if some "vote data" is collected.
> >>
> >> Maybe we don’t need Vtiger 7 “depending of what is bringing for
> >> community”
> >>
> >> About new features, sometimes they try to fill CRM’s in a way that gets
> >> massive and software looses his direction when try to include everything
> >> and that’s why extensions are great.
> >>
> >> Best Regards.
> >>
> >> Manuel
> >>
> >> > No dia 29/04/2016, às 09:50, Alan Bell <
>
> > alan.bell at .co
>
> > >
> >> escreveu:
> >> >
> >> > On 29/04/16 07:02, Preexo wrote:
> >> >> Alan Bell-6 wrote
> >> >>> >but I got a heap of merges accepted on
> >> >>> >code.vtiger.com over the past few days, so I am not too distressed
> >> at
> >> >>> >the moment.
> >> >> I just saw that on code.vtiger.com and it made my day! I will
> commit a
> >> few
> >> >> more things in the next few weeks as well and hope for the best,
> >> > worth noting for the vtiger folk that the best way to motivate people
> >> to
> >> contribute more stuff is to review issues and action merges in a
> >> reasonable
> >> timescale, (accepting or rejecting is fine, leaving it is not so good)
> if
> >> I
> >> have 10 outstanding merge requests sitting there with no feedback I am
> >> not
> >> going to do much more, but if they get merged then I am going to try and
> >> fill up the queue again, and if they get rejected I am going to fix them
> >> and try again.
> >> >
> >> > Sometimes what is needed on an issue is a little discussion about the
> >> right way to fix it before someone can go ahead and do the work and
> >> propose
> >> a merge - especially for situations like this one:
> >> http://code.vtiger.com/vtiger/vtigercrm/issues/184 where I want a
> feature
> >> I know is in the on-demand and I can implement in the open source, but
> >> that
> >> is a bit of a redundant effort (actually I already did it for a customer
> >> so
> >> not too much extra effort) and I think it just makes merging harder in
> >> the
> >> future.
> >> >
> >> > Alan.
> >> > _______________________________________________
> >> > http://www.vtiger.com/
> >>
> >>
> >> _______________________________________________
> >> http://www.vtiger.com/
> >
> > _______________________________________________
> > http://www.vtiger.com/
>
>
>
>
>
> --
> View this message in context:
> http://vtiger-crm.2324883.n4.nabble.com/Vtigercrm-developers-Roadmap-6-5-and-7-tp18757p18967.html
> Sent from the vtigercrm-developers mailing list archive at Nabble.com.
>
> _______________________________________________
> http://www.vtiger.com/
>



-- 
Simone Travaglini
328 5499846
Linkedin: Simone Travaglini


Rispetta l'ambiente: non stampare questa mail se non ti è veramente
necessario!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20160504/c8fd8c1d/attachment-0001.html>


More information about the vtigercrm-developers mailing list