This is the page we should be using to keep track of everything to be done for 4.2.5: <a href="http://vtiger.fosslabs.com/cgi-bin/trac.cgi/query?status=new&status=assigned&status=reopened&milestone=4.2.5">http://vtiger.fosslabs.com/cgi-bin/trac.cgi/query?status=new&status=assigned&status=reopened&milestone=4.2.5
</a><br><br>It would be nice to have a 4.2.6 (or 4.2 future) milestone to keep the list realistic though. Fell free to organize, add and prioritize the things in that list.<br><br>On the same note you here is the page of everything already accomplished for
4.2.5:<br><a href="http://vtiger.fosslabs.com/cgi-bin/trac.cgi/query?status=closed&milestone=4.2.5">http://vtiger.fosslabs.com/cgi-bin/trac.cgi/query?status=closed&milestone=4.2.5</a><br><br><div><span class="gmail_quote">
On 7/21/06, <b class="gmail_sendername">Richie</b> <<a href="mailto:richie@vtiger.com">richie@vtiger.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div>Matjaz, you already would have got the access mail for the trac.
<br>About the TRAC Wiki, Matt will do the needful.
<br>
<br>
<br>Let us know if you need anything else.
<br>
<br>Richie<br><br><br><br><br>---- <a href="mailto:Matjaz.Slak@atol.si" title="mailto:Matjaz.Slak@atol.si" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Matjaz.Slak@atol.si</a><<a href="mailto:Matjaz.Slak@atol.si" title="mailto:Matjaz.Slak@atol.si" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Matjaz.Slak@atol.si</a>> wrote ---- </div><div><span class="e" id="q_10c916fc9f7cbd35_1"><br><br><blockquote style="border-left: 2px solid rgb(0, 0, 255); padding: 6px;">
<br><font face="sans-serif" size="2">Hi!<br>
<br>
Thank you!</font>
<br>
<br><font face="sans-serif" size="2">I hope I'll be able to finish up some
of my other tasks within a week or so and then I'll start posting ideas
about what to work on here.</font>
<br>
<br><font face="sans-serif" size="2"><b>If anybody has any general wishes
and/or requests about which item(s) you would like to have fixed in 4.2.x,
post them here.</b> By this I mean areas perceived by vTiger users. Try
to fit them in the following categories:</font>
<ul>
<li><font face="sans-serif" size="2">debugging (fixing user-perceived functions
that either don't work at all and/or work incorrectly)</font>
</li><li><font face="sans-serif" size="2">improving usability (based on feedback
from users)</font>
</li><li><font face="sans-serif" size="2">improving security (let us know of possible
security holes)</font>
</li><li><font face="sans-serif" size="2">multilanguage support (simply get rid
of any and all hard-coded strings)</font>
</li><li><font face="sans-serif" size="2">localization support (number format,
date format, currency support etc - per user or at least per-system)</font>
</li><li><font face="sans-serif" size="2">other (we can create aditional categories
if the need arises)</font></li></ul>
<br><font face="sans-serif" size="2">For example:</font>
<ul>
<li><font face="sans-serif" size="2">Private Custom Views - allow for a custom
view to be marked as private and only be visible to the user that created
it (usability)</font>
</li><li><font face="sans-serif" size="2">All View columns sortable - allow a
user to click on any column and sort it (usability)</font>
</li><li><font face="sans-serif" size="2">Repeating calls/meetings - don't work
at all? (debugging)</font>
</li><li><font face="sans-serif" size="2">etc...</font></li></ul>
<br><font face="sans-serif" size="2">I'll be collecting them and posting
them somewhere - the TRAC Wiki comes to mind as an appropriate place. We
can the priorithise them and look into required work - and then create
tickets for developers (us, again :) to work on.</font>
<br>
<br><font face="sans-serif" size="2"><b>Richie, Jeff, Matt and/or others:</b>
would it me possible for me to have acces to post some content to the TRAC
Wiki? I would create a document like "vTiger 4.2.x to-do area"
that would include these items we wish to work on - and specific goals
for them. Tickets would then be created based on these. This document would
represent the general guideline.<br>
<br>
Matjaz Slak<br>
<a href="mailto:matjaz.slak@atol.si" title="mailto:matjaz.slak@atol.si" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">matjaz.slak@atol.si</a><br>
<br>
Atol d.o.o. | <a href="http://www.atol.si" title="http://www.atol.si" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.atol.si</a> | tel. +386 1
510 15 30</font>
<br>
<br>
<br>
<table width="100%">
<tbody><tr valign="top">
<td width="40%"><font face="sans-serif" size="1"><b>Nolan Andres <<a href="mailto:nolan@peaceworks.ca" title="mailto:nolan@peaceworks.ca" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">nolan@peaceworks.ca
</a>></b>
</font>
<br><font face="sans-serif" size="1">Sent by: <a href="mailto:vtigercrm-developers-bounces@lists.vtigercrm.com" title="mailto:vtigercrm-developers-bounces@lists.vtigercrm.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
vtigercrm-developers-bounces@lists.vtigercrm.com</a></font>
<p><font face="sans-serif" size="1">20.07.2006 19:50</font>
<table border="1">
<tbody><tr valign="top">
<td bgcolor="white">
<div align="center"><font face="sans-serif" size="1">Please respond to<br>
<a href="mailto:vtigercrm-developers@lists.vtigercrm.com" title="mailto:vtigercrm-developers@lists.vtigercrm.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">vtigercrm-developers@lists.vtigercrm.com
</a></font></div></td></tr></tbody></table>
<br>
</p></td><td width="59%">
<table width="100%">
<tbody><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">To</font></div>
</td><td><font face="sans-serif" size="1"><a href="mailto:vtigercrm-developers@lists.vtigercrm.com" title="mailto:vtigercrm-developers@lists.vtigercrm.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
vtigercrm-developers@lists.vtigercrm.com</a></font>
</td></tr><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">cc</font></div>
</td><td>
<br></td></tr><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">Subject</font></div>
</td><td><font face="sans-serif" size="1">Re: [Vtigercrm-developers] An Impassioned
Plea froma
VTiger Integrator</font></td></tr></tbody></table>
<br>
<table>
<tbody><tr valign="top">
<td>
<br></td><td><br></td></tr></tbody></table>
<br></td></tr></tbody></table>
<br>
<br>
<br><font size="2"><tt>Hi all,<br>
<br>
Although I'd really love to be able to just contribute features without
<br>
having to re-integrate (into v5,) I agree with priorities and I'll <br>
second the addition of security to the list. Security through obscurity
<br>
is bad enough, but with open source projects, it simply becomes security
<br>
through ignorance. I certainly wouldn't trust vTiger's security in an <br>
environment where the data is actually confidential and a malicious or
<br>
competitive party would stand to gain by accessing it illicitly.<br>
<br>
I don't have the availability to co-ordinate things, but you can count
<br>
on me for some quantity of bug-fixes, security patches, etc.<br>
<br>
peace,<br>
nokes<br>
<br>
GIRONNAY Thibault wrote:<br>
> Hi all,<br>
> <br>
> <br>
> <br>
> Matjaz I'll be with you and your team in your enterprise, I agree
with <br>
> your priorities and have one another to add : the security. The <br>
> organisation sharing privileges for example is indeed totally an <br>
> illusion. It's too easy too change those settings while not being
admin <br>
> or to see all records even if the privileges are private. I think
this <br>
> is very harmful to offer such buggy features and can discredit Vtiger
<br>
> for the people who have interests in security.<br>
> <br>
> <br>
> <br>
> Hope we'll have others hands up<br>
> <br>
> <br>
> <br>
> cabugs<br>
> <br>
> <br>
> <br>
> ------------------------------------------------------------------------<br>
> <br>
> *De :* <a href="mailto:vtigercrm-developers-bounces@lists.vtigercrm.com" title="mailto:vtigercrm-developers-bounces@lists.vtigercrm.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">vtigercrm-developers-bounces@lists.vtigercrm.com
</a> <br>
> [mailto:<a href="mailto:vtigercrm-developers-bounces@lists.vtigercrm.com" title="mailto:vtigercrm-developers-bounces@lists.vtigercrm.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">vtigercrm-developers-bounces@lists.vtigercrm.com
</a>] *De la part
<br>
> de* <a href="mailto:Matjaz.Slak@atol.si" title="mailto:Matjaz.Slak@atol.si" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Matjaz.Slak@atol.si</a><br>
> *Envoyé :* mercredi 19 juillet 2006 16:46<br>
> *À :* <a href="mailto:vtigercrm-developers@lists.vtigercrm.com" title="mailto:vtigercrm-developers@lists.vtigercrm.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">vtigercrm-developers@lists.vtigercrm.com
</a><br>
> *Objet :* Re: [Vtigercrm-developers] An Impassioned Plea froma VTiger
<br>
> Integrator<br>
> <br>
> <br>
> <br>
> <br>
> Hi Richie and the rest of the team!<br>
> <br>
> You address me correctly, Matjaz is my name :)<br>
> <br>
> <br>
> As I belive the 4.2.x stream is the current "production"
vTiger <br>
> environment for most of the users, my primary goal would be to focus
on:<br>
> <br>
> * debugging (fixing parts that either don't work at
all and/or work<br>
> incorrectly)<br>
> * improving usability (based on feedback from users)<br>
> <br>
> <br>
> I would also like to try and get the following not-quite-features,
maybe <br>
> bugs? implemented/fixed:<br>
> <br>
> * multilanguage support (simply get rid of any and all
hard-coded<br>
> strings)<br>
> * full per user or at least per-system localization
support (number<br>
> format, date format, currency support etc)<br>
> <br>
> <br>
> These two last items are - in my opinion - somewhere between debugging
<br>
> and new features. vTiger is already supposed to support multiple <br>
> languages, however this support is not well implemented. The same
can be <br>
> said for localization - vTiger is supposed to be able to support <br>
> per-user date format, but again there are areas where the implementation
<br>
> is not as good as it could be.<br>
> <br>
> Also, based on my researches into existing vTiger deployments, I see
<br>
> there are a lot of non-english users, but they probably are using
forked <br>
> code, as due to these two issues they cannot use the "official"
4.2.x <br>
> stream code. I would like to get these users back on the team, and
I <br>
> know they might return only if we provide them with a 100% localisable
<br>
> product. This will enable them to post the patches they make back
to the <br>
> community or at least give them an opportunity to work with us on
<br>
> resolving them.<br>
> <br>
> I would try and keep us on this track, rather than go try implement
new <br>
> features and make large changes to UI - the place for these is v5.<br>
> <br>
> <br>
> To achieve this, I would first gather any and all contributions <br>
> currently lying around (in the forum, as provided by other people
here <br>
> etc.) - matching the categories above - and start the process of getting
<br>
> them in the code. *I would like to see a show of hands* from people
that <br>
> would be prepared to devote some time to debugging/updating tthese
<br>
> contributions - as some might need an update. I know me and my <br>
> colleagues in our company will.<br>
> <br>
> If all goes well, we could try and implement a regular timeline (say
<br>
> every month) when we would be releasing point versions. If I get at
<br>
> least two or three people to help, I guess we could have our first
<br>
> result (4.2.5 I guess) in two months.<br>
> <br>
> I think there will be people using the 4.2.x stream for at least a
year <br>
> after v5 is released, and that if we as a team show them we are <br>
> supporting them, than they will upgrade to v5 -> if we don't they
might <br>
> start looking elsewhere.<br>
> <br>
> <br>
> *Thoughts, anyone?*<br>
> <br>
> <br>
> Matjaz Slak<br>
> <a href="mailto:matjaz.slak@atol.si" title="mailto:matjaz.slak@atol.si" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">matjaz.slak@atol.si</a><br>
> <br>
> Atol d.o.o. | <a href="http://www.atol.si" title="http://www.atol.si" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.atol.si</a> | tel. +386
1 510 15 30<br>
> <br>
> *Richie <<a href="mailto:richie@vtiger.com" title="mailto:richie@vtiger.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">richie@vtiger.com</a>>*<br>
> Sent by: <a href="mailto:vtigercrm-developers-bounces@lists.vtigercrm.com" title="mailto:vtigercrm-developers-bounces@lists.vtigercrm.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">vtigercrm-developers-bounces@lists.vtigercrm.com
</a><br>
> <br>
> 17.07.2006 16:57<br>
> <br>
> Please respond to<br>
> <a href="mailto:vtigercrm-developers@lists.vtigercrm.com" title="mailto:vtigercrm-developers@lists.vtigercrm.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">vtigercrm-developers@lists.vtigercrm.com
</a><br>
> <br>
> <br>
> <br>
> To<br>
> <br>
> <br>
> <br>
> <a href="mailto:vtigercrm-developers@lists.vtigercrm.com" title="mailto:vtigercrm-developers@lists.vtigercrm.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">vtigercrm-developers@lists.vtigercrm.com
</a><br>
> <br>
> cc<br>
> <br>
> <br>
> <br>
> <a href="mailto:vtigercrm-developers@lists.vtigercrm.com" title="mailto:vtigercrm-developers@lists.vtigercrm.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">vtigercrm-developers@lists.vtigercrm.com
</a><br>
> <br>
> Subject<br>
> <br>
> <br>
> <br>
> Re: [Vtigercrm-developers] An Impassioned Plea from a
VTiger <br>
> Integrator<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> Hi Matjaz!<br>
> I hope I am addressing you properly if not please forgive me and direct
<br>
> to the proper mode of addressing.<br>
> <br>
> If you are game then great!<br>
> Welcome to the club.<br>
> Please select your stand-in helper so that at least we have a backup
for <br>
> Linus Matjaz. Let me know and I will grant you the relevant access.<br>
> <br>
> It would be nice if you could briefly state how you plan to address
the<br>
> disparate contributions. This is just to get an idea as there are
lots <br>
> of data floating around in the code contributions and mailing lists;
<br>
> wanted to know if you have any specific plan. I will be busy with
the v5 <br>
> release and will not be able to help you much so the query.<br>
> I was earlier integrating it 1 by 1 till 4.2.3 and we do have a wiki
<br>
> page which reflects the status of the contributions. I am not sure
if <br>
> that is updated till the 4.2.4 release though. <br>
> <a href="http://www.vtiger.com/wiki/index.php/Vtiger_CRM_Code_Contributions" title="http://www.vtiger.com/wiki/index.php/Vtiger_CRM_Code_Contributions" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.vtiger.com/wiki/index.php/Vtiger_CRM_Code_Contributions</a><br>
> <br>
> <br>
> Allan, any tips from you will be nice.<br>
> <br>
> Richie<br>
> <br>
> <br>
> <br>
> <br>
> ---- Sergio A. Kessler<<a href="mailto:sergiokessler@gmail.com" title="mailto:sergiokessler@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">sergiokessler@gmail.com</a>> wrote ----
<br>
> <br>
> On 7/14/06, <a href="mailto:Matjaz.Slak@atol.si" title="mailto:Matjaz.Slak@atol.si" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Matjaz.Slak@atol.si</a> <<a href="mailto:Matjaz.Slak@atol.si" title="mailto:Matjaz.Slak@atol.si" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Matjaz.Slak@atol.si</a>> wrote:<br>
>><br>
>> Hi!<br>
>><br>
>> If there's no one else, I volunteer to be the v4 Linus.<br>
> <br>
> just do it. ;-)<br>
> <br>
> <br>
> /sak<br>
> _______________________________________________<br>
> Get started with creating presentations online - <a href="http://zohoshow.com?vt" title="http://zohoshow.com?vt" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://zohoshow.com?vt</a>
<br>
> <<a href="http://zohoshow.com?vt/%3E" title="http://zohoshow.com?vt/>" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://zohoshow.com?vt/></a> _______________________________________________
<br>
> Get started with creating presentations online - <a href="http://zohoshow.com?vt" title="http://zohoshow.com?vt" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://zohoshow.com?vt</a><br>
> <br>
> --<br>
> <br>
> Checked by AVG Anti-Virus.<br>
> Version: 7.0.308 / Virus Database: 268.10.1 - Release Date: 14/07/2006<br>
> <br>
> <br>
> ------------------------------------------------------------------------<br>
> <br>
> _______________________________________________<br>
> Get started with creating presentations online - <a href="http://zohoshow.com?vt" title="http://zohoshow.com?vt" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://zohoshow.com?vt</a>
<br>
_______________________________________________<br>
Get started with creating presentations online - <a href="http://zohoshow.com?vt" title="http://zohoshow.com?vt" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://zohoshow.com?vt</a>
<br>
</tt></font>
<br>
_______________________________________________<br>Get started with creating presentations online - <a href="http://zohoshow.com?vt" title="http://zohoshow.com?vt" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://zohoshow.com?vt</a> <br></blockquote></span></div><div></div>
</div><br>_______________________________________________<br>Get started with creating presentations online - <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://zohoshow.com?vt" target="_blank">http://zohoshow.com?vt
</a><br><br></blockquote></div><br>