<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DE" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I agree, it’s a systemic problem. But the bugtracking is only part of the problem. Vtiger of course is open-source – but it’s not a community project.
Perhaps I’m wrong, but I believe only vtiger employees have write access to the source code. Why don’t you give some “special” community members also the right to review patches and integrate them? “Community” means, that members with enough reputation get
the right to decide more! Today when you have the “not enough time”-problem you have to hire new employees. But I’m sure there are many people out there who would like to help you for free – you just ignore them!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Today vtiger is a company releasing its own software as open source when it’s finished. But it does not respect the original open-source-idea of
working together as a community to make things better! If you solved that problem, vtiger could be developed much faster and quality would get better!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Christian<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Von:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> vtigercrm-developers-bounces@lists.vtigercrm.com [mailto:vtigercrm-developers-bounces@lists.vtigercrm.com]
<b>Im Auftrag von </b>Sreenivas Kanumuru<br>
<b>Gesendet:</b> Donnerstag, 7. Februar 2013 06:41<br>
<b>An:</b> vtigercrm-developers@lists.vtigercrm.com<br>
<b>Betreff:</b> Re: [Vtigercrm-developers] Cooperation<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Adam,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">You are right. it is a systemic problem across many open source projects. We strive to do better. We have more resources in the core team now. Our QA team is actively reviewing the bugs submitted
<a href="http://trac.vtiger.com/cgi-bin/trac.cgi/report/37">here</a>. Before the Vtiger 6 final code is released, we will be going through all the Vtiger 6 patch submissions. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Sreenivas<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal">--<br>
Sreenivas Kanumuru<br>
vtiger Team<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Direct: +91 96323-55656<br>
Skype: skanumuru<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<b>Connect with us on: </b><a href="http://twitter.com/#%21/vtigercrm" target="_blank">Twitter</a>
<b>I</b> <a href="http://www.facebook.com/pages/vtiger/226866697333578?sk=wall" target="_blank">
Facebook</a> <b>I</b> <a href="http://blog.vtiger.com/" target="_blank">Blog</a><b> I</b>
<a href="http://wiki.vtiger.com/index.php/Main_Page" target="_blank">Wiki</a> <b>I
</b><a href="http://forums.vtiger.com/" target="_blank">Forums </a><b>I</b> <a href="http://vtiger.com/" target="_blank">Website</a><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Feb 7, 2013 at 1:24 AM, Adam Heinz <<a href="mailto:amh@metricwise.net" target="_blank">amh@metricwise.net</a>> wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">On Wed, Feb 6, 2013 at 2:13 PM, Sreenivas Kanumuru <<a href="mailto:svk@vtiger.com" target="_blank">svk@vtiger.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">We try to integrate as many patches as possible. 5.3 and 5.4 versions included some patches that we received from community members. But, i agree that we did not get back to all the developers who submitted patches. W<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">e
did not have sufficient time to monitor and close lower priority issues. </span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">I think this is a systemic problem. I'm a big believer that a bug tracking system is a general indicator of the overall health of a development team. Generally speaking, I lean towards agile software development, so my personal litmus
tests reflect that:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">1. There should be no open bugs in old milestones. They should either be fixed by development and verified by QA, or they should be moved forward by project management. If possible, old milestones should be locked so that new bugs can't
be entered against them.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">2. New bugs coming in should be assigned to either the current hotfix branch, the current development branch, the subsequent development branch, or the heap. When a development branch closes, the heap is reviewed, pulling bugs into the
development branch, potentially as WONTFIX, INVALID or WORKSFORME.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">There is nothing wrong with reviewing open source contributions and throwing them out. You can use a low level QA person to triage bugs as not reproducible. Nobody is going to get offended if a junior member of your team starts a dialogue
with them, asking for help to reproduce a bug. That said, I find it insulting that you claim not to have the few minutes it takes to review what may have taken a developer hours or days to build. It takes a lot less time to review a bug than it does to fix
it. When I manage other developers, I mostly get the hell out of their way, keep their slop bucket full of bugs, and review EVERY SINGLE LINE OF CODE THEY SUBMIT. It takes me no more than thirty minutes to review an entire eight hour day of another developer's
work and svn merge the change from their development branch into a testing branch.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
_______________________________________________<br>
<a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>