[Vtigercrm-developers] Community Help: Set roadmap for 7.5.0

[S T Prasad]

Great going so far.

I am a less than frequent contributor on this list, and I am motivated by
the recent discussions which have taken a very interesting turn in the last
few days.

At the outset, there is a perception, among those who make up the community
so to speak, that there is less than expected responsiveness by the Vtiger
team towards community concerns. A few, like, roadmap clarity, merge
requests pending, market place reviews pending, contribution
acknowledgement etc etc. Yes, the recent acclaim of contributors to 740 was
a significant departure from earlier release announcements.

I take the view that Vtiger, will, must and can do only so much. They are a
business. There are tradeoffs to be made, and those who are not direct
stakeholders, cannot make the rules. It is the bounden responsibility of
the Vtiger management to maximize their stakeholder returns.

Who are we? What is our interest, what is our stake? More after a bit. Lets
reserve the term WE, We, we for now.

If we are to start a branch on code.vtiger.com with community driven MRs as
opposed to Vtiger driven MRs, then we should have 740ce or 750ce branches.
This would keep the community motivation higher as the self review process
would be better. I don't know if the Gitlab access privileges for a
specific branch could be delegated to some of the leading contributors of
this developer-lists. Unless this step happens, we continue to be dependent
on, I desist saying at the mercy of, on Vtiger's ability to focus on the
community's priorities, which necessarily will conflict with their road map.

If one takes a cold view, apart from the individual hotlists, there are 466
issues on the Git, without milestones. 750 has 4 and 800 has 3.

Let's make a beginning, share out the division of labour like Angelo
Paglialonga did and lets get started. We have some 150 days left.

Now to the promised definition of WE.

We are those of us who seek to benefit from Vtiger, directly or indirectly.
Some are partners for many years, some have extension contributions and
many other service offerings where we are able to service a larger base of
users, who are happy with Vtiger but prefer an own instance as opposed to
the On Demand offering.

Some of us are here as those who have earned their daily bread from Vtiger.
Some more, some less. I have said this before, and for the last 10 years my
small enterprise has kept a 25 member team growing from 2, solely on
Vtiger.

So if WE speak, we are not the real community. There is a real community
out there, whose voice is not heard here, on this list. They report issues,
everyday, inexperience, some good, some stupid, some use it as a quasi
marketplace.

So let's WE get our act together, make the 466 to as near zero with
controlled improvement to show to ourselves what what really is lacking
here.

There are more than 466, believe me.

With best regards,

S.T.Prasad (Skype: stprasad at stprasad.com)



On Tue, Aug 10, 2021 at 5:57 PM Angelo Paglialonga <
info at angelopaglialonga.com> wrote:

> Hi Nilay here are my favorites!
> #1596 <https://code.vtiger.com/vtiger/vtigercrm/issues/1596>
> issue #1639
> <https://code.vtiger.com/vtiger/vtigercrm/issues/1639#note_11428>
> issue #1572
> <https://code.vtiger.com/vtiger/vtigercrm/issues/1572#note_10905>
>
> _______________
>
> Angelo Paglialonga
> Consulente per soluzioni CRM ad alto ROI.
>
> Telefono: 3386077866
> Skype: angelo.paglialonga
> Web: https://www.angelopaglialonga.com
>
>
>
> Il giorno 10 ago 2021, alle ore 13:44, nilay khatri <
> nilay.spartan at gmail.com> ha scritto:
>
> Angelo, thanks. Which one of them would you be interested in picking up
> from that list?
>
> On Tue, Aug 10, 2021 at 5:08 PM Angelo Paglialonga <
> info at angelopaglialonga.com> wrote:
>
>> Very good,
>> I think we can do better than just fixing things.
>>
>> Could we make a list to choose which enhancements we want to develop?
>>
>> I’ve made a list of them, feel free to add your favorite ones:
>>
>> issue #1633
>> <https://code.vtiger.com/vtiger/vtigercrm/issues/1633#note_11358>
>> issue #1639
>> <https://code.vtiger.com/vtiger/vtigercrm/issues/1639#note_11428>
>> issue #1572
>> <https://code.vtiger.com/vtiger/vtigercrm/issues/1572#note_10905>
>> #1596 <https://code.vtiger.com/vtiger/vtigercrm/issues/1596>
>> #1593 <https://code.vtiger.com/vtiger/vtigercrm/issues/1593>
>> #1592 <https://code.vtiger.com/vtiger/vtigercrm/issues/1592>
>> #1589 <https://code.vtiger.com/vtiger/vtigercrm/issues/1589>
>> #1588 <https://code.vtiger.com/vtiger/vtigercrm/issues/1588>
>> #1586 <https://code.vtiger.com/vtiger/vtigercrm/issues/1586>
>> #1585 <https://code.vtiger.com/vtiger/vtigercrm/issues/1585>
>>
>>
>>
>> _______________
>>
>> Angelo Paglialonga
>> Consulente per soluzioni CRM ad alto ROI.
>>
>> Telefono: 3386077866
>> Skype: angelo.paglialonga
>> Web: https://www.angelopaglialonga.com
>>
>>
>>
>> Il giorno 10 ago 2021, alle ore 12:39, nilay khatri <
>> nilay.spartan at gmail.com> ha scritto:
>>
>> Hi All,
>>
>> Hope every one is keeping safe and well.
>>
>> So as mentioned by Prasad from Vtiger's team, the extencations for next
>> version 7.5.0 are to fix bugs and it other contributions from the community.
>>
>> So as a community it would be great to set a roadmap ourselves, take
>> responsibilities for tasks/issues that interest you and take the product
>> ahead.
>>
>> The next version release is targeted for Jan 2022, giving us 4 months of
>> time.
>>
>> My suggestion would be to split this into 3 + 1, keeping 3 months for
>> development contributions and last 1 month towards bug fixes and testing.
>>
>> Given the short period of time, it would be wise to focus towards open
>> issues which are bugs, rather than introducing any new feature or trying to
>> enhance the framework. As the framework upgrades are planned for next major
>> version.
>>
>>
>> Ideally we can start a poll and which ever issues gets the highest vote
>> can be prioritized. But many of us might be already working on the open
>> issues or already have a fix, so let us first make a list of Contributors
>> and respective issues that they are interested in. Also, let's share the
>> feedback in the next 10 days which is on or before 20th Aug.
>>
>> Based on this input then we can finalize the distribution of issues among
>> the contributors and take it forward.
>>
>> Suggestions open, I am just initiating the thought.
>>
>>
>> _______________________________________________
>> http://www.vtiger.com/
>>
>>
>> _______________________________________________
>> http://www.vtiger.com/
>
> _______________________________________________
> http://www.vtiger.com/
>
>
> _______________________________________________
> http://www.vtiger.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20210810/24606336/attachment.html>