tag:old.nabble.com,2006:forum-1558Nabble - DotGNU2009-11-25T14:49:14ZThe DotGNU project aims to be for webservices and for C# programs what GNU/Linux is rapidly becoming for desktop and server applications. DotGNU currently consists of three main development projects: DotGNU Portable.NET, phpGroupWare, and the DGEE webservice server. DotGNU home is <a href="http://www.dotgnu.org/" target="_top" rel="nofollow">here</a>.tag:old.nabble.com,2006:post-26521658Re: Commit in official trunk ...2009-11-25T14:49:14Z2009-11-25T14:49:14ZMaâtCaeies wrote:
<div class='shrinkable-quote'><br>> Hi all,
<br>>
<br>> Maât a écrit :
<br>>
<br>>> Caeies wrote:
<br>>>
<br>>>> Hi all,
<br>>>>
<br>>>> I'm happy to see new logs in the svn. But I have to urge all devs to be
<br>>>> *very* carefull when commiting in the repository.
<br>>>> As maat suggest having an easy understable log is important. I will not
<br>>>> focus in this email on this, but I think that the way he proposed to
<br>>>> "tag" logs is a good idea.
<br>>>> The real focus in this message is this :
<br>>>> Each commit *in trunk* should be "atomic". I mean, that if somebody do a
<br>>>> checkout, trunk should be "usable" after each commit. You are free to
<br>>>> do whatever you want in your own branch (but I would recommand to stick
<br>>>> to this policy), but not in trunk. Reasons are :
<br>>>> - easily review patches
<br>>>> - easily merge
<br>>>> - no missing files for people
<br>>>> - ...
<br>>>>
<br>>>>
<br>>> I'll add also :
<br>>>
<br>>> - stable
<br>>> - tested
<br>>> - reviewed by peers if the change lets some questions unanswered
<br>>>
<br>>> Let's take an example with the following :
<br>>>
<br>>> Log Message:
<br>>> -----------
<br>>> Bug fix : try to fix the get_member stuff, not sure if this is the right way to do it, but it works
<br>>>
<br>>>
<br>>> Commits with some uncertainty and "i'm not sure" comments like this one
<br>>> should not imho be committed straight in reference repositories but
<br>>> rather in personal repositories and should trigger a call for review :)
<br>>>
<br>> If trunk was bug free, I will be ok with this way of working.
<br>> Unfortunately, trunk is far away such a base, fixing it like this will
<br>> be easier. Note that I speak about _fixes_ and not "new features" ...
<br>> and IMHO this is a real difference.
<br>>
</div>I knew you'd answer something like this.
<br><br>Th'as why i wrote the last part of my previous message.
<br><br>Keep cool : we say globally the same thing :)
<br><br><br><div class='shrinkable-quote'><br>>> Then, once the patch is tested/reviewed/improved, you can merge the
<br>>> (perhaps improved) changes in one single commit with a
<br>>> professionnal-looking comment like for example :
<br>>>
<br>>> Bug fix : replaced the inexistant variable $this->account_id by the
<br>>> existing $account_id
<br>>>
<br>>
<br>> Well If this is what you understand of the patch ... damn, review can
<br>> take long time :).
<br>>
<br>> It's not because I take care of doubt in my commit that I'm not sure of
<br>> what I do ...
<br>>
</div>People that do care about code being clean do also care about changelogs.
<br><br>Having clean changelog gives a better image than logs saying "i dunno
<br>what i'm doing but nevermind it seems to do the trick"
<br><br>Wether you know in facts what you are doing is out of bounds... but just
<br>for my own peace of mind it's good to know that you are not committing
<br>random things :)))))))))))
<br><br><br><div class='shrinkable-quote'><br>>> As we are starting from a low level of quality as far as sources and
<br>>> changes control management is concerned we can close eyes a moment and
<br>>> go on fixing things without too high expectations on process quality but
<br>>> keep in mind that we'll need to improve this sooner or later (dunno if i
<br>>> can use this for the french expression "tôt ou tard") if we want to use
<br>>> svn logs to generate good looking Changelogs :)
<br>>>
<br>> IMHO this should be done when merging new features... from personnal
<br>> branches.
<br>>
</div>For big bugfixes on api with potentially heavy impact on several apps also
<br><br>For patches changing the way of doing things even if the change does not
<br>add new features also
<br><br>And there are probably dozens of other cases where this approach is
<br>good even if no new features are concerned ;)
<br><br>
<br><br>> Btw, before doing a commit I'm near always doing a svn annotate and take
<br>> a look at the people who commited in and the associated log ...
<br>>
<br>I need to make myself clear : I did not thought nor said i that you were
<br>a poor hacker or whatever. (imho you are a really good at php coding)
<br><br>It's just source control quality that i hope we all work to improve
<br>(slowly) up to the highest level possible :))
<br><br>(btw my comments were not supposed to upset you but rather to make you
<br>smile and answer something like "ok we could work on this once the bing
<br>cleaning phase is over")
<br><br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26521658&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26520598Re: Re: [Phpgroupware-cvs] [20896] Bug fix : check for already encoded utf8 stuff ...2009-11-25T13:07:50Z2009-11-25T13:07:50ZSigurd NesBenoit Hamet wrote:
<div class='shrinkable-quote'><br>> Hi Sigurd,
<br>>
<br>>> That one didn't work (for me).
<br>>> the mb_detect_encoding($text) is detecting the text as utf-8 even if it
<br>>> is ISO-8859-1
<br>>
<br>> This is a problem in your configuration of php. Anyway, I commit a fix
<br>> that should work in most configuration. Note that our non ISO-8859-1
<br>> users will have problem with your code, since I'm not sure that
<br>> utf8_encode is able to take their charset into account ...
<br>>
</div><br>Great - it works fine
<br><br>Thanks
<br><br>Sigurd
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26520598&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26520329Re: Fixing bugs2009-11-25T12:57:48Z2009-11-25T12:57:48ZSigurd NesBenoit Hamet wrote:
<div class='shrinkable-quote'><br>> Hi Sigurd,
<br>>
<br>> Sigurd Nes a écrit :
<br>>> Hi Caeies
<br>>>
<br>>> I really think we should test the modules in my personal repository
<br>>> before starting to fix the old trunk.
<br>>>
<br>>> especially admin, phpgwapi, setup and preferences has bee subjected to
<br>>> massive enhancement/improvements compared to the old trunk.
<br>> If you have working carefully, this should not be a problem. When I see
<br>> fixes in email apps not taking care of coding standards ... I'm more
<br>> woried ...
<br>>
<br>> (Please use phpgw::get_var() call instead of $_POST or whatever $_ vars).
</div><br>I always do - this one was an intermediate fix just to make it work.
<br><br>$GLOBALS['HTTP_POST_VARS'] and $_POST is equivalent - but
<br>$GLOBALS['HTTP_POST_VARS'] is deprecated in php 5.3
<br><br>Hence: this was a fix (same level as before - but working) - not a feature.
<br><div class='shrinkable-quote'><br>>
<br>>
<br>>> It will save a lot of work if we could consider this as the new base for
<br>>> improvements.
<br>> If I was considering your code base as the new base for improvements, I
<br>> will have ask you to directly commit into trunk ... As already said, we
<br>> will merge features from personal branches into trunk. If you have fixes
<br>> to commit into trunk before adding new features, please point us the
<br>> patches to review for fixes and not features ...
<br>>
</div>What I ask - is that you have a look at it and try it out.
<br><br>>
<br>>>
<br>>> (The member stuff active/nonactive users are all working fine)
<br>> ?
<br><br>Your latest commits fixes things that is already taken care of.(20897,20899 )
<br>I ask you again: please have a look at the code in my tree (and test it).
<br><br>>
<br>>> If we disagree on stuff I have done - that's fine we can take it from
<br>>> there - but it will get us moving a lot faster.
<br>> If we have easier way to fix trunk, I agree with you.
<br><br>What I can't understand is that you even won't try it - it will save months - I
<br>promise.
<br><br><br>Regards
<br><br>Sigurd
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26520329&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26519651Re: Re: [Phpgroupware-cvs] [20896] Bug fix : check for already encoded utf8 stuff ...2009-11-25T11:27:52Z2009-11-25T11:27:52ZBenoit HametSigurd Nes a écrit :
<div class='shrinkable-quote'><br>> Caeies wrote:
<br>>> Revision: 20896
<br>>>
<br>>> <a href="http://svn.sv.gnu.org/viewvc/?view=rev&root=phpgroupware&revision=20896" target="_top" rel="nofollow">http://svn.sv.gnu.org/viewvc/?view=rev&root=phpgroupware&revision=20896</a><br>>> Author: Caeies
<br>>> Date: 2009-11-25 16:35:37 +0000 (Wed, 25 Nov 2009)
<br>>> Log Message:
<br>>> -----------
<br>>> Bug fix : check for already encoded utf8 stuff ... instead of forcing
<br>>> it in all cases since utf8_encode(utf8_encode(X)) != utf_8_encode(X)
<br>>> if X is not pure ascii
<br>>>
<br>>> Modified Paths:
<br>>> --------------
<br>>> modules/email/trunk/inc/class.mail_msg_base.inc.php
<br>>>
<br>>> Modified: modules/email/trunk/inc/class.mail_msg_base.inc.php
<br>>> ===================================================================
<br>>> --- modules/email/trunk/inc/class.mail_msg_base.inc.php 2009-11-25
<br>>> 16:06:05 UTC (rev 20895)
<br>>> +++ modules/email/trunk/inc/class.mail_msg_base.inc.php 2009-11-25
<br>>> 16:35:37 UTC (rev 20896)
<br>>> @@ -4437,7 +4437,7 @@
<br>>> */
<br>>> function ascii2utf($text = '')
<br>>> {
<br>>> - if ($text == utf8_encode($text))
<br>>> + if ((function_exists('mb_detect_encoding') &&
<br>>> mb_detect_encoding($text) == 'UTF-8'))
<br>>> {
<br>>> return $text;
<br>>> }
<br>>>
<br>> Hi Caeies,
<br>>
<br>> That one didn't work (for me).
<br>> the mb_detect_encoding($text) is detecting the text as utf-8 even if it
<br>> is ISO-8859-1
<br>>
<br>> Please test.
</div><br>You too.
<br>if ($text == utf8_encode($text)) is a non-sense with already utf8 non
<br>ascii-only text ...
<br><br>And I didn't put any comment on that in the commit ... But if you want
<br>me to insist on the garbage code on the public list, I will be happy to
<br>do so.
<br><br>Regards,
<br><br>Caeies.
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26519651&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26519640Re: Fixing bugs2009-11-25T11:20:58Z2009-11-25T11:20:58ZBenoit HametHi Sigurd,
<br><br>Sigurd Nes a écrit :
<br>>
<br>> Hi Caeies
<br>>
<br>> I really think we should test the modules in my personal repository
<br>> before starting to fix the old trunk.
<br>>
<br>> especially admin, phpgwapi, setup and preferences has bee subjected to
<br>> massive enhancement/improvements compared to the old trunk.
<br>If you have working carefully, this should not be a problem. When I see
<br>fixes in email apps not taking care of coding standards ... I'm more
<br>woried ...
<br><br>(Please use phpgw::get_var() call instead of $_POST or whatever $_ vars).
<br><br><br>>
<br>> It will save a lot of work if we could consider this as the new base for
<br>> improvements.
<br>If I was considering your code base as the new base for improvements, I
<br>will have ask you to directly commit into trunk ... As already said, we
<br>will merge features from personal branches into trunk. If you have fixes
<br>to commit into trunk before adding new features, please point us the
<br>patches to review for fixes and not features ...
<br><br><br>>
<br>>
<br>> (The member stuff active/nonactive users are all working fine)
<br>?
<br><br>>
<br>> If we disagree on stuff I have done - that's fine we can take it from
<br>> there - but it will get us moving a lot faster.
<br>If we have easier way to fix trunk, I agree with you.
<br><br>Regards,
<br><br>Caeies
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26519640&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26519589Re: Commit in official trunk ...2009-11-25T11:12:28Z2009-11-25T11:12:28ZCaeies-2Hi all,
<br><br>Maât a écrit :
<div class='shrinkable-quote'><br>> Caeies wrote:
<br>>> Hi all,
<br>>>
<br>>> I'm happy to see new logs in the svn. But I have to urge all devs to be
<br>>> *very* carefull when commiting in the repository.
<br>>> As maat suggest having an easy understable log is important. I will not
<br>>> focus in this email on this, but I think that the way he proposed to
<br>>> "tag" logs is a good idea.
<br>>> The real focus in this message is this :
<br>>> Each commit *in trunk* should be "atomic". I mean, that if somebody do a
<br>>> checkout, trunk should be "usable" after each commit. You are free to
<br>>> do whatever you want in your own branch (but I would recommand to stick
<br>>> to this policy), but not in trunk. Reasons are :
<br>>> - easily review patches
<br>>> - easily merge
<br>>> - no missing files for people
<br>>> - ...
<br>>>
<br>> I'll add also :
<br>>
<br>> - stable
<br>> - tested
<br>> - reviewed by peers if the change lets some questions unanswered
<br>>
<br>> Let's take an example with the following :
<br>>
<br>> Log Message:
<br>> -----------
<br>> Bug fix : try to fix the get_member stuff, not sure if this is the right way to do it, but it works
<br>>
<br>>
<br>> Commits with some uncertainty and "i'm not sure" comments like this one
<br>> should not imho be committed straight in reference repositories but
<br>> rather in personal repositories and should trigger a call for review :)
</div>If trunk was bug free, I will be ok with this way of working.
<br>Unfortunately, trunk is far away such a base, fixing it like this will
<br>be easier. Note that I speak about _fixes_ and not "new features" ...
<br>and IMHO this is a real difference.
<br><br>>
<br>> Then, once the patch is tested/reviewed/improved, you can merge the
<br>> (perhaps improved) changes in one single commit with a
<br>> professionnal-looking comment like for example :
<br>>
<br>> Bug fix : replaced the inexistant variable $this->account_id by the
<br>> existing $account_id
<br><br>Well If this is what you understand of the patch ... damn, review can
<br>take long time :).
<br><br>It's not because I take care of doubt in my commit that I'm not sure of
<br>what I do ...
<br><br><br>>
<br>> As we are starting from a low level of quality as far as sources and
<br>> changes control management is concerned we can close eyes a moment and
<br>> go on fixing things without too high expectations on process quality but
<br>> keep in mind that we'll need to improve this sooner or later (dunno if i
<br>> can use this for the french expression "tôt ou tard") if we want to use
<br>> svn logs to generate good looking Changelogs :)
<br>IMHO this should be done when merging new features... from personnal
<br>branches.
<br><br>Btw, before doing a commit I'm near always doing a svn annotate and take
<br>a look at the people who commited in and the associated log ...
<br><br>Regards,
<br><br>Caeies
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26519589&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26519464Re: Re: [Phpgroupware-cvs] [20896] Bug fix : check for already encoded utf8 stuff ...2009-11-25T11:00:33Z2009-11-25T11:00:33ZBenoit HametHi Sigurd,
<br><br>>
<br>> That one didn't work (for me).
<br>> the mb_detect_encoding($text) is detecting the text as utf-8 even if it
<br>> is ISO-8859-1
<br><br>This is a problem in your configuration of php. Anyway, I commit a fix
<br>that should work in most configuration. Note that our non ISO-8859-1
<br>users will have problem with your code, since I'm not sure that
<br>utf8_encode is able to take their charset into account ...
<br><br>Regards,
<br><br>Caeies.
<br><div class='shrinkable-quote'><br>>
<br>> Please test.
<br>>
<br>> I'm using PHP Version 5.3.1 with default settings:
<br>>
<br>>
<br>> mbstring
<br>>
<br>> Multibyte Support enabled
<br>> Multibyte string engine libmbfl
<br>> HTTP input encoding translation disabled
<br>>
<br>>
<br>> mbstring extension makes use of "streamable kanji code filter and
<br>> converter", which is distributed under the GNU Lesser General Public
<br>> License version 2.1.
<br>>
<br>>
<br>> Multibyte (japanese) regex support enabled
<br>> Multibyte regex (oniguruma) backtrack check On
<br>> Multibyte regex (oniguruma) version 4.7.1
<br>>
<br>>
<br>> Directive Local Value Master Value
<br>> mbstring.detect_order /no value/ /no value/
<br>> mbstring.encoding_translation Off Off
<br>> mbstring.func_overload 0 0
<br>> mbstring.http_input pass pass
<br>> mbstring.http_output pass pass
<br>> mbstring.http_output_conv_mimetypes ^(text/|application/xhtml\+xml)
<br>> ^(text/|application/xhtml\+xml)
<br>> mbstring.internal_encoding /no value/ /no value/
<br>> mbstring.language neutral neutral
<br>> mbstring.strict_detection Off Off
<br>> mbstring.substitute_character /no value/ /no value/
<br>>
<br>>
<br>>
<br>> Regards
<br>>
<br>> Sigurd
<br>>
<br>>
<br>> ------------------------------------------------------------------------
<br>>
<br>> _______________________________________________
<br>> phpGroupWare-developers mailing list
<br>> <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26519464&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br>> <a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a></div><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26519464&i=1" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26518111Re: Commit in official trunk ...2009-11-25T10:41:14Z2009-11-25T10:41:14ZMaâtCaeies wrote:
<div class='shrinkable-quote'><br>> Hi all,
<br>>
<br>> I'm happy to see new logs in the svn. But I have to urge all devs to be
<br>> *very* carefull when commiting in the repository.
<br>> As maat suggest having an easy understable log is important. I will not
<br>> focus in this email on this, but I think that the way he proposed to
<br>> "tag" logs is a good idea.
<br>> The real focus in this message is this :
<br>> Each commit *in trunk* should be "atomic". I mean, that if somebody do a
<br>> checkout, trunk should be "usable" after each commit. You are free to
<br>> do whatever you want in your own branch (but I would recommand to stick
<br>> to this policy), but not in trunk. Reasons are :
<br>> - easily review patches
<br>> - easily merge
<br>> - no missing files for people
<br>> - ...
<br>>
</div>I'll add also :
<br><br>- stable
<br>- tested
<br>- reviewed by peers if the change lets some questions unanswered
<br><br>Let's take an example with the following :
<br><br>Log Message:
<br>-----------
<br>Bug fix : try to fix the get_member stuff, not sure if this is the right way to do it, but it works
<br><br><br>Commits with some uncertainty and "i'm not sure" comments like this one
<br>should not imho be committed straight in reference repositories but
<br>rather in personal repositories and should trigger a call for review :)
<br><br>Then, once the patch is tested/reviewed/improved, you can merge the
<br>(perhaps improved) changes in one single commit with a
<br>professionnal-looking comment like for example :
<br><br>Bug fix : replaced the inexistant variable $this->account_id by the
<br>existing $account_id
<br><br>As we are starting from a low level of quality as far as sources and
<br>changes control management is concerned we can close eyes a moment and
<br>go on fixing things without too high expectations on process quality but
<br>keep in mind that we'll need to improve this sooner or later (dunno if i
<br>can use this for the french expression "tôt ou tard") if we want to use
<br>svn logs to generate good looking Changelogs :)
<br><br>regards,
<br>Maât
<br><br><br><br><br><br><br><br>
<br><br><br><br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26518111&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26518095Fixing bugs2009-11-25T10:40:27Z2009-11-25T10:40:27ZSigurd NesHi Caeies
<br><br>I really think we should test the modules in my personal repository before
<br>starting to fix the old trunk.
<br><br>especially admin, phpgwapi, setup and preferences has bee subjected to massive
<br>enhancement/improvements compared to the old trunk.
<br><br>It will save a lot of work if we could consider this as the new base for
<br>improvements.
<br><br><br>(The member stuff active/nonactive users are all working fine)
<br><br>If we disagree on stuff I have done - that's fine we can take it from there -
<br>but it will get us moving a lot faster.
<br><br>Regards
<br><br>Sigurd
<br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26518095&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26517324Re: [Phpgroupware-cvs] [20896] Bug fix : check for already encoded utf8 stuff ...2009-11-25T09:50:08Z2009-11-25T09:50:08ZSigurd Nes<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Caeies wrote:
<blockquote cite="mid:E1NDKq9-0004rh-Ec@cvs.savannah.gnu.org" type="cite">
<pre wrap="">Revision: 20896
<a class="moz-txt-link-freetext" href="http://svn.sv.gnu.org/viewvc/?view=rev&root=phpgroupware&revision=20896" target="_top" rel="nofollow">http://svn.sv.gnu.org/viewvc/?view=rev&root=phpgroupware&revision=20896</a>
Author: Caeies
Date: 2009-11-25 16:35:37 +0000 (Wed, 25 Nov 2009)
Log Message:
-----------
Bug fix : check for already encoded utf8 stuff ... instead of forcing it in all cases since utf8_encode(utf8_encode(X)) != utf_8_encode(X) if X is not pure ascii
Modified Paths:
--------------
modules/email/trunk/inc/class.mail_msg_base.inc.php
Modified: modules/email/trunk/inc/class.mail_msg_base.inc.php
===================================================================
--- modules/email/trunk/inc/class.mail_msg_base.inc.php 2009-11-25 16:06:05 UTC (rev 20895)
+++ modules/email/trunk/inc/class.mail_msg_base.inc.php 2009-11-25 16:35:37 UTC (rev 20896)
@@ -4437,7 +4437,7 @@
*/
function ascii2utf($text = '')
{
- if ($text == utf8_encode($text))
+ if ((function_exists('mb_detect_encoding') && mb_detect_encoding($text) == 'UTF-8'))
{
return $text;
}
</pre>
</blockquote>
Hi Caeies,<br>
<br>
That one didn't work (for me).<br>
the mb_detect_encoding($text) is detecting the text as utf-8 even if it
is ISO-8859-1<br>
<br>
Please test.<br>
<br>
I'm using PHP Version 5.3.1 with default settings:<br>
<br>
<h2><a name="module_mbstring" target="_top">mbstring</a></h2>
<table border="0" cellpadding="3" width="600">
<tbody>
<tr>
<td class="e">Multibyte Support </td>
<td class="v">enabled </td>
</tr>
<tr>
<td class="e">Multibyte string engine </td>
<td class="v">libmbfl </td>
</tr>
<tr>
<td class="e">HTTP input encoding translation </td>
<td class="v">disabled </td>
</tr>
</tbody>
</table>
<br>
<table border="0" cellpadding="3" width="600">
<tbody>
<tr class="h">
<th>mbstring extension makes use of "streamable
kanji code filter and converter", which is distributed under the GNU
Lesser General Public License version 2.1.</th>
</tr>
</tbody>
</table>
<br>
<table border="0" cellpadding="3" width="600">
<tbody>
<tr>
<td class="e">Multibyte (japanese) regex support </td>
<td class="v">enabled </td>
</tr>
<tr>
<td class="e">Multibyte regex (oniguruma) backtrack check </td>
<td class="v">On </td>
</tr>
<tr>
<td class="e">Multibyte regex (oniguruma) version </td>
<td class="v">4.7.1 </td>
</tr>
</tbody>
</table>
<br>
<table border="0" cellpadding="3" width="600">
<tbody>
<tr class="h">
<th>Directive</th>
<th>Local Value</th>
<th>Master Value</th>
</tr>
<tr>
<td class="e">mbstring.detect_order</td>
<td class="v"><i>no value</i></td>
<td class="v"><i>no value</i></td>
</tr>
<tr>
<td class="e">mbstring.encoding_translation</td>
<td class="v">Off</td>
<td class="v">Off</td>
</tr>
<tr>
<td class="e">mbstring.func_overload</td>
<td class="v">0</td>
<td class="v">0</td>
</tr>
<tr>
<td class="e">mbstring.http_input</td>
<td class="v">pass</td>
<td class="v">pass</td>
</tr>
<tr>
<td class="e">mbstring.http_output</td>
<td class="v">pass</td>
<td class="v">pass</td>
</tr>
<tr>
<td class="e">mbstring.http_output_conv_mimetypes</td>
<td class="v">^(text/|application/xhtml\+xml)</td>
<td class="v">^(text/|application/xhtml\+xml)</td>
</tr>
<tr>
<td class="e">mbstring.internal_encoding</td>
<td class="v"><i>no value</i></td>
<td class="v"><i>no value</i></td>
</tr>
<tr>
<td class="e">mbstring.language</td>
<td class="v">neutral</td>
<td class="v">neutral</td>
</tr>
<tr>
<td class="e">mbstring.strict_detection</td>
<td class="v">Off</td>
<td class="v">Off</td>
</tr>
<tr>
<td class="e">mbstring.substitute_character</td>
<td class="v"><i>no value</i></td>
<td class="v"><i>no value</i></td>
</tr>
</tbody>
</table>
<br>
<br>
Regards<br>
<br>
Sigurd<br>
</body>
</html>
<br />_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26517324&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26511350Commit in official trunk ...2009-11-25T03:41:04Z2009-11-25T03:41:04ZCaeies-2Hi all,
<br><br>I'm happy to see new logs in the svn. But I have to urge all devs to be
<br>*very* carefull when commiting in the repository.
<br>As maat suggest having an easy understable log is important. I will not
<br>focus in this email on this, but I think that the way he proposed to
<br>"tag" logs is a good idea.
<br>The real focus in this message is this :
<br>Each commit *in trunk* should be "atomic". I mean, that if somebody do a
<br> checkout, trunk should be "usable" after each commit. You are free to
<br>do whatever you want in your own branch (but I would recommand to stick
<br>to this policy), but not in trunk. Reasons are :
<br> - easily review patches
<br> - easily merge
<br> - no missing files for people
<br> - ...
<br><br>Thanks to all !
<br><br>Caeies.
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26511350&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26494146Re: Email search fixing (was : Code available for test)2009-11-24T03:14:11Z2009-11-24T03:14:11ZMaâtSigurd Nes wrote:
<br>>
<br>>> From: Maât [<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26494146&i=0" target="_top" rel="nofollow">maat@...</a>]
<br>>>
<br>>> (Btw i did not understand this non-ascii problem by just reading your
<br>>> changes... would you mind to explain the problem and the fix to me please ?)
<br>>>
<br>> The search didn't work at all - now it works at least with ascii.
<br>>
<br>ok :)
<br><br>that's why i did not see code that looked like something that does deal
<br>with ascii/non-ascii problems :)
<br><br>> Tried to play with different encoding - like imap_utf7_encode() to the criteria applied to imap_search - but no luck.
<br>> Maybe you can have a go at it?
<br>> The actual search is performed in class.mail_dcom_imap.inc.php, function: i_search() around line 243.
<br>>
<br>> The only (other) thing (I think) remaining - is the filter feature - seems like a object wasn't initialized....
<br>>
<br>> Maybe you can see at it with fresh eyes?
<br>>
<br>yep... that can not bring harm if i give it a look just in case :)
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26494146&i=1" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26493500RE: Code available for test2009-11-24T02:22:18Z2009-11-24T02:22:18ZSigurd Nes<br><div class='shrinkable-quote'><div class='shrinkable-quote'><br>> From: Maât [<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26493500&i=0" target="_top" rel="nofollow">maat@...</a>]
<br>> Sent: 2009-11-24 10:14:29 CET
<br>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26493500&i=1" target="_top" rel="nofollow">phpgroupware-developers@...</a>
<br>> Subject: Re: [phpGroupWare-developers] Code available for test
<br>>
<br>> Sigurd Nes wrote:
<br>> >
<br>> >> wow...
<br>> >>
<br>> >> subversion log living again :)
<br>> >>
<br>> >> just one question (i'm curious) do subversion repos and this tar.gz
<br>> >> contain the same code ?
<br>> >>
<br>> >> if no which one is ahead ?
<br>> >>
<br>> >>
<br>> > It is identical (to the date) - it's just to spare peopel of having to deal with svn:externals.
<br>> >
<br>> Wooohooo ! Then i can test it with a checkout and compare trees \o/
<br>>
<br>> Thanks :)
<br>>
<br>> > email is from phpgroupware/modules/email/trunk - the rest is from phpgroupware/people/sigurdne...
<br>> >
<br>> > (I took the liberty of tuning the email-app directly without going via the personal repository - as this is minor fixes)
<br>> >
<br>> I looked at the patches... yeah they all seem minor and positive fixes
<br>> so no problem for me.
<br>>
<br>>
<br>> May i just suggest something for the future ?
<br>>
<br>> I'd like we all think about commit log standardization so that we have
<br>> more presision and the possibility to create changelogs automatically later.
<br>>
<br>> I's suggest for example something like a beginning tag
<br>>
<br>> Bug fix : <-- patche that fix wrong code
<br>> Security fix : <-- obvious isn't it ? :)
<br>> Code formatting : <-- this one just for indentation and other chenges
<br>> that do not change the code
<br>> Code cleaning : <-- this one for php modernization and other changes
<br>> that do change the code but do not change the resulting behavior
<br>> New feature : <-- this one new cool feature
<br>> ...
<br>>
<br>> (we would of course need to define the precise list of possible tags)
<br>>
<br>> And i'd suggest that a commit concerns only one specific point
<br>>
<br>> for example i'd rather have seen change set [20890] Fix search (not
<br>> happy with non-ascii) splitted in two :
<br>>
<br>> -- one for the php code modernization :
<br>> Code cleaning : changing from $GLOBALS['HTTP_POST_VARS'] to $_POST and
<br>> removing trailing ?>
<br>>
<br>> -- One for the real fixing part :
<br>> Bug fix : Fix search problem with non-ascii
<br>>
<br>>
<br>> That suggestion is not supposed to be taken "as it is" but rather to be
<br>> the start point of a common work to improve it so that we end with
<br>> some nice rules for svn management :)
<br>>
<br>>
<br>> (Btw i did not understand this non-ascii problem by just reading your
<br>> changes... would you mind to explain the problem and the fix to me please ?)
<br>>
</div>The search didn't work at all - now it works at least with ascii.
</div>Tried to play with different encoding - like imap_utf7_encode() to the criteria applied to imap_search - but no luck.
<br>Maybe you can have a go at it?
<br>The actual search is performed in class.mail_dcom_imap.inc.php, function: i_search() around line 243.
<br><br>The only (other) thing (I think) remaining - is the filter feature - seems like a object wasn't initialized....
<br><br>Maybe you can see at it with fresh eyes?
<br><br>Regards
<br><br>Sigurd
<br><br />_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26493500&i=2" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26492833Re: Code available for test2009-11-24T01:14:29Z2009-11-24T01:14:29ZMaâtSigurd Nes wrote:
<div class='shrinkable-quote'><br>>
<br>>> wow...
<br>>>
<br>>> subversion log living again :)
<br>>>
<br>>> just one question (i'm curious) do subversion repos and this tar.gz
<br>>> contain the same code ?
<br>>>
<br>>> if no which one is ahead ?
<br>>>
<br>>>
<br>> It is identical (to the date) - it's just to spare peopel of having to deal with svn:externals.
<br>>
</div>Wooohooo ! Then i can test it with a checkout and compare trees \o/
<br><br>Thanks :)
<br><br>> email is from phpgroupware/modules/email/trunk - the rest is from phpgroupware/people/sigurdne...
<br>>
<br>> (I took the liberty of tuning the email-app directly without going via the personal repository - as this is minor fixes)
<br>>
<br>I looked at the patches... yeah they all seem minor and positive fixes
<br>so no problem for me.
<br><br><br>May i just suggest something for the future ?
<br><br>I'd like we all think about commit log standardization so that we have
<br>more presision and the possibility to create changelogs automatically later.
<br><br>I's suggest for example something like a beginning tag
<br><br>Bug fix : <-- patche that fix wrong code
<br>Security fix : <-- obvious isn't it ? :)
<br>Code formatting : <-- this one just for indentation and other chenges
<br>that do not change the code
<br>Code cleaning : <-- this one for php modernization and other changes
<br>that do change the code but do not change the resulting behavior
<br>New feature : <-- this one new cool feature
<br>...
<br><br>(we would of course need to define the precise list of possible tags)
<br><br>And i'd suggest that a commit concerns only one specific point
<br><br>for example i'd rather have seen change set [20890] Fix search (not
<br>happy with non-ascii) splitted in two :
<br><br>-- one for the php code modernization :
<br>Code cleaning : changing from $GLOBALS['HTTP_POST_VARS'] to $_POST and
<br>removing trailing ?>
<br><br>-- One for the real fixing part :
<br>Bug fix : Fix search problem with non-ascii
<br><br><br>That suggestion is not supposed to be taken "as it is" but rather to be
<br>the start point of a common work to improve it so that we end with
<br>some nice rules for svn management :)
<br><br><br>(Btw i did not understand this non-ascii problem by just reading your
<br>changes... would you mind to explain the problem and the fix to me please ?)
<br><br><br>Best regards,
<br>Maât
<br><br><br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26492833&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26491976RE: Code available for test2009-11-24T00:10:47Z2009-11-24T00:10:47ZSigurd Nes<br><div class='shrinkable-quote'><div class='shrinkable-quote'><br>> From: Maât [<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26491976&i=0" target="_top" rel="nofollow">maat@...</a>]
<br>> Sent: 2009-11-24 00:00:53 CET
<br>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26491976&i=1" target="_top" rel="nofollow">phpgroupware-developers@...</a>
<br>> Subject: Re: [phpGroupWare-developers] Code available for test
<br>>
<br>> Sigurd Nes wrote:
<br>> > Sigurd Nes wrote:
<br>> >> The email app is updated and seems to work.
<br>> >>
<br>> >> Fresh code is available for testing at:
<br>> >>
<br>> >> XXX
<br>> > Old one is removed.
<br>> >
<br>> >>
<br>> >>
<br>> >> Modules:
<br>> >> * addressbook
<br>> >> * admin
<br>> >> * calendar
<br>> >> * email
<br>> >> * hrm
<br>> >> * manual
<br>> >> * messenger
<br>> >> * notes
<br>> >> * preferences
<br>> >> * (projects - well - kind of)
<br>> >> * property
<br>> >> * sms
<br>> >> * todo
<br>> >>
<br>> >
<br>> > There is a new one:
<br>> > <a href="http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_23.tar.gz" target="_top" rel="nofollow">http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_23.tar.gz</a><br>> >
<br>> >
<br>> > Fixes to the email app:
<br>> > File attachment, spell checker and search
<br>> >
<br>> >
<br>> >
<br>> > Regards
<br>> >
<br>> > Sigurd
<br>> wow...
<br>>
<br>> subversion log living again :)
<br>>
<br>> just one question (i'm curious) do subversion repos and this tar.gz
<br>> contain the same code ?
<br>>
<br>> if no which one is ahead ?
<br>>
</div>It is identical (to the date) - it's just to spare peopel of having to deal with svn:externals.
</div><br>email is from phpgroupware/modules/email/trunk - the rest is from phpgroupware/people/sigurdne...
<br><br>(I took the liberty of tuning the email-app directly without going via the personal repository - as this is minor fixes)
<br><br>Regards
<br><br>Sigurd
<br><br />_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26491976&i=2" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26487684Re: Code available for test2009-11-23T15:00:53Z2009-11-23T15:00:53ZMaâtSigurd Nes wrote:
<div class='shrinkable-quote'><br>> Sigurd Nes wrote:
<br>>> The email app is updated and seems to work.
<br>>>
<br>>> Fresh code is available for testing at:
<br>>>
<br>>> XXX
<br>> Old one is removed.
<br>>
<br>>>
<br>>>
<br>>> Modules:
<br>>> * addressbook
<br>>> * admin
<br>>> * calendar
<br>>> * email
<br>>> * hrm
<br>>> * manual
<br>>> * messenger
<br>>> * notes
<br>>> * preferences
<br>>> * (projects - well - kind of)
<br>>> * property
<br>>> * sms
<br>>> * todo
<br>>>
<br>>
<br>> There is a new one:
<br>> <a href="http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_23.tar.gz" target="_top" rel="nofollow">http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_23.tar.gz</a><br>>
<br>>
<br>> Fixes to the email app:
<br>> File attachment, spell checker and search
<br>>
<br>>
<br>>
<br>> Regards
<br>>
<br>> Sigurd
</div>wow...
<br><br>subversion log living again :)
<br><br>just one question (i'm curious) do subversion repos and this tar.gz
<br>contain the same code ?
<br><br>if no which one is ahead ?
<br><br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26487684&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26485810Re: Code available for test2009-11-23T12:44:34Z2009-11-23T12:44:34ZSigurd NesSigurd Nes wrote:
<br>> The email app is updated and seems to work.
<br>>
<br>> Fresh code is available for testing at:
<br>>
<br>> XXX
<br>Old one is removed.
<br><div class='shrinkable-quote'><br>>
<br>>
<br>> Modules:
<br>> * addressbook
<br>> * admin
<br>> * calendar
<br>> * email
<br>> * hrm
<br>> * manual
<br>> * messenger
<br>> * notes
<br>> * preferences
<br>> * (projects - well - kind of)
<br>> * property
<br>> * sms
<br>> * todo
<br>>
</div><br>There is a new one:
<br><a href="http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_23.tar.gz" target="_top" rel="nofollow">http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_23.tar.gz</a><br><br>Fixes to the email app:
<br>File attachment, spell checker and search
<br><br><br><br>Regards
<br><br>Sigurd
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26485810&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26474426Re: phpmailer needs to be replaced2009-11-23T00:48:14Z2009-11-23T00:48:14ZMaâtMaât wrote:
<div class='shrinkable-quote'><br>> Sigurd Nes wrote:
<br>>
<br>>> phpmailer in which email depends on - seems to be GPLv2-only.
<br>>>
<br>>> Anyone care to find (and implement) an alternative?
<br>>>
<br>>> Regards
<br>>>
<br>>> Sigurd
<br>>>
<br>> Seems that it's LGPL without the version being detailed in the body of
<br>> the files.
<br>>
<br>> And a license file LGPL v 2.1 is provided aside.
<br>>
<br>> I dont think they would mind if we use v3 instead of v 2
<br>>
<br>> I'm going to ask them : it's the shortest way to know about their point
<br>> of view
<br>>
<br>> Maât
<br>>
</div>Well after digging a lilttle bit phpmailer is not a problem.
<br><br><a href="http://www.gnu.org/licenses/gpl-faq.html#matrix-skip-target" target="_top" rel="nofollow">http://www.gnu.org/licenses/gpl-faq.html#matrix-skip-target</a><br><br>we can use a lgpl v2.1 only library into a GPL v3 project.
<br><br>We would need phpmailer guys authorization if we wanted to convert to
<br>lgpl v3
<br><br>plase note also that we could convert lgpl v2.1 to gpl v3 (not lgpl)
<br>without needing to ask them : lgpl explicitly allows us to do so.
<br><br>i'm still going to ask them because having all libraries under the same
<br>lgpl v3 licence would be more logical and easier to understand for
<br>everybody.
<br><br>Regards,
<br><br>Maât
<br><br><br>PS : We could also move the phpmailer library from lgpl 2.1 only to lgpl
<br>2.1 or later then move from lgpl v2.1 or later to lgpl v 3 or later but
<br>we would need to publish somewhere these libraries as independant packages.
<br><br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26474426&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26473825Re: phpmailer needs to be replaced2009-11-22T23:44:39Z2009-11-22T23:44:39ZMaâtSigurd Nes wrote:
<br>> phpmailer in which email depends on - seems to be GPLv2-only.
<br>>
<br>> Anyone care to find (and implement) an alternative?
<br>>
<br>> Regards
<br>>
<br>> Sigurd
<br>Seems that it's LGPL without the version being detailed in the body of
<br>the files.
<br><br>And a license file LGPL v 2.1 is provided aside.
<br><br>I dont think they would mind if we use v3 instead of v 2
<br><br>I'm going to ask them : it's the shortest way to know about their point
<br>of view
<br><br>Maât
<br><br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26473825&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26470117phpmailer needs to be replaced2009-11-22T14:12:59Z2009-11-22T14:12:59ZSigurd Nesphpmailer in which email depends on - seems to be GPLv2-only.
<br><br>Anyone care to find (and implement) an alternative?
<br><br>Regards
<br><br>Sigurd
<br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26470117&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26469573Code available for test2009-11-22T13:16:38Z2009-11-22T13:16:38ZSigurd NesThe email app is updated and seems to work.
<br><br>Fresh code is available for testing at:
<br><br><a href="http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_22.tar.gz" target="_top" rel="nofollow">http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_22.tar.gz</a><br><br><br>Modules:
<br>* addressbook
<br>* admin
<br>* calendar
<br>* email
<br>* hrm
<br>* manual
<br>* messenger
<br>* notes
<br>* preferences
<br>* (projects - well - kind of)
<br>* property
<br>* sms
<br>* todo
<br><br><br>Regards
<br><br>Sigurd
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26469573&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26460973Re: IMPORTANT : SVN Structure change (Was Re: Who wants to play?)2009-11-21T14:26:08Z2009-11-21T14:26:08ZMaâtSigurd Nes wrote:
<div class='shrinkable-quote'><br>>>> The main difference are
<br>>>> - That db-abstraction is converted to pdo (faster and more secure) -
<br>>>> and that innodb is default for Mysql (to support transactions).
<br>>>> The db-object supports db-cloning - which I really really need - so
<br>>>> please don't remove it.
<br>>> In you personal repository *nobody* except you is supposed to play :
<br>>> you're your own master. If you don't remove it then it will not be
<br>>> removed (not by me whatever).
<br>>>
<br>>> but till the feature is considered fool-proof, suited for stable
<br>>> release, tested against regressions and accepted by all the coordinators
<br>>> team it's merge into base repository could be delayed
<br>>>
<br>>> please do not consider this as a personal offence... it's just
<br>>> paranoïa :)
<br>>>
<br>> By all means - but the current trunk is really a mess.
<br>> If you don't want to use my version as base for improvements - I will
<br>> recommend to revert to the state of before Dave's mega patch -and take
<br>> it from there.
</div>i personnally *want* to use as much as possible of your improvements but
<br>one mega patch is already too much.
<br><br>reverting this patch wouldbring more harm than good.
<br><br>i'm just pleading for a clean way of doing things even if the starting
<br>base is not the best :)
<br><br><br><br><br>>>
<br>>>> - mcrypted all settings in header.inc.php if set
<br>>> ?
<br>> If mcrypt is installed and set to "true" - the
<br>> db-name/db-user/db-password is encrypted. Making it more secure.
<br>ok thanks
<br><div class='shrinkable-quote'><br>>>
<br>>>> I recommend that we take it further from the current state rather than
<br>>>> trying to merge back single fixes.
<br>>> well i'm not all for this way of doing things. I know previous gigantic
<br>>> merges from resight have been done and accepted but thats (imho) the
<br>>> best way to create problems.
<br>>
<br>> This ones fixes all the problems induced by the previous mega-patch :)
<br>> Also - it is tested - and runs in a production environment.
<br>>
<br>> (phpgwapi/setup/manual/preferences/property/sms)
</div><br>well that's a good point but that's just one production environment...
<br>we can imagine that other production environments could be harmed by
<br>the changes
<br><br>i'm just trying to avoid problems :)
<br><br>if yours changes solve problems they *need* to be merged into base repos :)
<br><div class='shrinkable-quote'><br>>>>
<br>>>>
<br>>>> * system trunk:
<br>>>> email might work(if configuration is correct): if it hangs - delete
<br>>>> the menu-hook and restart apache
<br>>> ?
<br>>>
<br>>> Could you explain more this case please ?
<br>>>
<br>>> Just so that i understand why deleting menu-hook could improve
<br>>> things :)
<br>> It stops the process of trying to connect to the wrongly configured
<br>> pop/imap-server when loading the menu.
<br>> The email app is a weak spot...
</div>ok thanks :)
<br><div class='shrinkable-quote'><br>>
<br>> Another coming feature (in a few weeks) is general support for jasper
<br>> reports
<br>>
<br>> To make it easy to test - I have uploaded this version to:
<br>> <a href="http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_21.tar.gz" target="_top" rel="nofollow">http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_21.tar.gz</a><br>>
<br>>
<br>> Keep in mind that you need pdo - and I recommend PostgreSQL 8.3 and
<br>> above.
<br>>
<br>> Install all apps and try it:)
<br>>
<br>> Regards
<br>>
<br>> Sigurd
<br>>
</div>:)
<br><br>thanks for your answeer Sigurd :)
<br><br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26460973&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26460883Re: IMPORTANT : SVN Structure change (Was Re: Who wants to play?)2009-11-21T14:14:18Z2009-11-21T14:14:18ZSigurd NesMaât wrote:
<div class='shrinkable-quote'><br>> Sigurd Nes wrote:
<br>>>> Thanks Sigrud.
<br>>>>
<br>>>> Glad to see you have started to put new things into your "personal"
<br>>>> repository.
<br>>>>
<br>>>> Hope you'll find a little bit of time to explain quickly the big
<br>>>> differences between each base trunk app and your work so that we know
<br>>>> what could be looked at for later merging :)
<br>>>>
<br>>> I'm done - Take it for a spin :)
<br>> :)
<br>>
<br>>> The main difference are
<br>>> - That db-abstraction is converted to pdo (faster and more secure) -
<br>>> and that innodb is default for Mysql (to support transactions).
<br>>> The db-object supports db-cloning - which I really really need - so
<br>>> please don't remove it.
<br>> In you personal repository *nobody* except you is supposed to play :
<br>> you're your own master. If you don't remove it then it will not be
<br>> removed (not by me whatever).
<br>>
<br>> but till the feature is considered fool-proof, suited for stable
<br>> release, tested against regressions and accepted by all the coordinators
<br>> team it's merge into base repository could be delayed
<br>>
<br>> please do not consider this as a personal offence... it's just paranoïa :)
<br>>
</div>By all means - but the current trunk is really a mess.
<br>If you don't want to use my version as base for improvements - I will recommend
<br>to revert to the state of before Dave's mega patch -and take it from there.
<br><div class='shrinkable-quote'><br>>
<br>>> - New template (set as default)
<br>> i'll give a look a t it :)
<br>>
<br>> /me just being curious :)
<br>>
<br>>> - (most)Third party libraries are updated to latest.
<br>> cool :)
<br>>
<br>>> - runs on php version 5.3
<br>> cool :)
<br>>
<br>>> - mcrypted all settings in header.inc.php if set
<br>> ?
</div>If mcrypt is installed and set to "true" - the db-name/db-user/db-password is
<br>encrypted. Making it more secure.
<br><div class='shrinkable-quote'><br>>
<br>>> - Admin can set preferences on behalf of users
<br>> *very* cool
<br>>
<br>>> - working Interlink - links (two-ways) items across the system
<br>> *very* cool
<br>>
<br>>> - properly working install/uninstall.
<br>> :)
<br>>
<br>>> Other than that: massive fixes for ACL, LDAP, conversion of users
<br>>> handled as object (before:arrays), session handling and more...
<br>>> SOAP and XMLRPC is updated to latest and works as client and service -
<br>>> but the old services need attention.
<br>> ?
<br>>
<br>>> I recommend that we take it further from the current state rather than
<br>>> trying to merge back single fixes.
<br>> well i'm not all for this way of doing things. I know previous gigantic
<br>> merges from resight have been done and accepted but thats (imho) the
<br>> best way to create problems.
</div><br>This ones fixes all the problems induced by the previous mega-patch :)
<br>Also - it is tested - and runs in a production environment.
<br><br>(phpgwapi/setup/manual/preferences/property/sms)
<br><div class='shrinkable-quote'><br>>
<br>> i'd prefer to merge nice-featuire by nice-feature
<br>>
<br>>
<br>>> * Working modules(personal trunk):
<br>>>
<br>>> core
<br>>> phpgwapi
<br>>> setup
<br>>> addressbook
<br>>> admin
<br>>> calendar
<br>>> hrm
<br>>> manual
<br>>> messenger
<br>>> notes
<br>>> preferences
<br>>> (projects - well - kind of)
<br>>> property
<br>>> sms
<br>>> todo
<br>>>
<br>>> * system trunk:
<br>>> email might work(if configuration is correct): if it hangs - delete
<br>>> the menu-hook and restart apache
<br>> ?
<br>>
<br>> Could you explain more this case please ?
<br>>
<br>> Just so that i understand why deleting menu-hook could improve things :)
</div>It stops the process of trying to connect to the wrongly configured
<br>pop/imap-server when loading the menu.
<br>The email app is a weak spot...
<br>>
<br>>
<br>>> Regards
<br>>>
<br>>> Sigurd
<br>> thanks Sigurd for this *big* contributiuon. It's up to us *all* to work
<br>> and merge these features into reference repository :)
<br>>
<br>>
<br><br>Another coming feature (in a few weeks) is general support for jasper reports
<br><br>To make it easy to test - I have uploaded this version to:
<br><a href="http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_21.tar.gz" target="_top" rel="nofollow">http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_21.tar.gz</a><br><br>Keep in mind that you need pdo - and I recommend PostgreSQL 8.3 and above.
<br><br>Install all apps and try it:)
<br><br>Regards
<br><br>Sigurd
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26460883&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26460471Re: IMPORTANT : SVN Structure change (Was Re: Who wants to play?)2009-11-21T13:22:06Z2009-11-21T13:22:06ZMaâtSigurd Nes wrote:
<div class='shrinkable-quote'><br>>>
<br>>> Thanks Sigrud.
<br>>>
<br>>> Glad to see you have started to put new things into your "personal"
<br>>> repository.
<br>>>
<br>>> Hope you'll find a little bit of time to explain quickly the big
<br>>> differences between each base trunk app and your work so that we know
<br>>> what could be looked at for later merging :)
<br>>>
<br>>
<br>> I'm done - Take it for a spin :)
</div>:)
<br><br>> The main difference are
<br>> - That db-abstraction is converted to pdo (faster and more secure) -
<br>> and that innodb is default for Mysql (to support transactions).
<br>> The db-object supports db-cloning - which I really really need - so
<br>> please don't remove it.
<br>In you personal repository *nobody* except you is supposed to play :
<br>you're your own master. If you don't remove it then it will not be
<br>removed (not by me whatever).
<br><br>but till the feature is considered fool-proof, suited for stable
<br>release, tested against regressions and accepted by all the coordinators
<br>team it's merge into base repository could be delayed
<br><br>please do not consider this as a personal offence... it's just paranoïa :)
<br><br><br>> - New template (set as default)
<br>i'll give a look a t it :)
<br><br>/me just being curious :)
<br><br>> - (most)Third party libraries are updated to latest.
<br>cool :)
<br><br>> - runs on php version 5.3
<br>cool :)
<br><br>> - mcrypted all settings in header.inc.php if set
<br>?
<br><br>> - Admin can set preferences on behalf of users
<br>*very* cool
<br><br>> - working Interlink - links (two-ways) items across the system
<br>*very* cool
<br><br>> - properly working install/uninstall.
<br>:)
<br><br>> Other than that: massive fixes for ACL, LDAP, conversion of users
<br>> handled as object (before:arrays), session handling and more...
<br>> SOAP and XMLRPC is updated to latest and works as client and service -
<br>> but the old services need attention.
<br>?
<br><br>> I recommend that we take it further from the current state rather than
<br>> trying to merge back single fixes.
<br>well i'm not all for this way of doing things. I know previous gigantic
<br>merges from resight have been done and accepted but thats (imho) the
<br>best way to create problems.
<br><br>i'd prefer to merge nice-featuire by nice-feature
<br><br><div class='shrinkable-quote'><br>>
<br>> * Working modules(personal trunk):
<br>>
<br>> core
<br>> phpgwapi
<br>> setup
<br>> addressbook
<br>> admin
<br>> calendar
<br>> hrm
<br>> manual
<br>> messenger
<br>> notes
<br>> preferences
<br>> (projects - well - kind of)
<br>> property
<br>> sms
<br>> todo
<br>>
<br>> * system trunk:
<br>> email might work(if configuration is correct): if it hangs - delete
<br>> the menu-hook and restart apache
</div>?
<br><br>Could you explain more this case please ?
<br><br>Just so that i understand why deleting menu-hook could improve things :)
<br><br><br>> Regards
<br>>
<br>> Sigurd
<br>thanks Sigurd for this *big* contributiuon. It's up to us *all* to work
<br>and merge these features into reference repository :)
<br><br>Regards,
<br><br>Maat
<br><br><br><br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26460471&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26460278Re: IMPORTANT : SVN Structure change (Was Re: Who wants to play?)2009-11-21T12:59:42Z2009-11-21T12:59:42ZSigurd NesMaât wrote:
<div class='shrinkable-quote'><br>> Sigurd Nes wrote:
<br>>> Maât wrote:
<br>>>> Maât wrote:
<br>>>>> to get a working copy from there you just need to checkout this url
<br>>>>> with subversion (or any graphical svn client like tortoise) :
<br>>>>> <a href="http://svn.savannah.gnu.org/svn/phpgroupware/core/trunk" target="_top" rel="nofollow">http://svn.savannah.gnu.org/svn/phpgroupware/core/trunk</a><br>>>>>
<br>>>>> -- branches : the various stable (and some of them outdated)
<br>>>>> branches...
<br>>>>> for example you'll fint there the branch dedicated to current stable
<br>>>>> versions 0.9.16.xxx
<br>>>>>
<br>>>>> the here above stable branch name is "branch_0_9_16" i tried to
<br>>>>> normalize all branch names ( branch_0_9_10 branch_0_9_12 branch_0_9_14
<br>>>>> branch_0_9_16...)
<br>>>>>
<br>>>>> to get a working copy from there you just need to checkout this url
<br>>>>> with subversion (or any graphical svn client like tortoise) :
<br>>>>> <a href="http://svn.savannah.gnu.org/svn/phpgroupware/core/branches/branch_0_9_16" target="_top" rel="nofollow">http://svn.savannah.gnu.org/svn/phpgroupware/core/branches/branch_0_9_16</a><br>>>>>
<br>>>>>
<br>>> I works
<br>>>
<br>>> Here is a howto on setting svn:externals
<br>>> <a href="http://blog.kowalczyk.info/article/Short-tutorial-on-svn-propset-for-svnexternals-p.html" target="_top" rel="nofollow">http://blog.kowalczyk.info/article/Short-tutorial-on-svn-propset-for-svnexternals-p.html</a><br>>>
<br>>>
<br>>> Regards
<br>>>
<br>>> Sigurd
<br>>
<br>> Thanks Sigrud.
<br>>
<br>> Glad to see you have started to put new things into your "personal"
<br>> repository.
<br>>
<br>> Hope you'll find a little bit of time to explain quickly the big
<br>> differences between each base trunk app and your work so that we know
<br>> what could be looked at for later merging :)
<br>>
</div><br>I'm done - Take it for a spin :)
<br><br>The main difference are
<br>- That db-abstraction is converted to pdo (faster and more secure) - and that
<br>innodb is default for Mysql (to support transactions).
<br>The db-object supports db-cloning - which I really really need - so please don't
<br>remove it.
<br>- New template (set as default)
<br>- (most)Third party libraries are updated to latest.
<br>- runs on php version 5.3
<br>- mcrypted all settings in header.inc.php if set
<br>- Admin can set preferences on behalf of users
<br>- working Interlink - links (two-ways) items across the system
<br>- properly working install/uninstall.
<br><br><br>Other than that: massive fixes for ACL, LDAP, conversion of users handled as
<br>object (before:arrays), session handling and more...
<br>SOAP and XMLRPC is updated to latest and works as client and service - but the
<br>old services need attention.
<br><br>I recommend that we take it further from the current state rather than trying to
<br>merge back single fixes.
<br><br>* Working modules(personal trunk):
<br><br>core
<br>phpgwapi
<br>setup
<br>addressbook
<br>admin
<br>calendar
<br>hrm
<br>manual
<br>messenger
<br>notes
<br>preferences
<br>(projects - well - kind of)
<br>property
<br>sms
<br>todo
<br><br>* system trunk:
<br>email might work(if configuration is correct): if it hangs - delete the
<br>menu-hook and restart apache
<br><br>Regards
<br><br>Sigurd
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26460278&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26460034Re: Future ... and Poll2009-11-21T12:36:38Z2009-11-21T12:36:38ZMaâtChris Weiss wrote:
<br>> On Thu, Nov 19, 2009 at 1:38 AM, Maât <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26460034&i=0" target="_top" rel="nofollow">maat@...</a>> wrote:
<br>>
<br>>> we could also imagine data synchronisation between wikis pages (or
<br>>> groups of pages) or synchronization between knowledge bases
<br>>>
<br>>
<br>> something like <a href="http://semantic-mediawiki.org/wiki/Semantic_MediaWiki" target="_top" rel="nofollow">http://semantic-mediawiki.org/wiki/Semantic_MediaWiki</a> ?
<br>>
<br>>
<br>i must admit that the iddea of a semantic groupware is really sexy :)
<br><br>this could be the start point of something really new and really different !
<br><br><br><br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26460034&i=1" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26459779Re: IMPORTANT : SVN Structure change (Was Re: Who wants to play?)2009-11-21T12:04:19Z2009-11-21T12:04:19ZMaâtSigurd Nes wrote:
<div class='shrinkable-quote'><br>> Maât wrote:
<br>>> Maât wrote:
<br>>>> to get a working copy from there you just need to checkout this url
<br>>>> with subversion (or any graphical svn client like tortoise) :
<br>>>> <a href="http://svn.savannah.gnu.org/svn/phpgroupware/core/trunk" target="_top" rel="nofollow">http://svn.savannah.gnu.org/svn/phpgroupware/core/trunk</a><br>>>>
<br>>>> -- branches : the various stable (and some of them outdated)
<br>>>> branches...
<br>>>> for example you'll fint there the branch dedicated to current stable
<br>>>> versions 0.9.16.xxx
<br>>>>
<br>>>> the here above stable branch name is "branch_0_9_16" i tried to
<br>>>> normalize all branch names ( branch_0_9_10 branch_0_9_12 branch_0_9_14
<br>>>> branch_0_9_16...)
<br>>>>
<br>>>> to get a working copy from there you just need to checkout this url
<br>>>> with subversion (or any graphical svn client like tortoise) :
<br>>>> <a href="http://svn.savannah.gnu.org/svn/phpgroupware/core/branches/branch_0_9_16" target="_top" rel="nofollow">http://svn.savannah.gnu.org/svn/phpgroupware/core/branches/branch_0_9_16</a><br>>>>
<br>>>>
<br>>
<br>> I works
<br>>
<br>> Here is a howto on setting svn:externals
<br>> <a href="http://blog.kowalczyk.info/article/Short-tutorial-on-svn-propset-for-svnexternals-p.html" target="_top" rel="nofollow">http://blog.kowalczyk.info/article/Short-tutorial-on-svn-propset-for-svnexternals-p.html</a><br>>
<br>>
<br>> Regards
<br>>
<br>> Sigurd
</div><br>Thanks Sigrud.
<br><br>Glad to see you have started to put new things into your "personal"
<br>repository.
<br><br>Hope you'll find a little bit of time to explain quickly the big
<br>differences between each base trunk app and your work so that we know
<br>what could be looked at for later merging :)
<br><br>/me very happy to see new commit logs commit logs appear :)
<br><br>Maat
<br><br><br><br><br><br><br><br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26459779&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26431274Re: IMPORTANT : SVN Structure change (Was Re: Who wants to play?)2009-11-19T10:14:38Z2009-11-19T10:14:38ZSigurd NesMaât wrote:
<div class='shrinkable-quote'><br>> Maât wrote:
<br>>> PART FOR EVERYBODY WITHOUT COMMIT RIGHTS
<br>>> ################################################
<br>>>
<br>>> Svn repositories (not repository because i have splitted them) share a
<br>>> common root
<br>>>
<br>>> which is publicly available there :
<br>>>
<br>>> <a href="http://svn.savannah.gnu.org/svn/phpgroupware/" target="_top" rel="nofollow">http://svn.savannah.gnu.org/svn/phpgroupware/</a><br>>>
<br>>> under this root we have core, modules and misc :
<br>>>
<br>>> ** core : the repository everybody (betatesters, bug hunters, svn loging
<br>>> users) will want to checkout
<br>>>
<br>>> under core we have :
<br>>> ------------------------
<br>>>
<br>>> -- trunk : the last (hopefully fast) moving codebase with the last
<br>>> exciting features (and currently the greatest number of bugs we want to
<br>>> get rid of)
<br>>>
<br>>> to get a working copy from there you just need to checkout this url
<br>>> with subversion (or any graphical svn client like tortoise) :
<br>>> <a href="http://svn.savannah.gnu.org/svn/phpgroupware/core/trunk" target="_top" rel="nofollow">http://svn.savannah.gnu.org/svn/phpgroupware/core/trunk</a><br>>>
<br>>> -- branches : the various stable (and some of them outdated) branches...
<br>>> for example you'll fint there the branch dedicated to current stable
<br>>> versions 0.9.16.xxx
<br>>>
<br>>> the here above stable branch name is "branch_0_9_16" i tried to
<br>>> normalize all branch names ( branch_0_9_10 branch_0_9_12 branch_0_9_14
<br>>> branch_0_9_16...)
<br>>>
<br>>> to get a working copy from there you just need to checkout this url
<br>>> with subversion (or any graphical svn client like tortoise) :
<br>>> <a href="http://svn.savannah.gnu.org/svn/phpgroupware/core/branches/branch_0_9_16" target="_top" rel="nofollow">http://svn.savannah.gnu.org/svn/phpgroupware/core/branches/branch_0_9_16</a><br>>>
<br>> ----8<----
<br>>> Thanks all and apologies for this really long mail
<br>>>
<br>>> Maât
<br>>>
<br>>
<br>> Can someone test this and give me feedback ?
<br>>
</div><br>I works
<br><br>Here is a howto on setting svn:externals
<br><a href="http://blog.kowalczyk.info/article/Short-tutorial-on-svn-propset-for-svnexternals-p.html" target="_top" rel="nofollow">http://blog.kowalczyk.info/article/Short-tutorial-on-svn-propset-for-svnexternals-p.html</a><br><br>Regards
<br><br>Sigurd
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26431274&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26427605Re: Future ... and Poll2009-11-19T06:41:05Z2009-11-19T06:41:05ZChris Weiss-2On Thu, Nov 19, 2009 at 1:38 AM, Maât <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26427605&i=0" target="_top" rel="nofollow">maat@...</a>> wrote:
<br>> we could also imagine data synchronisation between wikis pages (or
<br>> groups of pages) or synchronization between knowledge bases
<br><br>something like <a href="http://semantic-mediawiki.org/wiki/Semantic_MediaWiki" target="_top" rel="nofollow">http://semantic-mediawiki.org/wiki/Semantic_MediaWiki</a> ?
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26427605&i=1" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26421855Re: Future ... and Poll2009-11-18T23:38:01Z2009-11-18T23:38:01ZMaâtChris Weiss wrote:
<div class='shrinkable-quote'><br>>>> - do you think that having a groupware able to communicate with other
<br>>>> groupware is important ?
<br>>>>
<br>>>>
<br>>> yes this also is a killer feature that no other groupware offer atm
<br>>>
<br>>
<br>> this depends on what you mean by "communicate". From where I'm
<br>> standing, most serious groupware systems can communicate with other
<br>> systems.
<br>>
<br>> as a use-case example, my vendor sends me a meeting request, I accept
<br>> and it gets added to my calendar and he gets a response confirming I
<br>> accepted. This works now, I've been a part of it with Exchange on one
<br>> side and gmail/gcal on the other. I would expect any groupware that
<br>> supports email and iCal would work too.
<br>>
<br>> if you mean something beyond that, like calendar and
<br>> addressbook/contacts sharing, some groupware's also already do this.
<br>> things like LDAP and iCal make it rather easy.
<br>>
<br>> At work we're using Kerio, and it goes as far as to provide a link to
<br>> users so they can let others subscribe to their Kerio calendar from
<br>> anything that supports iCal. it's read-only, but it's still
<br>> communication.
<br>>
</div>Yep... you're right i must explain what i meant.
<br><br>when i want to plan a meeting some groupwares allow to check local
<br>people availability... but for other not locally known pople this is not
<br>possible.
<br><br>groupwares able to communicate with each other could ask for
<br>availability to have a meeting distributed planner that even notes dones
<br>not offer.
<br><br>(that would also need to control what data you want to make available to
<br>what groupware)
<br><br>same thing for addressbook : communication between groupwares would
<br>allow to automatically complete fields clicking on retrieve/sync data
<br>from reference groupware
<br><br>that could also be true for ged : sharing documentss across several
<br>groupwares and making relations between these documents
<br><br>same thing for tasks... we could have a project done by several
<br>compagnies each having to do a part of the job but tasks obviously would
<br>be inter-dependant
<br><br>having dependancy relations between tasks distributed on several
<br>groupwares would allow a better co-operation
<br><br>that sorts of "communication" between groupwares today are offered by no
<br>groupware afaik
<br><br>we could also imagine data synchronisation between wikis pages (or
<br>groups of pages) or synchronization between knowledge bases
<br><br><br><br><br><br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26421855&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26424146Re: Future ... and Poll2009-11-18T23:23:31Z2009-11-18T23:23:31ZOlivier BergerLe jeudi 19 novembre 2009 à 00:52 +0100, Maât a écrit :
<br><br>> i'm using phpGroupWare as a basis for ged
<br><br>for non-french speakers : GED == "Gestion Electronique de Documents",
<br>i.e Documents management system (ECM ?) ;)
<br><br>My two cents as a lurker.
<br><br>PS: Stabilizing a stable and secure version would be an important
<br>concern, IMHO, i.e. Distribution packagers need to be able to stabilize
<br>an official update of their packages that will no-longer be including
<br>"floating" patches that were not part officially of a major release from
<br>you guys ;)
<br>--
<br>Olivier BERGER <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26424146&i=0" target="_top" rel="nofollow">olivier.berger@...</a>>
<br><a href="http://www-public.it-sudparis.eu/~berger_o/" target="_top" rel="nofollow">http://www-public.it-sudparis.eu/~berger_o/</a> - OpenPGP-Id: 1024D/6B829EEC
<br>Ingénieur Recherche - Dept INF
<br>Institut TELECOM, SudParis (<a href="http://www.it-sudparis.eu/" target="_top" rel="nofollow">http://www.it-sudparis.eu/</a>), Evry (France)
<br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26424146&i=1" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26420006Re: Future ... and Poll2009-11-18T19:51:55Z2009-11-18T19:51:55ZChris Weiss-2>> - do you think that having a groupware able to communicate with other
<br>>> groupware is important ?
<br>>>
<br>> yes this also is a killer feature that no other groupware offer atm
<br><br>this depends on what you mean by "communicate". From where I'm
<br>standing, most serious groupware systems can communicate with other
<br>systems.
<br><br>as a use-case example, my vendor sends me a meeting request, I accept
<br>and it gets added to my calendar and he gets a response confirming I
<br>accepted. This works now, I've been a part of it with Exchange on one
<br>side and gmail/gcal on the other. I would expect any groupware that
<br>supports email and iCal would work too.
<br><br>if you mean something beyond that, like calendar and
<br>addressbook/contacts sharing, some groupware's also already do this.
<br>things like LDAP and iCal make it rather easy.
<br><br>At work we're using Kerio, and it goes as far as to provide a link to
<br>users so they can let others subscribe to their Kerio calendar from
<br>anything that supports iCal. it's read-only, but it's still
<br>communication.
<br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26420006&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26418016Re: Future ... and Poll2009-11-18T15:52:27Z2009-11-18T15:52:27ZMaât-2Caeies wrote:
<br>> Hi all,
<br>>
<br>> As some of you already know, I'm officially the new phpGroupWare
<br>> maintainer from the FSF point of view.
<br>No comment on that. For the while we have more urgent questions to deal
<br>with... first of all : can we give a new life to this project :)
<br><br>> I want to thanks Dave / skwashd
<br>> for all the work he has made as the FSF maintainer of this project.
<br>>
<br>agreed :)
<br><br>> We have recently hardly discuss about the death of the project. It seems
<br>> that we want to try to make it alive :).
<br>>
<br>/me votes for life rather than death :)
<br><br><br>> Maat did a good job by reworking the svn tree, making it easier to
<br>> understand. Thanks for that.
<br>>
<br>:)
<br><br>Now a single svn checkout allows people to have a working copy ready to
<br>test or code.
<br><br>Next i'll publish a quick howto get started on phpGW with Eclipse PDT
<br>(Eclipse IDE for PHP with many cool features that make phpGroupWare
<br>hacking and debugging easier)
<br><br><br>> Sigurd seems to have things to commit in his branch (btw is this on the
<br>> =2E16 base or .18 ?). I'm waiting for this to speak about that after.
<br>>
<br>Sigurd can work in his brand new dedicated repository so that we can
<br>cherry pick cool features and commit them into base repository :)
<br><br>> I don't want to start a "blabla" thread. But I want to know what you
<br>> think about the real added values of phpGW :
<br>> - do you think that the building of custom module is important ?
<br>>
<br>It's important to let this possibility imho.
<br>Though we cannot expect people to start coding new apps on our base
<br>before a new stable and sexy version is published.
<br><br><br>> - do you think that having a high level API is important ?
<br>>
<br>Yes also
<br><br>> - do you think that the intermodule communication is important ?
<br>>
<br>It's a killer feature that no other groupware offer atm
<br><br><br>> - do you think that the number of proposed module is important ?
<br>>
<br>no
<br><br><br>> - do you think that having an easy setup is important
<br>>
<br>yes * 1000
<br><br>> - do you think that having a groupware able to communicate with other
<br>> groupware is important ?
<br>>
<br>yes this also is a killer feature that no other groupware offer atm
<br><br>and that would perhaps allow to create things like groupware based
<br>social networks without central node with the ability for people to well
<br>control their personal datas :)
<br><br><br>> - do you think that having a groupware able to communicate with
<br>> specialized devices is important ?
<br>>
<br>for me no but i know many people cannot live without that
<br><br>and we have jonhang GSoC work for that now :)
<br><br><br>> - do you think that being able to easily brand phpgroupware is important=
<br>> ?
<br>>
<br>what d'you mean there ?
<br><br>> - what kind of applications are important ? why ?
<br>>
<br>Depends on the user need ... i proposed long ago to make several flavors
<br>of phpGroupWare with various sets of applications optimised for specific
<br>purposes.
<br><br>-- personal communicationware : webmail + calendar + notes
<br>-- project management groupware (tasks + tts + ged)
<br>-- facilities management ( property + ....)
<br><br>i think we can find others classical usage patterns
<br><br>that would make us the first flavored GroupWare
<br><div class='shrinkable-quote'><br>> - other things that I forgot ?
<br>>
<br>> Please, keep in mind that we have the following things already well
<br>> running :
<br>> -> google apps (shared calendar, shared documents, mail, ...) and their
<br>> concurrent.
<br>> -> API : Zend Framework, symfony, cakePHP, ...
<br>> -> other groupwares in java / php / python / whatever ...
<br>>
<br>> So, in short : where can we add value to our project, what are our
<br>> strengths for YOU developers ? (users are welcome to give their feedback
<br>> too :).
<br>>
<br>> Beeing free software is important for all of US (at least I hope !). But
<br>> we need to go ahead, rebuilding a strong community of contributing
<br>> developer and not only users.
<br>>
</div>i'm using phpGroupWare as a basis for ged but the need is raising for a
<br>really good task/project manager with module linking with email for
<br>notifications and ged for documents related to the tasks
<br><br>perhaps a link with calendar for gant displaying would be great too
<br>(later because Gantt displaying is really a difficult thing to do with a
<br>web app)
<br><br>i think we can at least make phpGroupWare a leading project-management
<br>dedicated groupware... wich would allow us to attract small companies as
<br>"customers"
<br><br><br><br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26418016&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26410436Future ... and Poll2009-11-18T07:54:42Z2009-11-18T07:54:42ZCaeies-2Hi all,
<br><br>As some of you already know, I'm officially the new phpGroupWare
<br>maintainer from the FSF point of view. I want to thanks Dave / skwashd
<br>for all the work he has made as the FSF maintainer of this project.
<br><br>We have recently hardly discuss about the death of the project. It seems
<br>that we want to try to make it alive :).
<br><br>Maat did a good job by reworking the svn tree, making it easier to
<br>understand. Thanks for that.
<br><br>Sigurd seems to have things to commit in his branch (btw is this on the
<br>=2E16 base or .18 ?). I'm waiting for this to speak about that after.
<br><br>I don't want to start a "blabla" thread. But I want to know what you
<br>think about the real added values of phpGW :
<br> - do you think that the building of custom module is important ?
<br> - do you think that having a high level API is important ?
<br> - do you think that the intermodule communication is important ?
<br> - do you think that the number of proposed module is important ?
<br> - do you think that having an easy setup is important
<br> - do you think that having a groupware able to communicate with other
<br>groupware is important ?
<br> - do you think that having a groupware able to communicate with
<br>specialized devices is important ?
<br> - do you think that being able to easily brand phpgroupware is important=
<br> ?
<br> - what kind of applications are important ? why ?
<br> - other things that I forgot ?
<br><br>Please, keep in mind that we have the following things already well
<br>running :
<br> -> google apps (shared calendar, shared documents, mail, ...) and their
<br>concurrent.
<br> -> API : Zend Framework, symfony, cakePHP, ...
<br> -> other groupwares in java / php / python / whatever ...
<br><br>So, in short : where can we add value to our project, what are our
<br>strengths for YOU developers ? (users are welcome to give their feedback
<br>too :).
<br><br>Beeing free software is important for all of US (at least I hope !). But
<br>we need to go ahead, rebuilding a strong community of contributing
<br>developer and not only users.
<br><br><br><br /> <br />_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26410436&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>signature.asc</strong> (268 bytes) <a href="http://old.nabble.com/attachment/26410436/0/signature.asc" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>tag:old.nabble.com,2006:post-26409654Re: IMPORTANT : SVN Structure change (Was Re: Who wants to play?)2009-11-18T07:07:15Z2009-11-18T07:07:15ZMaâtCaeies wrote:
<div class='shrinkable-quote'><br>> Hi all,
<br>>
<br>> Maât a écrit :
<br>>
<br>>> Maât wrote:
<br>>>
<br>>>> PART FOR EVERYBODY WITHOUT COMMIT RIGHTS
<br>>>> ################################################
<br>>>>
<br>>>>
<br>>
<br>>
<br>>>> Thanks all and apologies for this really long mail
<br>>>>
<br>>>> Maât
<br>>>>
<br>>>>
<br>>> Can someone test this and give me feedback ?
<br>>>
<br>>>
<br>>
<br>> Looks working for me. BeAware of savannah nickname with mixed case !
<br>>
<br>> Regards,
<br>>
<br>> Caeies
<br>>
</div>thank you Caeies :)
<br><br><br><br><br>_______________________________________________
<br>phpGroupWare-developers mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26409654&i=0" target="_top" rel="nofollow">phpGroupWare-developers@...</a>
<br><a href="http://lists.gnu.org/mailman/listinfo/phpgroupware-developers" target="_top" rel="nofollow">http://lists.gnu.org/mailman/listinfo/phpgroupware-developers</a><br><p>From forum: <a href="http://old.nabble.com/DotGNU---phpGroupWare---Dev-f1564.html" embed="fixTarget[1564]" target="_top" >DotGNU - phpGroupWare - Dev</a></p>