Goodbye

[Dave Hall]

Hi all,

I will keep my message here brief, but I am stepping down from all of my
roles within the project effectively immediately. I have thought long
and hard about this decision. You can read all about it on my blog at
http://davehall.com.au/blog/dave/2009/10/02/goodbye-phpgroupware

If people still want to continue the project I will assist with the
transition. I am also available to assist with any shutdown.

Thanks everyone who I have worked with trying to make phpGW as awesome
as we could.

Cheers

Dave

[Sigurd Nes]

Post by Dave Hall
Hi all,
I will keep my message here brief, but I am stepping down from all of my
roles within the project effectively immediately. I have thought long
and hard about this decision. You can read all about it on my blog at
http://davehall.com.au/blog/dave/2009/10/02/goodbye-phpgroupware
If people still want to continue the project I will assist with the
transition. I am also available to assist with any shutdown.
Thanks everyone who I have worked with trying to make phpGW as awesome
as we could.
Cheers
Dave

Hi all,

Dave has meant a lot to the project - and I wish him well as he steps aside.

I think this is a opportunity to get out the 0.9.18 - or - why not make it 1.0

We have been busy developing the system and update the libraries in the API.
Though I have to admit the work has been focused on a sub-set of applications -
and some new ones.

Some highlights:

* It runs on php 5.3
* The UI on latest apps (and 'property') are using YUI 2.8.0
* SOAP and XMLRPC updated to latest (SOAP using native php server/client)
* LDAP working
* PDO - db abstraction
* support for localized translations (per domain)
* php functions can be invoked from templates.
* sensitive information in header.inc.php is (optionally) scrambled by mcrypt
* Excel/odf - export
* Excel read
* Interlink - linking items across the system
* SMS-gateway supporting webservice (SOAP and GET) and cellular(gnokii)
* Support for Help on each function (write as .odt - displayed as HTML)
* integration with handhelds
* and more...


We have currently 6 professional developers (project based) working on two new
modules - which integrates with the 'property'-module and general accounting
systems.

1) Booking - (public frontend/restricted backend) to handle resources available
for hire - as training facilities, concert halls, class rooms ...

2) Rental - specialized module for space rental


The municipal of Bergen is currently in a pilot phase for a new organization
(comprising 1 mill m2 of schools and institutions).

The ramp up project is stipulated to last for at least two more years.

Maybe we should have a new supersmart template engine...

I propose myself as the API-koordinator.

I also think we have to let parties that are willing to fund the project to play
a role at some level.

Regards

Sigurd

[Maât]

Post by Dave Hall
Hi all,
I will keep my message here brief, but I am stepping down from all of my
roles within the project effectively immediately. I have thought long
and hard about this decision. You can read all about it on my blog at
http://davehall.com.au/blog/dave/2009/10/02/goodbye-phpgroupware
If people still want to continue the project I will assist with the
transition. I am also available to assist with any shutdown.
Thanks everyone who I have worked with trying to make phpGW as awesome
as we could.
Cheers
Dave

hi Dave,

Sorry to see you go away from phpGroupWare from a phpGroupWare point of
view.

You have a very deep knowledge of phpGW internals and we'll probably
find we miss this in due term.

We are still maintaining ged electronic documents management module and
the now stable generic flow management system.

If there are enough people interrested in phpGW going on (and willing to
contribute even very slightly... we also need people that are not
killers in php coding) we could try to see what can be done to make it
grow again instead of shutting it down.

What do people think here ? (dont limit yourselves ;) )

Maât

[Caeies]

Hi All,
Hi Dave,

Mieux vaut tard que jamais ...

Post by Dave Hall
Hi all,
I will keep my message here brief, but I am stepping down from all of my
roles within the project effectively immediately. I have thought long
and hard about this decision. You can read all about it on my blog at
http://davehall.com.au/blog/dave/2009/10/02/goodbye-phpgroupware
If people still want to continue the project I will assist with the
transition. I am also available to assist with any shutdown.
Thanks everyone who I have worked with trying to make phpGW as awesome
as we could.

Thanks again for your time, your energy and your money on this project.
I enjoyed working with you, and hope to see you again. Perhaps working
together one day, who knows :).

I know that this decision was not easy to take, but sometime people need
to go ahead not only "to eat", nor feeling "good" with design choices or
code base ... And yes their still a lot's of problem with the actual
code base, and that's not with part time workers that this will improve
... Rewriting the full code, yeah, We think together about this ... but
lack of time ...

This project has an heavy history, with a lot's of forks, lot's of
individuals fighting to get THE position, and when they disagreed they
fork the project (even fork the fork ...). So that's Open Source too.
Human story. Once again.

When Sigurd ask for the "Main" Position, I recall to all of you that
there's still a CT (even with Dave's resignation (?)), and that If
people want to take over the project, they should be elected by the
community.

So if the community let us organize some kind of election, and not a "is
there any objections" election, then this project could have a future ...

So If contributors / users want to be "promoted" for the former Dave's
Role, please let us know.

Caeies,

Applications Coordinator, CT Member.

[Sigurd Nes]

Post by Caeies
So If contributors / users want to be "promoted" for the former Dave's
Role, please let us know.

I'm in the race: I want to be promoted for the former Dave's Role.

Regards

Sigurd

[Sigurd Nes]

Any objections to that I take over as the maintainer of phpGroupWare?


Regards

Sigurd.

Sent from the phpGroupWare forums @ forums.phpGroupWare.org

[Dan Kuykendall]

Hi all,

My preference at this point would be to shut down the project. It seems
like the codebase is just too outdated. Maybe at somepoint it would be
worth picking up and starting from scratch with all thats been learned
both in phpGW and across all the various projects in the open source
community these last 9+ years.

Anyways, if a clear vision can be had and a developer to continue it is
around, then please contact me... otherwise a leaderless project is a
dead one.

Dan

Hi,

Post by Dave Hall
I will keep my message here brief, but I am stepping down from all of my
roles within the project effectively immediately.

Obviously, we all have to respect your decision. Nevertheless, it's a pity.
Thanks a lot for all your work for phpGW.

Post by Dave Hall
If people still want to continue the project I will assist with the
transition. I am also available to assist with any shutdown.

Well, it would be sad if we had to shut down phpGW. The code base might
be a bit outdated (php4), but the concept of phpGW of being more that
just calendar, mail and addressbook is stil valid and rather unique.
Most "modern" groupware systems just focus on these "essentials" - it's
easier to maintain.
Unfortunately, I have no programming power at hand to contribute - I
myself am not a programmer any more...
Hope we find a way to continue
Regards
Christian aka bofh42
_______________________________________________
coordinators mailing list
http://lists.phpgroupware.org/mailman/listinfo/coordinators

[Sigurd Nes]

Sent: 2009-10-06 08:22:41 CEST
Subject: Re: [phpGroupWare coordinators] Goodbye
Hi all,
My preference at this point would be to shut down the project. It seems
like the codebase is just too outdated. Maybe at somepoint it would be
worth picking up and starting from scratch with all thats been learned
both in phpGW and across all the various projects in the open source
community these last 9+ years.
Anyways, if a clear vision can be had and a developer to continue it is
around, then please contact me... otherwise a leaderless project is a
dead one.
Dan

Hi all,

I have plans for it and want to keep it alive.

I think the best approach will be to focus on the system as a general application development framework - starting with the API and some core modules (admin, setup, preferences).
I also think the majority of the existing applications without a minimum level of maintenance has to be put in a historical archive for future reference and a possible source of inspiration only.

Important features are:
* user-handling
* integration capabilities (xmlrpc/soap/ldap...)
* building blocks for ui as super-objects prepared to utilize common elements (as tables, lists, calendars)
* mechanism for internal integration across modules

I will fix the API (and core) to a usable state (running php 5.3) - and update to the latest 3-party libraries.

I think that once the system is in a shape that makes is possible to install and operate - it will attract developers and users.

Regards

Sigurd

[Maât]

Post by Dave Hall

Sent: 2009-10-06 08:22:41 CEST
Subject: Re: [phpGroupWare coordinators] Goodbye
Hi all,
My preference at this point would be to shut down the project. It seems
like the codebase is just too outdated. Maybe at somepoint it would be
worth picking up and starting from scratch with all thats been learned
both in phpGW and across all the various projects in the open source
community these last 9+ years.
Anyways, if a clear vision can be had and a developer to continue it is
around, then please contact me... otherwise a leaderless project is a
dead one.
Dan

Hi all,
I have plans for it and want to keep it alive.
I think the best approach will be to focus on the system as a general application development framework - starting with the API and some core modules (admin, setup, preferences).

Every single framework does that... and many better than we do : Zend
first of them but also Symfony, drupal, eZ...

If we plan to gon on their scope we are dead...

Post by Dave Hall
I also think the majority of the existing applications without a minimum level of maintenance has to be put in a historical archive for future reference and a possible source of inspiration only.

That makes sense but the svn system as i re-organized it just need to
change the list of externals to let these module aside

Post by Dave Hall
* user-handling

Yes and there we'll need to put hard work

And part of this work will involve thinking about template system :
coders are often very poor interface designers

And good interface designers have often very poor php and xml skills.
Dreamweaver (sorry guys for the ugly word) and css and htmls are their
worlds.

Relying on current xsltemplate even if it's sexy on the paper will
ensure that zero descent web designer will be able to get in and help
us make nice looking user interfaces.

As far as web design is concerned the previous phplib based template
system was loads better.

Post by Dave Hall
* integration capabilities (xmlrpc/soap/ldap...)

Agreed

Post by Dave Hall
* building blocks for ui as super-objects prepared to utilize common elements (as tables, lists, calendars)

Not agreed

Post by Dave Hall
* mechanism for internal integration across modules

Agreed a million times

Post by Dave Hall
I will fix the API (and core) to a usable state (running php 5.3) - and update to the latest 3-party libraries.

Ok on the goal but if we go on we'll have to discuss the method : i
don't wand to see a giant commit changing things everywhere whitout more
thant "Merge from my working company tree"

Suvbersion is all about keeping track of changes and helping bug hunting
by the means of changelog and commit date analysis

A million times okay for code fixing... but a million times not okay for
giant commits impossible to check

You probably did not even consider such commit... in this case please
accept my apologies for this part of my mail :)

Post by Dave Hall
I think that once the system is in a shape that makes is possible to install and operate - it will attract developers and users.
Regards
Sigurd

indeed having something that installs and works would be a nice idea :)

but if you want to attract devs ans users that will not be enough

we'll need documentation (people willing to write it) and user + dev
support (people willing to help people getting in... explaining things
again and again)

And till we have enough manpower to make separate teams for support and
developpement and doc writing and betatesting the remaining people will
have to be everywhere

[Sigurd Nes]

Post by Maât

Post by Dave Hall

Sent: 2009-10-06 08:22:41 CEST
Subject: Re: [phpGroupWare coordinators] Goodbye
Hi all,
My preference at this point would be to shut down the project. It seems
like the codebase is just too outdated. Maybe at somepoint it would be
worth picking up and starting from scratch with all thats been learned
both in phpGW and across all the various projects in the open source
community these last 9+ years.
Anyways, if a clear vision can be had and a developer to continue it is
around, then please contact me... otherwise a leaderless project is a
dead one.
Dan

Hi all,
I have plans for it and want to keep it alive.
I think the best approach will be to focus on the system as a general application development framework - starting with the API and some core modules (admin, setup, preferences).

Every single framework does that... and many better than we do : Zend
first of them but also Symfony, drupal, eZ...
If we plan to gon on their scope we are dead...

Post by Dave Hall
I also think the majority of the existing applications without a minimum level of maintenance has to be put in a historical archive for future reference and a possible source of inspiration only.

That makes sense but the svn system as i re-organized it just need to
change the list of externals to let these module aside

Great :)

Post by Maât

Post by Dave Hall
* user-handling

Yes and there we'll need to put hard work
coders are often very poor interface designers
And good interface designers have often very poor php and xml skills.
Dreamweaver (sorry guys for the ugly word) and css and htmls are their
worlds.
Relying on current xsltemplate even if it's sexy on the paper will
ensure that zero descent web designer will be able to get in and help
us make nice looking user interfaces.
As far as web design is concerned the previous phplib based template
system was loads better.

A lot of work has been put into making use of yui.
There is a (bit old) demo at http://beta.resight.no/login.php

Post by Maât

Post by Dave Hall
* integration capabilities (xmlrpc/soap/ldap...)

Agreed

Post by Dave Hall
* building blocks for ui as super-objects prepared to utilize common elements (as tables, lists, calendars)

Not agreed

Post by Dave Hall
* mechanism for internal integration across modules

Agreed a million times

Post by Dave Hall
I will fix the API (and core) to a usable state (running php 5.3) - and update to the latest 3-party libraries.

Ok on the goal but if we go on we'll have to discuss the method : i
don't wand to see a giant commit changing things everywhere whitout more
thant "Merge from my working company tree"
Suvbersion is all about keeping track of changes and helping bug hunting
by the means of changelog and commit date analysis
A million times okay for code fixing... but a million times not okay for
giant commits impossible to check
You probably did not even consider such commit... in this case please
accept my apologies for this part of my mail :)

The work has been done over a long period of time - so it is not very easy
differentiate the fixes - but some splits should be doable.

One commit per app - some more for the API

- Think of it as a fix of the latest mega-commit.

Post by Maât

Post by Dave Hall
I think that once the system is in a shape that makes is possible to install and operate - it will attract developers and users.

indeed having something that installs and works would be a nice idea :)
but if you want to attract devs ans users that will not be enough
we'll need documentation (people willing to write it) and user + dev
support (people willing to help people getting in... explaining things
again and again)
And till we have enough manpower to make separate teams for support and
developpement and doc writing and betatesting the remaining people will
have to be everywhere

Well - we have to start somewhere :)


Regards

Sigurd

[Dr. Christian Böttger]

Hi,

Post by Dave Hall
I will keep my message here brief, but I am stepping down from all of my
roles within the project effectively immediately.

Obviously, we all have to respect your decision. Nevertheless, it's a pity.

Thanks a lot for all your work for phpGW.

Post by Dave Hall
If people still want to continue the project I will assist with the
transition. I am also available to assist with any shutdown.

Well, it would be sad if we had to shut down phpGW. The code base might
be a bit outdated (php4), but the concept of phpGW of being more that
just calendar, mail and addressbook is stil valid and rather unique.
Most "modern" groupware systems just focus on these "essentials" - it's
easier to maintain.

Unfortunately, I have no programming power at hand to contribute - I
myself am not a programmer any more...

Hope we find a way to continue

Regards

Christian aka bofh42
--
Dr. Christian Böttger (Dipl.Phys.) DF5OP Open Source Broker
ph.: +49.5173.9249744 | fax: [phone] | 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]

Hi,

Post by Dave Hall
I will keep my message here brief, but I am stepping down from all of my
roles within the project effectively immediately.

Obviously, we all have to respect your decision. Nevertheless, it's a pity.
Thanks a lot for all your work for phpGW.

Same thoughts here :)

Post by Dave Hall
If people still want to continue the project I will assist with the
transition. I am also available to assist with any shutdown.

Well, it would be sad if we had to shut down phpGW. The code base might
be a bit outdated (php4), but the concept of phpGW of being more that
just calendar, mail and addressbook is stil valid and rather unique.

Agreed for phpGW being unique

The code base still needs cleaning but that's not a complicated thing to
do. Provided a good "cleaning guide" even beginners could get in and
play with us all

Most "modern" groupware systems just focus on these "essentials" - it's
easier to maintain.

these are mainly mail+agenda-wares

there are other needs (budget management, projet management, team
management) that could be focused by groupware suites

Unfortunately, I have no programming power at hand to contribute - I
myself am not a programmer any more...

I maintain what i said long ago : we lacked documentation (nice user
guide, nice developper guide, nice code documentation) that prevented
people to get in et slowed people adoption of phpGW

We can chose to work on these things and part off them do not need
killer coding skills :)

we need people ready to write user documentation, people willing to
install, test, detect regressions, reproduce and classify bugs before
passing them to coders

I think we also could do with a guy skilled with css and web "look and
feel"... that would not need php

Hope we find a way to continue
Regards
Christian aka bofh42

There are unaddressed user needs... we could address them and try to
focus on software intelligence (workflows for example) as well as
ergonomy (ajaxizing phpGW for example)

The main question is : are there enough of us left willing to continue
or not.

If the answer is "yes" we can then focus on team organization, election
of a leader and so on.

If the answer is "no"...

hope it will be "yes" :)

[Maât]

Maât wrote:
----8<----

Post by Maât
The main question is : are there enough of us left willing to continue
or not.
If the answer is "yes" we can then focus on team organization, election
of a leader and so on.
If the answer is "no"...
hope it will be "yes" :)

Well... either we are not so many or everybody entered into winter sleep :)