Doug, <div><br></div><div>I have spawn new thread for discussing your feature - as its unrelated to this thread's main focus.</div><div><br></div><div>Regards,</div><div>Prasad<br>
<br><div class="gmail_quote">On Sat, Aug 25, 2012 at 12:39 AM, Doug <span dir="ltr"><<a href="mailto:sailsfast@gmail.com" target="_blank">sailsfast@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
My biggest concern at this point, and I haven't been following development closely this summer. Lies in the Calendar function of vtiger..<br><br>The lack of the ability to capture the precise length of phone calls is a large barrier to it's adoption in most sales driven businesses. With the default 5 minute increments it is impossible to measure the effectiveness of call scripts, patterns, and behaviors of individual sales or customer service reps. <br>
<br>We would be much more well served with a "NOW" button that would automatically fill in the correct local time including hours, minutes and <u>seconds</u> into the appropriate fields and an automatic calculation of call duration.<br>
<br>And as well perhaps an option to manually fill in the hours and minutes into future appointment or call times.<br><br>Nearly all of my clients need to be able to differentiate between a rep that is spending on average 7minutes 20 seconds on calls from a rep that is spending 8 minutes 35 seconds on calls in a particular week or month for instance. Even if we are tracking only minutes there is still a big difference between the 7 minutes and 9 minutes that might otherwise look like in rounded off minutes. 1 minute and 15 seconds looks like 2 minutes. A huge discrepancy.<br>
<br>5 minute increments are impossible.<br>
<br><br><div class="gmail_quote"><div><div class="h5">On Fri, Aug 24, 2012 at 2:36 PM, Sreenivas Kanumuru <span dir="ltr"><<a href="mailto:svk@vtiger.com" target="_blank">svk@vtiger.com</a>></span> wrote:<br></div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div>Adam, Joe,</div><div><br></div><div>As developers, i am sure you both are aware of the perils of putting out half baked code. We are certainly looking forward to your contributions and feel the new client framework will spur development of more such extensions. The alpha release that we are going to publish in a couple of weeks will still have some incomplete areas. We appreciate your patience as we work to deliver a solid vtiger 6 release (most likely in November).</div>
<div><br></div><div>Regards,</div><div>Sreenivas</div><div><br><br><div class="gmail_quote">On Fri, Aug 24, 2012 at 11:47 PM, Prasad <span dir="ltr"><<a href="mailto:prasad@vtiger.com" target="_blank">prasad@vtiger.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>I wanted to clarify the perception difference that is being discussed on this thread. Please don't read me wrong - I'm certainly young compared to your expertise.</div>
<div><br></div><div>* Ondemand dev-team set the goals (every month) and focus</div>
<div>more on working on issues / features that can be rolled in the target cycle.</div><div><br></div><div>* Opensource dev-team set the goals in longer cycles as they collobrate</div><div>with Ondemand team changes + support customers bug-fixes + </div>
<div>community contributions + customizations + extensions.</div><div><br></div><div>Opensource product features match the Ondemand except they are few customization enabled for adapting the our billing system and service is enabled with round-the-clock support & IT team.</div>
<div><br></div><div>--</div><div>The practise of maintaing staging repository (instead of "hidden branch") has been their ever before ondemand started, the primary purpose was to eliminate the fear from young developers while committing the untested / validated code (and avoid loosing the changes!). The reviewed / validated code will be pushed to <a href="http://trac.vtiger.com" target="_blank">trac.vtiger.com</a> branches which need additional time.</div>
<div><br></div><div>--</div><div>vtiger6 development has been challenging with the agenda to </div><div>get the earlier version with least disruption to existing backend API</div><div>but yet enabled flexibity to provide adaptable UI (front end).</div>
<div><br></div><div>This had certainly raised the bars on dev-team who took few hard-bytes</div><div>refactoring the code very often and now settled with the better model.</div><div><br></div><div>Translation design / Module packages were the concepts that was </div>
<div>discussed few weeks back and is in process of implementation.</div><div><br></div><div>Which was the major reason to postpone commit to <a href="http://trac.vtiger.com" target="_blank">trac.vtiger.com</a> branch.</div>
<div><br></div>
<div>I appreciate your collaboration and look forward for greater assistance.</div><div><br></div><div>Regards,</div><div>Prasad</div><div>vtiger Team</div><div><div><div><br></div>On Friday, August 24, 2012, Joe Bordes <<a href="mailto:joe@tsolucio.com" target="_blank">joe@tsolucio.com</a>> wrote:<br>
> I couldn't have said it better :-)<br>><br>> Thanks<br>><br>><br>> On 24/08/12 14:51, Adam Heinz wrote:<br>>> On Fri, Aug 24, 2012 at 8:13 AM, Stefan Warnat <<a href="mailto:ich@stefanwarnat.de" target="_blank">ich@stefanwarnat.de</a>> wrote:<br>
>>> I think that it's no problem to wait, because vtiger is Open Source! It's<br>>>> not like commercial Software, you have pay for the functions.<br>>>> Nobody should expect any changes and be thankfull for every update you<br>
>>> become for FREE.<br>>> I don't think waiting is the problem. Joe's complaint reads to me<br>>> like, "Hey guys, why won't you let me help you sooner (by contributing<br>>> code and translations)!"<br>
>><br>>> So long as primary development is done in a hidden branch, community<br>>> contribution will always lag several months behind. My theory is that<br>>> they are trying to add value to their On Demand offering by delaying<br>
>> features into trunk, which is unfortunate for the development<br>>> community. I personally believe that that the contributions of<br>>> community developers already exceed that value. Even if vtiger<br>
>> doesn't want to open up the On Demand branch to the world, at least<br>>> give your translators and long-time community developers early access!<br>>> Joe has been a member of the community since 2006!<br>
>> _______________________________________________<br>>> <a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br>><br>> _______________________________________________<br>> <a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br>
>
</div></div><br>_______________________________________________<br>
<a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br></blockquote></div><br></div>
<br></div></div>_______________________________________________<br>
<a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br></blockquote></div><br>
<br>_______________________________________________<br>
<a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br></blockquote></div><br></div>