<br><br><div><span class="gmail_quote">On 3/4/06, <b class="gmail_sendername">Fathi BOUDRA</b> <<a href="mailto:fboudra@free.fr">fboudra@free.fr</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;">
Le Samedi 4 Mars 2006 20:41, Mike Fedyk a écrit:<br>> >I'm on record as favoring external dependency (with version checking, of<br>> >course) for everything vtigercrm currently keeps private snapshots/forks<br>
> >of. My reasons were primarily for distro-provided security upgrades, but<br>> >now licensing issues seem like they would be made easier if we didn't<br>> >distribute third-party software and keep it in our repository.
<br>> > <br>><br>> This only offloads the licensing issue to the distributor, like the<br>> vtiger windows exe and Linux bin distro so we don't gain anything<br>> there. Also it leaves the vtiger users in hot water. I don't think
<br>> this is a good way at all to avoid licensing issues.<br><br>from the beginning, there's architectural problem to keep our own copies of<br>softwares inside vtigercrm. We must deal with all licenses problem.<br><br>
We must focus on vigercrm code only and integration with external<br>dependencies. Yes, it's only dependencies and not vtigercrm core code.<br>These 3rd party software must be packaged correctly by packagers, it's their<br>
job.<br><br>vtigercrm really need code cleanup, and a modular view of vtigercrm<br>"distribution".<br></blockquote></div><br><br>I agree in 100%<br><br>at this moment I modularized:<br><br>- adodb<br>- libphp-log4php
<br><br>and work on:<br><br>- squirrelmail<br>- phpsysinfo<br>- xtemplate<br>- tutos<br><br>and think about:<br><br>- phpBB<br>- fpdf<br>- phpmail<br><br><br>Marcin<br><br><br>