Hi Alex,<br><br><div class="gmail_quote">On Sun, Dec 13, 2009 at 1:07 AM, Alexander Halle <span dir="ltr">&lt;<a href="mailto:ahalle-otrs@radprax.de">ahalle-otrs@radprax.de</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
OTRS::CiCS is an add-on to OTRS, like OTRS::ITSM or OTRS Manager. Users are informed of this for example in the manual and they can donwload the CiCS code under GPL license. Did you know this already ?</blockquote><div><br>
Yes, I recognized this. <br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
&gt; So can you clarify why you do not contribute your modifications to the<br>
&gt; OTRS project?<br></div>
[...]<br>
<br>
Do you mean backporting features to OTRS or did you mean the point discussed above ?<br></blockquote><div><br>Yes. Contribution/backport, that&#39;s my point. Why not contributing to OTRS it self (because most of the changes related to OTRS base, not as a own extension with new functionality like OTRS::ITSM or OTRS Manager - by the way, which I really like :) ).<br>
<br>In other point of view, isn&#39;t the goal to get OTRS it self forward by contributing back to the OTRS project?<br><br>Just my 2 cents,<br><br> Frank<br><br> --- OTRS fan since 2003 ---<br></div></div>