phpgroupware-developers
[Top][All Lists]
Advanced

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

Re: [phpGroupWare-developers] release model idea


From: Dave Hall
Subject: Re: [phpGroupWare-developers] release model idea
Date: Sat, 21 Apr 2007 00:08:28 +1000

On Fri, 2007-04-20 at 08:41 -0500, Chris Weiss wrote:
> On 4/20/07, Sigurd Nes <address@hidden> wrote:
> > In my opinion - the core (or supercore) can be limited to: API, 
> > admin, preferences and setup.
> > Not sure about the manual.
> 
> I second this, except that manual should be included in Core *if* it
> gets a redesign so that it's easier to plug into by any app.
> 

Sigurd has done some work on this.  Now we use ODT for creating the
manual.  Give people a familar GUI for the work and it is GPLd :)

> My reason is that I have done some installs where only email is used,
> and others where no apps were used except custom ones, property also
> fits here as a basic install does not require PIM apps, even though it
> may use some of their API's.
> 

I think that we should include the basic PIM apps in the core.  For
example all events should be stored in calendar, addressbook is used to
manage the user contact data.  We should be encouraging the use of the
functionality in these apps, to keep it consistent and stop duplication.

> This, however, means a minor change in direction of the project.
> Right now we are a groupware suite that also provides a framework.
> This more modular structure with Core including only the minimum
> required to login and a rich API would be a framework that includes a
> groupware suite.  We could also offer bundle packs as releases, like
> Core, GroupWare (Core + PIM apps), and World (Core + PIM + everything
> that "works").

I am all for people developing bundles, a bit like Debian does with
derivatives.  I think we should build an eco system rather than
monolithic tarballs.  

Do go back to how drupal does it.  They provide the basics you need for
a functioning CMS, then you just download little tarballs of what you
need.  For davehall.com.au I have about 6 additional modules which give
me the functionality I need.

If I want to package up a tarball which has core + some supported
modules - say projects, tts and ged and push it as a software
development tool, this structure will allow that :)

Cheers

Dave
-- 
Dave Hall (aka skwashd)
API Coordinator
phpGroupWare
e address@hidden
w phpgroupware.org
j address@hidden
sip address@hidden
       _            ____                    __        __             
 _ __ | |__  _ __  / ___|_ __ ___  _   _ _ _\ \      / /_ _ _ __ ___ 
| '_ \| '_ \| '_ \| |  _| '__/ _ \| | | | '_ \ \ /\ / / _` | '__/ _ \
| |_) | | | | |_) | |_| | | | (_) | |_| | |_) \ V  V / (_| | | |  __/
| .__/|_| |_| .__/ \____|_|  \___/ \__,_| .__/ \_/\_/ \__,_|_|  \___|
|_|         |_|                         |_|Web based collaboration platform






reply via email to

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