[Vtigercrm-developers] Happy New Year

[Alan Lord]

On 07/01/16 17:39, Sreenivas Kanumuru wrote:
> Happy New year!
>
> We are excited about the developments coming to Vtiger open source
> edition. While it will not have all the features of our cloud edition,
> it will continue to draw many of the enhancements that we roll out to
> the cloud edition.
>
> These are the priorities for us in 2016.
>
> 1. To facilitate community contributions and collaboration, we recently
> moved to git (code.vtiger.com <http://code.vtiger.com>). We will be
> reviewing the contributions and respond promptly.

Good.

> 2. Promote extensions development and strengthen marketplace. While Open
> source doesn't have all cloud edition features, through marketplace
> customers have access to a rich set of functionality.

OK. But we - all of us - need to come up with some way to handle support 
for Marketplace extensions that run on On-Demand. The problem with 
GoeTools and v7 is a right PITA frankly. I have had several emails about 
it from users but it is completely out of my control... (Just like the 
Outlook plugin). Please spend some time deciding what you really want... 
If you want 3rd party extensions available to On-Demand then you must 
provide some "sandbox" type developer access to the system for testing 
and support. As I suggested one possible approach is to strengthen your 
partner programme and provide access by means of an NDA or something 
similar (if you are really that paranoid about cannibalisation)...

> 3. Roadmap - We'll release 6.5 by end of Q1, and Vtiger 7.0 in Q3.

Great but what does that mean? What's in 6.5? What will be in 7.0?

> As to the question of making Vtiger On Demand code open source, the
> answer is that we do not foresee doing that. On Demand service is a
> collection of applications that are running on different servers, CRM
> being one of them. There is Global search that is driven through Solr.
> Then there is Email campaigns service that we run through a network of
> servers. And there is a Email Archival and Response service for
> converting emails into tickets, ..etc. In addition, Notifications, and
> some of the connectors such as Quickbooks, and Zapier require
> intermediate services.

That makes sense to a large extent but please see above regarding item 2.