Who wants to play?

I dont think there is enough momentum to essentially re-launch the
project as your intending.
At least I am not convinced at this point, and if there was a re-launch
I would probably prefer to be involved. I do have some time to code, but
I just dont think theres a sufficient need atm.

I will keep watching, and if there is enough energy behind this I may
get convinced.

Dan
aka Seek3r

Post by Sigurd Nes
Hi all,
It looks by now that there is only Maât and me that are interested in actively
keeping on with the project (I could be wrong...)
I think we should make up a status so we can take it from there.
All willing to participate: please state your business and what role you want to
play.
I think a 10 days period should be sufficient for people to sign up for the sequel.
Regards
Sigurd
_______________________________________________
coordinators mailing list
http://lists.phpgroupware.org/mailman/listinfo/coordinators

--
Dan Kuykendall (aka Seek3r)
http://www.mightyseek.com

In God we trust, all others we virus scan.
Programmer - an organism that turns coffee into software.

Sigurd Nes

2009-10-11 18:46:52 UTC

Your active involvement would be great.

In Norway we have this Facilities Management project based on phpGroupWare going
that will live for many years to come.
This project is for professionals and is funded as a serie of collaborating
sub-projects where each gain from each other.
This is organized more like the "Cathedral".
I think it would be beneficial to also have access to the "Bazaar" - and that is
why I try to back-port the results to the original project (along with the
appreciation of the fact that we wouldn't have got this far without its origin).

New developers coming into the project usually has three complaints:
1) Lack of documentation
2) They wish for a more object-oriented approach (more objects, less arrays) -
and of course: new apps are coded this way.
3) The template system(s) is not their favorite.

Still - we have a lot of energy and resources - that I feel would get to an even
better outcome if we could revitalize the original project and collaborate in a
symbiotic fashion.

Regards

Sigurd

Post by Dan Kuykendall
I dont think there is enough momentum to essentially re-launch the
project as your intending.
At least I am not convinced at this point, and if there was a re-launch
I would probably prefer to be involved. I do have some time to code, but
I just dont think theres a sufficient need atm.
I will keep watching, and if there is enough energy behind this I may
get convinced.
Dan
aka Seek3r

Maât

2009-10-11 21:09:31 UTC

Hi Dan,

Glad to see you're watching.

Indeed re-launching this project would need some energy but we have a
rather big code base which can be considered as a problem because
updating it woill need more work.

But it can also be considered as a chance : because it gives students
the opportunity to learn important things about php coding and big php
software architectures.

Digging into this code (and Dave advice) helped me getting better with
php coding

We could put lights on this and attract a fair amount of new coders
willing to learn and help

That would still need a heavy involvement from a hanful of people ready
to drive newcomers and help them stepping in. And a continuous
communication flow from "the project" to make the wold know that phpGW
is moving again

Going this way would not need a big bunch of php masters i think...

Maât

2009-11-05 13:26:20 UTC

Post by Dan Kuykendall
I will keep watching, and if there is enough energy behind this I may
get convinced.
Dan
aka Seek3r

Dr. Christian Böttger

2009-11-05 13:42:13 UTC

Fine with me ...

Post by Dan Kuykendall
I will keep watching, and if there is enough energy behind this I may
get convinced.
Dan
aka Seek3r

Well seems that nobody's ready to take the first step
May i try to clean svn tree and publish a howto check-out and get
started with a few mouse click ?
as we are not so many obviously we can only hope to restart with slow
moves and tiny steps
_______________________________________________
coordinators mailing list
http://lists.phpgroupware.org/mailman/listinfo/coordinators

--
Dr. Christian Böttger (Dipl.Phys.) DF5OP Open Source Broker
ph.: +49.5173.9249744 | fax: +49.5173.925769 | Skype: c.boettger
Bentestraße 10 / 31311 Uetze / Germany
E-Mail: work ***@Boettger-consulting.de
E-Mail: Home ***@Boettger.cc
WWW: http://www.boettger-consulting.de/ http://www.boettger.cc/

Xing: http://www.xing.com/profile/Christian_Boettger2
LinkedIn: https://www.linkedin.com/in/christianboettger
https://www.linkedin.com/ppl/webprofile?action=vmi&id=1447968&trk=ppro_viewmore

Maât

2009-11-09 11:49:23 UTC

i think we can create a per coder sub-repository so that you can publish
your code
people will have the choice to checkout from your base or from default
base, compare codes and work on both
then we can step by step merge features from your base to default and
have by the end both a clean code and a clean changelog for default base :)
that will allow everyone to go on without deadlock :)
Okay for that ?

I suppose so - that leaves only the license issue

Okay so : the per coder structure is now ready and follows the
core/module base svn architecture

so for you sigurd the "core" place is there (and empty well i created
just the trunk/tags/branches level) :

svn+ssh://***@svn.savannah.gnu.org/phpgroupware/people/sigurdne/core

and i also added an empty module repository for property in your tree
which is there :

svn+ssh://***@svn.savannah.gnu.org/phpgroupware/people/sigurdne/modules/property

you have also the trunk/tags/branches level created so that it's useable
just out of the box :)

for the remaining license issue i don't understand why there is a
problem with GPL v3

can someone explain please ?

Dave Hall

2009-11-09 12:13:21 UTC

Post by MaÃ¢t
for the remaining license issue i don't understand why there is a
problem with GPL v3
can someone explain please ?

Sigurd wants to import felamimail from eGroupWare - which depends on
PEAR code (which is PHP licensed code - read not GPLv2 or v3
compatible). His work around for the licensing issue is to play the
same game as eGroupWare by telling people to download the PHP licensed
code separately. This may actually constitute a GPL violation as there
is expert opinion around which suggests include/require in PHP
constitute static linking - regardless of if you distribute the code
with it or not.

Regardless of which license the project uses, I feel that it is totally
unacceptable for a GNU package to attempt skirt around the requirements
of the GPL in such a way.

In addition to this the FSF has already indicated (and communicated this
to Sigurd) that they would not support the project reverting to GPLv2
just so the project can use some GPLv2 only code.

Sigurd has been playing divisive games around licensing for years, first
it was suggesting using AGPL, then it was switching back to GPLv2. This
is one of the reasons why I stopped working on the project, having to
constantly deal with Sigurd and his stupid games. He may claim to be
ignorant of the above issues, but that is crap it has been explained to
him at length many times.

As someone else has already suggested, Sigurd is free to take the GPLv2
code, fork and start his own project, and so long as he complies with
the requirements of the GPL he is free to do as he wants.

Good luck to those who continue on with the project, I just hope you
have the patience and energy to deal with Sigurd and his games.

Cheers

Dave

Sigurd Nes

2009-11-09 12:26:55 UTC

Sent: 2009-11-09 13:13:21 CET
Subject: [phpGroupWare-developers] GPLv3 (was Who wants to play?)

Post by MaÃ¢t
for the remaining license issue i don't understand why there is a
problem with GPL v3
can someone explain please ?

Nope - that's a lie.

Sigurd has been playing divisive games around licensing for years, first
it was suggesting using AGPL, then it was switching back to GPLv2. This
is one of the reasons why I stopped working on the project, having to
constantly deal with Sigurd and his stupid games. He may claim to be
ignorant of the above issues, but that is crap it has been explained to
him at length many times.
As someone else has already suggested, Sigurd is free to take the GPLv2
code, fork and start his own project, and so long as he complies with
the requirements of the GPL he is free to do as he wants.
Good luck to those who continue on with the project, I just hope you
have the patience and energy to deal with Sigurd and his games.

Well - after Dave has left the tent - I sure all will calm down nicely :)

Regards

Sigurd

Sigurd Nes

2009-11-09 12:35:02 UTC

Sent: 2009-11-09 13:13:21 CET
Subject: [phpGroupWare-developers] GPLv3 (was Who wants to play?)

Post by MaÃ¢t
for the remaining license issue i don't understand why there is a
problem with GPL v3
can someone explain please ?

Btw: I can skip the felamimail application from being ported.
That should ease the pain.
The existing one (that does not use PEAR code) is still GPLv2 only.

Regards

Sigurd

Maât

2009-11-09 13:42:11 UTC

Sent: 2009-11-09 13:13:21 CET
Subject: [phpGroupWare-developers] GPLv3 (was Who wants to play?)

Post by MaÃ¢t
for the remaining license issue i don't understand why there is a
problem with GPL v3
can someone explain please ?

Btw: I can skip the felamimail application from being ported.
That should ease the pain.
The existing one (that does not use PEAR code) is still GPLv2 only.
Regards
Sigurd

I think you're wrong Sigurd :

felamimail either in our repository or in egw's is "version 2 or later" :)

/**************************************************************************\
* phpGroupWare - FeLaMiMail *
* http://www.phpgroupware.org *
* http://www.phpgw.de *
* http://www.linux-at-work.de *
* Written by Lars Kneschke [***@linux-at-work.de] *
* ----------------------------------------------- *
* This program is free software; you can redistribute it and/or modify it *
* under the terms of the GNU General Public License as published by the *
* Free Software Foundation; either version 2 of the License, or (at your *
* option) any later version. *
\**************************************************************************/

/**************************************************************************\
* eGroupWare - FeLaMiMail *
* http://www.egroupware.org *
* http://www.phpgw.de *
* http://www.linux-at-work.de *
* Written by Lars Kneschke [***@linux-at-work.de] *
* ----------------------------------------------- *
* This program is free software; you can redistribute it and/or modify it *
* under the terms of the GNU General Public License as published by the *
* Free Software Foundation; either version 2 of the License, or (at your *
* option) any later version. *
\**************************************************************************/

the PEAR part is perhaps more annoying (it sounds like a subtle experts
debate though)... but if the needed pear lib is not too complex we could
try to replace it ?

Maât

Benoit Hamet

2009-11-09 14:01:06 UTC

Hi all,

Sent: 2009-11-09 13:13:21 CET
Subject: [phpGroupWare-developers] GPLv3 (was Who wants to play?)

Post by MaÃ¢t
for the remaining license issue i don't understand why there is a
problem with GPL v3
can someone explain please ?

Btw: I can skip the felamimail application from being ported.
That should ease the pain.
The existing one (that does not use PEAR code) is still GPLv2 only.
Regards
Sigurd

felamimail either in our repository or in egw's is "version 2 or later" :)
/**************************************************************************\
* phpGroupWare - FeLaMiMail *
* http://www.phpgroupware.org *
* http://www.phpgw.de *
* http://www.linux-at-work.de *
* ----------------------------------------------- *
* This program is free software; you can redistribute it and/or modify it *
* under the terms of the GNU General Public License as published by the *
* Free Software Foundation; either version 2 of the License, or (at your *
* option) any later version. *
\**************************************************************************/
/**************************************************************************\
* eGroupWare - FeLaMiMail *
* http://www.egroupware.org *
* http://www.phpgw.de *
* http://www.linux-at-work.de *
* ----------------------------------------------- *
* This program is free software; you can redistribute it and/or modify it *
* under the terms of the GNU General Public License as published by the *
* Free Software Foundation; either version 2 of the License, or (at your *
* option) any later version. *
\**************************************************************************/
the PEAR part is perhaps more annoying (it sounds like a subtle experts
debate though)... but if the needed pear lib is not too complex we could
try to replace it ?

Well, rewriting something on top of http://swiftmailer.org/ could be an
option. If I understand all the questions and needs ...

I have asked to FSF an advice about the potential usage of the symfony
project or the zend framework. let see what they "officialy" think of it.

Btw, for me the debate on the code license is closed. it's GPLv3 or
later, as per recommended policy of the FSF / GNU Project. If we start
from scratch, we can then discuss the "right" license, still depending
on the FSF / GNU Project point of view.

I want to thank maat for his help building the new repositories, as well
as moving the debate on.

Regards,

Caeies.

Sigurd Nes

2009-11-09 14:51:48 UTC

Sent: 2009-11-09 14:42:11 CET
Subject: Re: [phpGroupWare coordinators] [phpGroupWare-developers] GPLv3 (was Who wants to play?)

Sent: 2009-11-09 13:13:21 CET
Subject: [phpGroupWare-developers] GPLv3 (was Who wants to play?)

Post by MaÃ¢t
for the remaining license issue i don't understand why there is a
problem with GPL v3
can someone explain please ?

Btw: I can skip the felamimail application from being ported.
That should ease the pain.
The existing one (that does not use PEAR code) is still GPLv2 only.
Regards
Sigurd

felamimail either in our repository or in egw's is "version 2 or later" :)

We are both wrong:
In egw's version there are files that are V2-only.
In our repository - all files are "version 2 or later".

I rest my case: as soon as there is an working alternative for the ported felamimail (for now I need it) - I will convert to GPLv3.

Regards

Sigurd

Maât

2009-11-09 15:01:17 UTC

Sent: 2009-11-09 14:42:11 CET
Subject: Re: [phpGroupWare coordinators] [phpGroupWare-developers] GPLv3 (was Who wants to play?)

Sent: 2009-11-09 13:13:21 CET
Subject: [phpGroupWare-developers] GPLv3 (was Who wants to play?)

Post by MaÃ¢t
for the remaining license issue i don't understand why there is a
problem with GPL v3
can someone explain please ?

Btw: I can skip the felamimail application from being ported.
That should ease the pain.
The existing one (that does not use PEAR code) is still GPLv2 only.
Regards
Sigurd

felamimail either in our repository or in egw's is "version 2 or later" :)

In egw's version there are files that are V2-only.
In our repository - all files are "version 2 or later".
I rest my case: as soon as there is an working alternative for the ported felamimail (for now I need it) - I will convert to GPLv3.
Regards
Sigurd

ok so i suggest start working in that direction : there is so much to be
done on the current code that we can start cleaning licenses headers
towards full "GPL v3 or later" now beacause it will take a rather long
time and during this slow cleaning process we can also work on a cool
email solution (wether felamimail-based or not) that fit your (and
hopefully not only your) needs

Maât

Caeies

2009-11-09 15:21:16 UTC

Hi all,

Sent: 2009-11-09 14:42:11 CET
Subject: Re: [phpGroupWare coordinators] [phpGroupWare-developers] GPLv3 (was Who wants to play?)

Sent: 2009-11-09 13:13:21 CET
Subject: [phpGroupWare-developers] GPLv3 (was Who wants to play?)

</snip for brievity>

Post by Sigurd Nes
Regards
Sigurd

most of licence headers are already gplv3 or later aware. This work was
done when the project had decided to use it ... There's perhaps some
missing headers, and in that case we should correct it.

I think sensible that all new stuff put in the official trunk, or that
want to be merged in the official trunk, should already have the gplv3
headers.

For the mail client, we need it.

Regards,

Caeies.

Maât

2009-11-09 16:10:19 UTC

Post by Sigurd Nes
Hi all,

Post by MaÃ¢t
ok so i suggest start working in that direction : there is so much to be
done on the current code that we can start cleaning licenses headers
towards full "GPL v3 or later" now beacause it will take a rather long
time and during this slow cleaning process we can also work on a cool
email solution (wether felamimail-based or not) that fit your (and
hopefully not only your) needs

most of licence headers are already gplv3 or later aware. This work was
done when the project had decided to use it ... There's perhaps some
missing headers, and in that case we should correct it.

after a deeper look in the code "most of" is a little bit optimistic ^^

there are thousands of remaining "gpl v2 or later" headers rather easy
to find... and a few more trickier cases with "exotic" formulation :/

----8<----

Post by Sigurd Nes
For the mail client, we need it.

agreed for the need of a nice webmail client :)

Sigurd Nes

2009-11-09 12:17:41 UTC

Sent: 2009-11-09 12:49:23 CET
Subject: Re: [phpGroupWare coordinators] [phpGroupWare-developers] Re: Who wants to play?

I suppose so - that leaves only the license issue

Okay so : the per coder structure is now ready and follows the
core/module base svn architecture
so for you sigurd the "core" place is there (and empty well i created
and i also added an empty module repository for property in your tree
you have also the trunk/tags/branches level created so that it's useable
just out of the box :)
for the remaining license issue i don't understand why there is a
problem with GPL v3
can someone explain please ?

It seems to work :)

The problem with GPLv3 is that it is not compatible with GPLv2 - and there is code in the system that is GPLv2-only.
It is normal to specify " either version 2 of the License, or (at your option) any later version" - but there is code where the "option" is left out.

Here is why we can stay on GPLv2 for the current trunk:
(GPLv3 is aimed to address hardware issues)

http://gplv3.fsf.org/rms-why.html

Don't get me wrong: I am all for moving to GPLv3 on the next framework.

Benoit: Have you had the time to asses the GPLv2 vs GPLv3 ?

Regards

Sigurd

Maât

2009-11-09 13:06:57 UTC

----8<----

Post by MaÃ¢t
for the remaining license issue i don't understand why there is a
problem with GPL v3
can someone explain please ?

----8<----

Post by Sigurd Nes
The problem with GPLv3 is that it is not compatible with GPLv2 - and there is code in the system that is GPLv2-only.
It is normal to specify " either version 2 of the License, or (at your option) any later version" - but there is code where the "option" is left out.
(GPLv3 is aimed to address hardware issues)
http://gplv3.fsf.org/rms-why.html
Don't get me wrong: I am all for moving to GPLv3 on the next framework.

So if we just hunt GPLv2 only code and either :
-- get the autorization to use GPLv3 from the authors
-- replace by something else GPL v3 compatible

we'll have the problem sorted ?

Maât

2009-11-11 12:40:01 UTC

Post by MaÃ¢t
Okay so : the per coder structure is now ready and follows the
core/module base svn architecture
so for you sigurd the "core" place is there (and empty well i created
and i also added an empty module repository for property in your tree
you have also the trunk/tags/branches level created so that it's useable

----8<----

Post by Sigurd Nes
It seems to work :)

----8<----

Next step in progress : changing structure so that a single checkout is
needed to get started

Please mark this mail because the following info are really important to
get started.

PART FOR EVERYBODY WITHOUT COMMIT RIGHTS
################################################

Svn repositories (not repository because i have splitted them) share a
common root

which is publicly available there :

http://svn.savannah.gnu.org/svn/phpgroupware/

under this root we have core, modules and misc :

** core : the repository everybody (betatesters, bug hunters, svn loging
users) will want to checkout

under core we have :
------------------------

-- trunk : the last (hopefully fast) moving codebase with the last
exciting features (and currently the greatest number of bugs we want to
get rid of)

to get a working copy from there you just need to checkout this url
with subversion (or any graphical svn client like tortoise) :
http://svn.savannah.gnu.org/svn/phpgroupware/core/trunk

-- branches : the various stable (and some of them outdated) branches...
for example you'll fint there the branch dedicated to current stable
versions 0.9.16.xxx

the here above stable branch name is "branch_0_9_16" i tried to
normalize all branch names ( branch_0_9_10 branch_0_9_12 branch_0_9_14
branch_0_9_16...)

to get a working copy from there you just need to checkout this url
with subversion (or any graphical svn client like tortoise) :
http://svn.savannah.gnu.org/svn/phpgroupware/core/branches/branch_0_9_16

if you browse core trunk or one of the core branches in core you'll find
they are nearly empty : don't panic this is normal... once you begin the
check out svn will get all the needed phpgw modules which are located in
modules root dir (nice transition for the following subject)

** modules : a root dir located just aside core... modules contains one
repository (each with svn trunk / tags / branches canocical structure )
per module... you'll see there addressbook, notes, todo, property and
some more

for each module repository we have :
------------------------------------------

-- trunk : the last (hopefully fast) moving codebase with the last
exciting features (and currently the greatest number of bugs we want to
get rid of)

-- branches : the various stable (and some of them outdated) branches...
for example you'll fint there the branch dedicated to current stable
versions 0.9.16.xxx

the here above stable branch name is "branch_0_9_16" i tried to
normalize all branch names ( branch_0_9_10 branch_0_9_12 branch_0_9_14
branch_0_9_16...)

modules trunks are linked to core trunk through a subversion link system
using the svn property svn:externals

and modules branches are each linked to the appropriate core branch (
modules branches "branch_0_9_16" with core branch "branch_0_9_16" for
example) alike

most of the time you won't need to play with externals because most of
the phpgw modules are already linked

if you wan to get another module (let's take we are working in trunks)
just edit the svn:externals property of your working copy

it looks like this :

addressbook
http://svn.savannah.gnu.org/svn/phpgroupware/modules/addressbook/trunk
admin http://svn.savannah.gnu.org/svn/phpgroupware/modules/admin/trunk
calendar http://svn.savannah.gnu.org/svn/phpgroupware/modules/calendar/trunk
email http://svn.savannah.gnu.org/svn/phpgroupware/modules/email/trunk

if you wan to add for example the module stocks juste add a line like this
stocks http://svn.savannah.gnu.org/svn/phpgroupware/modules/stocks/trunk

and update :)

The property svn:externals will appear as modified in svn status but as
http://svn.savannah.gnu.org/svn repositories are read-only you'll nver
break anything even if you try a svn commit :)

PART FOR APP MAINTAINERS WITH COMMIT RIGHTS
##################################################

This part is also for people interrested in becomin' maintainers :)

the root for your app must be changed so that you can commit without
savannah rejecting you

So in svn:externals you have the to edit the line of your app changing
the url root http://svn.savannah.gnu.org/svn/phpgroupware with
svn+ssh://svn.savannah.gnu.org/phpgroupware or
svn+ssh://***@svn.savannah.gnu.org/phpgroupware

and run a svn update on your working copy : you app will be updated and
the commits will be accepted by savannah

if you maintain severas apps just change each needed line in svn:externals

WARNING : Double check the coherence of svn:externals urls... if you
check out a working copy for 0.9.16.X branch and target the trunk of
your app with svn:externals there are very few chances to see it work :)

PART FOR PHPGW MAINTAINERS WITH COMMIT RIGHTS
######################################################

This part is also for people interrested in becomin' maintainers :)

if you need to :
-- patch phpgw root doc
-- patch one of the few files located in core repository
-- create new branches (for example the waited branch_0_9_18)
-- publish releases (for that we need to play with tags... that will be
for an other kilometer-long mail :) )

then you need to commit on core repository

for that you need to check out with the svn+ssh root url :

for trunk :

svn co svn+ssh://***@svn.savannah.gnu.org/phpgroupware/core/trunk

for branch_0_9_16 :

svn co
vn+ssh://***@svn.savannah.gnu.org/phpgroupware/core/branches/branch_0_9_16

PART FOR PERSONAL REPOSITORIES USAGE
##########################################

aside core and modules there is a people root dit with inside one
directory per coder

under each coder directory you have the same structure with core and
modules (but it's empty till people play with them)

that will allow coders to play each in his own sandbox without fearing
to break things in reference structure... once a new feature is working
in personal repository the coder can merge his code in the maintream in
one shot... that will allow us to have a nice commit log in maintream :)

for example in my personal core/trunk i can have a copy of root
core/trunk with just a change on svn:externals so that i use svn+ssh for
ged on my own modules/ged repository

then a checkout on svn co
svn+ssh://***@svn.savannah.gnu.org/phpgroupware/people/maat/core/trunk
gives me a ready-to-code working copy

That structure can also allow, for example, to use a customized phpgwapi
with new features not yed teady for mainstream inclusion

So changing just the phpgwapi svn:externals link to
svn+ssh://***@svn.savannah.gnu.org/phpgroupware/people/nickname/modules/phpgwapi/trunk
will allow to play with this patched api and test it with the current
official modules trunks

Thanks all and apologies for this really long mail

Maât

Maât

2009-11-11 12:48:05 UTC

Post by MaÃ¢t
That structure can also allow, for example, to use a customized phpgwapi
with new features not yed teady for mainstream inclusion

s/yed/yet/;s/teady/ready/

(sorry for all the typos)

Maât

2009-11-13 19:06:34 UTC

Post by MaÃ¢t
PART FOR EVERYBODY WITHOUT COMMIT RIGHTS
################################################
Svn repositories (not repository because i have splitted them) share a
common root
http://svn.savannah.gnu.org/svn/phpgroupware/
** core : the repository everybody (betatesters, bug hunters, svn loging
users) will want to checkout
------------------------
-- trunk : the last (hopefully fast) moving codebase with the last
exciting features (and currently the greatest number of bugs we want to
get rid of)
to get a working copy from there you just need to checkout this url
http://svn.savannah.gnu.org/svn/phpgroupware/core/trunk
-- branches : the various stable (and some of them outdated) branches...
for example you'll fint there the branch dedicated to current stable
versions 0.9.16.xxx
the here above stable branch name is "branch_0_9_16" i tried to
normalize all branch names ( branch_0_9_10 branch_0_9_12 branch_0_9_14
branch_0_9_16...)
to get a working copy from there you just need to checkout this url
http://svn.savannah.gnu.org/svn/phpgroupware/core/branches/branch_0_9_16

----8<----

Post by MaÃ¢t
Thanks all and apologies for this really long mail
Maât

Can someone test this and give me feedback ?

Sigurd Nes

2009-11-15 11:38:08 UTC

Maat wrote on Fri, 13 November 2009 20:06

Post by MaÃ¢t
Can someone test this and give me feedback ?

I should be able to test it after (next) Tuesday.

Regards

Sigurd.

Sent from the phpGroupWare forums @ forums.phpGroupWare.org

Maât

2009-11-15 15:05:13 UTC

Post by Sigurd Nes
Maat wrote on Fri, 13 November 2009 20:06

Post by MaÃ¢t
Can someone test this and give me feedback ?

I should be able to test it after (next) Tuesday.
Regards
Sigurd.

Thank you Sigurd

Maât

Caeies

2009-11-18 13:18:47 UTC

Hi all,

Post by MaÃ¢t
PART FOR EVERYBODY WITHOUT COMMIT RIGHTS
################################################
Thanks all and apologies for this really long mail
Maât

Can someone test this and give me feedback ?

Looks working for me. BeAware of savannah nickname with mixed case !

Regards,

Caeies

Maât

2009-11-18 15:07:15 UTC

Post by Sigurd Nes
Hi all,

Post by MaÃ¢t
PART FOR EVERYBODY WITHOUT COMMIT RIGHTS
################################################
Thanks all and apologies for this really long mail
Maât

Can someone test this and give me feedback ?

Looks working for me. BeAware of savannah nickname with mixed case !
Regards,
Caeies

thank you Caeies :)

Sigurd Nes

2009-11-19 18:14:38 UTC

----8<----

Post by MaÃ¢t
Thanks all and apologies for this really long mail
Maât

Can someone test this and give me feedback ?

I works

Here is a howto on setting svn:externals
http://blog.kowalczyk.info/article/Short-tutorial-on-svn-propset-for-svnexternals-p.html

Regards

Sigurd

Maât

2009-11-21 21:22:06 UTC

Thanks Sigrud.
Glad to see you have started to put new things into your "personal"
repository.
Hope you'll find a little bit of time to explain quickly the big
differences between each base trunk app and your work so that we know
what could be looked at for later merging :)

I'm done - Take it for a spin :)

The main difference are
- That db-abstraction is converted to pdo (faster and more secure) -
and that innodb is default for Mysql (to support transactions).
The db-object supports db-cloning - which I really really need - so
please don't remove it.

In you personal repository *nobody* except you is supposed to play :
you're your own master. If you don't remove it then it will not be
removed (not by me whatever).

but till the feature is considered fool-proof, suited for stable
release, tested against regressions and accepted by all the coordinators
team it's merge into base repository could be delayed

please do not consider this as a personal offence... it's just paranoïa :)

- New template (set as default)

i'll give a look a t it :)

/me just being curious :)

- (most)Third party libraries are updated to latest.

cool :)

- runs on php version 5.3

cool :)

- mcrypted all settings in header.inc.php if set

- Admin can set preferences on behalf of users

*very* cool

- working Interlink - links (two-ways) items across the system

*very* cool

- properly working install/uninstall.

Other than that: massive fixes for ACL, LDAP, conversion of users
handled as object (before:arrays), session handling and more...
SOAP and XMLRPC is updated to latest and works as client and service -
but the old services need attention.

I recommend that we take it further from the current state rather than
trying to merge back single fixes.

well i'm not all for this way of doing things. I know previous gigantic
merges from resight have been done and accepted but thats (imho) the
best way to create problems.

i'd prefer to merge nice-featuire by nice-feature

core
phpgwapi
setup
addressbook
admin
calendar
hrm
manual
messenger
notes
preferences
(projects - well - kind of)
property
sms
todo
email might work(if configuration is correct): if it hangs - delete
the menu-hook and restart apache

?

Could you explain more this case please ?

Just so that i understand why deleting menu-hook could improve things :)

Regards
Sigurd

thanks Sigurd for this *big* contributiuon. It's up to us *all* to work
and merge these features into reference repository :)

Regards,

Maat

Sigurd Nes

2009-11-21 22:14:18 UTC

I'm done - Take it for a spin :)

you're your own master. If you don't remove it then it will not be
removed (not by me whatever).
but till the feature is considered fool-proof, suited for stable
release, tested against regressions and accepted by all the coordinators
team it's merge into base repository could be delayed
please do not consider this as a personal offence... it's just paranoïa :)

By all means - but the current trunk is really a mess.
If you don't want to use my version as base for improvements - I will recommend
to revert to the state of before Dave's mega patch -and take it from there.

- New template (set as default)

i'll give a look a t it :)
/me just being curious :)

- (most)Third party libraries are updated to latest.

cool :)

- runs on php version 5.3

cool :)

- mcrypted all settings in header.inc.php if set

If mcrypt is installed and set to "true" - the db-name/db-user/db-password is
encrypted. Making it more secure.

- Admin can set preferences on behalf of users

*very* cool

- working Interlink - links (two-ways) items across the system

*very* cool

- properly working install/uninstall.

I recommend that we take it further from the current state rather than
trying to merge back single fixes.

well i'm not all for this way of doing things. I know previous gigantic
merges from resight have been done and accepted but thats (imho) the
best way to create problems.

This ones fixes all the problems induced by the previous mega-patch :)
Also - it is tested - and runs in a production environment.

(phpgwapi/setup/manual/preferences/property/sms)

Post by MaÃ¢t
i'd prefer to merge nice-featuire by nice-feature

?
Could you explain more this case please ?
Just so that i understand why deleting menu-hook could improve things :)

It stops the process of trying to connect to the wrongly configured
pop/imap-server when loading the menu.
The email app is a weak spot...

Regards
Sigurd

thanks Sigurd for this *big* contributiuon. It's up to us *all* to work
and merge these features into reference repository :)

Another coming feature (in a few weeks) is general support for jasper reports

To make it easy to test - I have uploaded this version to:
http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_21.tar.gz

Keep in mind that you need pdo - and I recommend PostgreSQL 8.3 and above.

Install all apps and try it:)

Regards

Sigurd

Maât

2009-11-21 22:26:08 UTC

By all means - but the current trunk is really a mess.
If you don't want to use my version as base for improvements - I will
recommend to revert to the state of before Dave's mega patch -and take
it from there.

i personnally *want* to use as much as possible of your improvements but
one mega patch is already too much.

reverting this patch wouldbring more harm than good.

i'm just pleading for a clean way of doing things even if the starting
base is not the best :)

- mcrypted all settings in header.inc.php if set

If mcrypt is installed and set to "true" - the
db-name/db-user/db-password is encrypted. Making it more secure.

ok thanks

I recommend that we take it further from the current state rather than
trying to merge back single fixes.

well i'm not all for this way of doing things. I know previous gigantic
merges from resight have been done and accepted but thats (imho) the
best way to create problems.

This ones fixes all the problems induced by the previous mega-patch :)
Also - it is tested - and runs in a production environment.
(phpgwapi/setup/manual/preferences/property/sms)

well that's a good point but that's just one production environment...
we can imagine that other production environments could be harmed by
the changes

i'm just trying to avoid problems :)

if yours changes solve problems they *need* to be merged into base repos :)

email might work(if configuration is correct): if it hangs - delete
the menu-hook and restart apache

?
Could you explain more this case please ?
Just so that i understand why deleting menu-hook could improve things :)

It stops the process of trying to connect to the wrongly configured
pop/imap-server when loading the menu.
The email app is a weak spot...

ok thanks :)

Post by Sigurd Nes
Another coming feature (in a few weeks) is general support for jasper reports
http://www.byggeplass.bergen.no/download/phpggroupware_17524_nov_21.tar.gz
Keep in mind that you need pdo - and I recommend PostgreSQL 8.3 and above.
Install all apps and try it:)
Regards
Sigurd

:)

thanks for your answeer Sigurd :)

Sigurd Nes

2009-11-21 20:59:42 UTC

Post by MaÃ¢t
to get a working copy from there you just need to checkout this url
http://svn.savannah.gnu.org/svn/phpgroupware/core/trunk
-- branches : the various stable (and some of them outdated) branches...
for example you'll fint there the branch dedicated to current stable
versions 0.9.16.xxx
the here above stable branch name is "branch_0_9_16" i tried to
normalize all branch names ( branch_0_9_10 branch_0_9_12 branch_0_9_14
branch_0_9_16...)
to get a working copy from there you just need to checkout this url
http://svn.savannah.gnu.org/svn/phpgroupware/core/branches/branch_0_9_16

I works
Here is a howto on setting svn:externals
http://blog.kowalczyk.info/article/Short-tutorial-on-svn-propset-for-svnexternals-p.html
Regards
Sigurd

I'm done - Take it for a spin :)

The main difference are
- That db-abstraction is converted to pdo (faster and more secure) - and that
innodb is default for Mysql (to support transactions).
The db-object supports db-cloning - which I really really need - so please don't
remove it.
- New template (set as default)
- (most)Third party libraries are updated to latest.
- runs on php version 5.3
- mcrypted all settings in header.inc.php if set
- Admin can set preferences on behalf of users
- working Interlink - links (two-ways) items across the system
- properly working install/uninstall.

Other than that: massive fixes for ACL, LDAP, conversion of users handled as
object (before:arrays), session handling and more...
SOAP and XMLRPC is updated to latest and works as client and service - but the
old services need attention.

I recommend that we take it further from the current state rather than trying to
merge back single fixes.

* Working modules(personal trunk):

core
phpgwapi
setup
addressbook
admin
calendar
hrm
manual
messenger
notes
preferences
(projects - well - kind of)
property
sms
todo

* system trunk:
email might work(if configuration is correct): if it hangs - delete the
menu-hook and restart apache

Regards

Sigurd

Maât

2009-11-21 20:04:19 UTC

Post by MaÃ¢t
to get a working copy from there you just need to checkout this url
http://svn.savannah.gnu.org/svn/phpgroupware/core/trunk
-- branches : the various stable (and some of them outdated)
branches...
for example you'll fint there the branch dedicated to current stable
versions 0.9.16.xxx
the here above stable branch name is "branch_0_9_16" i tried to
normalize all branch names ( branch_0_9_10 branch_0_9_12 branch_0_9_14
branch_0_9_16...)
to get a working copy from there you just need to checkout this url
http://svn.savannah.gnu.org/svn/phpgroupware/core/branches/branch_0_9_16

I works
Here is a howto on setting svn:externals
http://blog.kowalczyk.info/article/Short-tutorial-on-svn-propset-for-svnexternals-p.html
Regards
Sigurd

Thanks Sigrud.

Glad to see you have started to put new things into your "personal"
repository.

Hope you'll find a little bit of time to explain quickly the big
differences between each base trunk app and your work so that we know
what could be looked at for later merging :)

/me very happy to see new commit logs commit logs appear :)

Maat

Lars

2010-01-17 14:19:16 UTC

Hello,

I'd like to play! ;)

The role I'd like to play is the role of a developer. To understand the code I'd like to start with some bugfixes and other rather small but needed changes before I can start to help with implementing new features.

Are you interested?

Regards,

Lars.

Sent from the phpGroupWare forums @ forums.phpGroupWare.org

Maât

2010-01-17 18:08:50 UTC

Post by Lars
Hello,
I'd like to play! ;)
The role I'd like to play is the role of a developer. To understand the code I'd like to start with some bugfixes and other rather small but needed changes before I can start to help with implementing new features.
Are you interested?
Regards,
Lars.

Of course we are interested :)

Your help is really welcome !

Regards

Maât

Lars

2010-01-17 18:50:13 UTC

Great!

I'll grab a copy from svn as soon as possible.

Is the bugtracker (https://savannah.gnu.org/bugs/?group=phpgroupware) current or are there bugs listed which are already fixed?

Regards,

Lars.

Sent from the phpGroupWare forums @ forums.phpGroupWare.org

Maât

2010-01-17 19:03:33 UTC

Post by Lars
Great!
I'll grab a copy from svn as soon as possible.
Is the bugtracker (https://savannah.gnu.org/bugs/?group=phpgroupware) current or are there bugs listed which are already fixed?
Regards,
Lars.

it's current (well that's theory ^^)

what i can say for sure is that's our only bugtracker

it's filled with many things... more or less accurate and probably
targeted at old versions family 0.9.16.x

trunk we are currently working on will end on new 0.9.18.x

so many things currently "active" in our bugtracker may be not
applicable on new code base (check needed i guess)

if there are questions this very list is the right place to ask them :)

Regards,

Maât

Lars

2010-01-17 19:33:04 UTC

Ok, I see.. ;)

Thank you very much. I'll ask here, if I have something to ask (which might be often, we'll see).. ;)

Good to know, that some bugs might have disappeared without being noticed.. I'll check each bug for existence before working on it.

I'll start my work tomorrow. It might take some time until I can provide the first bugfix, because I didn't look at the sources yet and might need some time to understand it.

BTW: Will anyone update the website? It's pretty old and many things are no longer correct, some links dead. This lets the project look even more dead than it is, I almost thought it died completely..

Regards,

Lars.

Sent from the phpGroupWare forums @ forums.phpGroupWare.org

Sigurd Nes

2010-01-17 20:08:21 UTC

Hi Lars,

The official trunk has fallen somewhat behind - and all though it is not the
official code - I will take this opportunity to point to my version of the code
which is much more updated (especially for api, admin, setup, preferences,
property, hrm, phpsysinfo and manual)

At least - have a look at it for reference.

Of course - all good things should be migrated to the official trunk...

if you have project member subversion access via SSH -you can get is like this:

svn co
svn+ssh://<membername>@svn.savannah.gnu.org/phpgroupware/people/sigurdne/core/trunk

if not - get it from http://www.byggeplass.bergen.no/download/savanna/

Regards

Sigurd

Lars

2010-01-17 20:25:04 UTC

Interesting.

Which one is the right one?
In the beginning I will provide rather small parts like bug fixes, but as soon as I intend to provide bigger changes, it would be good to know, which of the two trunks is the right base?

Do both provide the same functionality or is the official trunk providing more than your code? If official has the same or fewer functionality it might be a good idea to ignore official and continue with your code. But I guess it's not that easy? ;)

So, which is the better code for me to work on?

Regards,

Lars.

Sent from the phpGroupWare forums @ forums.phpGroupWare.org

Maât

2010-01-17 20:48:56 UTC

Post by Lars
Interesting.
Which one is the right one?

The right one is base trunk of course

Sigurd has done a lot of work on his own in his personal repository trunk

this advances need to be tested and merged into trunk cleanly

this mergework can be rather difficult but it would bring huge advances
to the project

Post by Lars
In the beginning I will provide rather small parts like bug fixes, but as soon as I intend to provide bigger changes, it would be good to know, which of the two trunks is the right base?

answered :)

Post by Lars
Do both provide the same functionality or is the official trunk providing more than your code? If official has the same or fewer functionality it might be a good idea to ignore official and continue with your code. But I guess it's not that easy? ;)

Some of the new features Sigurd added in his repository might cause
deadlocks in other apps for example

so we need to be carfeful merging his changes... mut many of them are
likely to be harmless and need to be merged as quickly as we can

Post by Lars
So, which is the better code for me to work on?
Regards,
Lars.

for bug hunting plase use base trunk as future release will comme from there

but if you have time and energy please test Sigurd work and compare it
to base trunk... isolate some interresting changes and provide them as
patches

please note that Sigurd might have already dealt with some bugs... so
playing with both trunks can also help you save time

I wish you happy coding and bug hunting

Maât

Lars

2010-01-17 21:50:33 UTC

Ok, I guess, I'll test trunk and Sigurds work as far as I can. And then I'll start trying to merge this and that.

This might be enough work for quite some days. ;) It will require me to look at a lot of code, which will for sure help me to understand it.

Regards,

Lars.

Sent from the phpGroupWare forums @ forums.phpGroupWare.org

Laurie D Kingsland

2010-03-05 11:31:53 UTC

I am very interested in communicating with people actively using and developing this project. My immediate concern is how do I get the icons for the applications to show in my nav-bar? I am a programmer, document writer and active tester. I wish to contribute to the functionality of this project. I can best be reached by skype: Lauriedk2 or email: mailto:***@gmail.com although I am scheduled to receive notices of posts on this forum. Looking forward to hearing from someone!
--
Laurie D Kingsland
Skype -- Lauriedk2
email -- mailto:***@gmail.com.

Sent from the phpGroupWare forums @ forums.phpGroupWare.org

Sigurd Nes

2010-03-07 15:54:41 UTC

Post by Laurie D Kingsland
--
Laurie D Kingsland
Skype -- Lauriedk2

Hi Laurie,

First of all you have to have run-priveleges for the application - then using
'notes' as example:

Have a look at notes/inc/class.menu.inc.php which sets up the menu/navigation.

you will find something like: 'image' => array('notes', 'navbar'),

this means that the menu will look for navbar.png within the application 'notes'

It will first try notes/templates/<selected template>/images/navbar.png and fall
back to notes/templates/base/images/navbar.png if nothing found.

Regards

Sigurd

Laurie D Kingsland

2010-03-08 03:54:02 UTC

I figured out the solution to getting the icons showing. Now my interest is in how I can contribute to the development of this project. I am currently taking a close look at the Projects application and modifying it to meet my needs. The current problem is how do I set the country and currency in the global preferences? Thank you for responding and I look forward to more conversations with you.

Laurie D Kingsland
Skype -- Lauriedk2
email -- mailto:***@gmail.com
--
Laurie D Kingsland
Skype -- Lauriedk2
email -- mailto:***@gmail.com.

Sent from the phpGroupWare forums @ forums.phpGroupWare.org

Sigurd Nes

2010-03-08 20:25:18 UTC

Post by Laurie D Kingsland
I figured out the solution to getting the icons showing. Now my interest is in how I can contribute to the development of this project. I am currently taking a close look at the Projects application and modifying it to meet my needs. The current problem is how do I set the country and currency in the global preferences? Thank you for responding and I look forward to more conversations with you.

Hi Laurie,

Your interest are most welcome.

You can set the values in the preferences section of the system.

The url will look like:
http://<something>/preferences/preferences.php?appname=preferences&type=user

What version (and template) are you trying?

I personally would recommend that you gave this one a try:

svn co svn+ssh://svn.savannah.gnu.org/phpgroupware/people/sigurdne/core/trunk

in order accomplish the checkout - you need to edit your ~/.ssh/config as
explained in
http://blog.caeies.org/2010/01/happy-new-year-2010-and-new-repository.html

Here is a guideline on how to write patches:
http://support.phpgroupware.org/patches

and here is the coding standard:
http://svn.savannah.gnu.org/svn/phpgroupware/modules/phpgwapi/trunk/doc/coding_standard.txt

That should get you started - don't hesitate to ask for advice.

Regards

Sigurd

Laurie D Kingsland

2010-03-11 06:21:02 UTC

I am a self-taught programmer and am unaccustomed to working with others on programming projects but I am really looking forward to getting to do this with phpgroupware. I downloaded the version that I first came to when searching for a program that would let me coordinate projects and the efforts of the people working on them. I don't know how to try the version you suggested but would like to. I would be interested in helping to document the applications that are currently being offered in phpgroupware. It says this project is already started but I didn't see a way to get in touch with those doing it. I would also appreciate you time and attention in helping me to get this software to do what I want it to do and to become someone who can contribute to it.

I found the link to download your trunk and am doing so. Hope you will give me a hand in making it work.

--
Laurie D Kingsland
Skype -- Lauriedk2
email -- mailto:***@gmail.com.

Sent from the phpGroupWare forums @ forums.phpGroupWare.org

Sigurd Nes

2010-03-11 17:23:43 UTC