phpgroupware-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Phpgroupware-developers] Re: phpGroupware database and uml d ocumen


From: Kai Hofmann
Subject: RE: [Phpgroupware-developers] Re: phpGroupware database and uml d ocumentation in wiki?
Date: Fri, 13 Jun 2003 09:41:55 +0200

> -----Original Message-----
> From: Dave Hall [mailto:address@hidden
> Sent: Friday, June 13, 2003 2:36 AM

> One minute you wish to have an open discussion then you send the
> proposal to a select few, with a request to not publish it.  
> I am confused.
>
> I do not understand the licensing issues.  As it currently stands all
> apps in the phpgw cvs are distributed under the GPL.  This schema
> impacts on all phpgw apps, and there components of the model which
> affects a GPL'd app, so I fail to see what the licensing issues are.
>
> So I do not see why this document can't be added to the wiki 

The database model I send is completly independend of the phpGroupware -
it is another probusiness internal project - and I got permission to send
it to some people as an example how the phpgroupware db could look like -
to make clear about what we (at probusiness) are talking about.

> I think we can all understand db modelling.

I have received answers that tell me that "this theoretical stuff is not
understandable". So I explained this.
 
> This actually appears to me to be some type of confused model which
> attempts to do HR and CRM in one model.  Unfortunately phpGW is
> groupware which should have some CRM functionality (through 
> infolog) and
> basic HR functions (through reworked contacts/accounts link), 
> not trying
> to do everything possible for every situation.

The database model and the software modules that are working on it
are two different things. As long as you also design the database in
different modules without interaction between the data (relations)
you have no real groupware (from my point of view). You only have
different applications which are trying to interact by another one
(infolog).
When having a whole database as in my example - you don't need
something like infolog for the data communication (between the modules).
Infolog is a great thing - but it should be there only for the
user interaction.


Greetings

   Kai Hofmann

-- 
*****    Open Source und Linux im professionellen Einsatz    *****
**  komplexe Mailserver, Groupware, Office: sprechen Sie uns an **
Dipl.-Inform. Kai Hofmann                    Team Softwarelösungen
pro|business AG, EXPO Plaza 1 (Deutscher Pavillon), 30539 Hannover
E-Mail: address@hidden,   Tel.: 0511/60066-332, Fax: -355
WWW: http://www.probusiness.de/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]