[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Evolution] CALL FOR SPONSORSHIP: The Open Group Ware Project
From: |
Benny Li |
Subject: |
Re: [Evolution] CALL FOR SPONSORSHIP: The Open Group Ware Project |
Date: |
Thu, 8 Feb 2001 21:43:21 -0800 |
can somebody tell me how i can get off this mailing list?
----- Original Message -----
From: "Lloyd Llewellyn" <address@hidden>
To: <address@hidden>
Cc: "Evo-List" <address@hidden>; "OO-List" <address@hidden>;
"Glue-List" <address@hidden>
Sent: Friday, February 09, 2001 8:03 PM
Subject: Re: [Evolution] CALL FOR SPONSORSHIP: The Open Group Ware Project
>
>
> > I'm no DB geek by any definition, but has anyone thinking about this
> > considered what/how the database ought to work? Is it possible to
> > implement a solution built on top of MySQL or Postgres, or something
> > else that might scale well?
>
> My original conception was to make the back end pluggable, given the S
> on OGS. There should be a mapping layer between the goupware
> application services in the middle and the back end storage. You should
> be able to swap in DB's. If an organization already has Oracle running,
> OGS should be able to store its data in Oracle.
>
>
> > Let's pick an attainable scope of features, determine minimum functional
> > requirements for those features, and then get started. We need not
> > define a huge feature set initially, but we need to understand the
> > architectural consequenses of decisions made when implementing those
> > features.
>
> Absolutely. We need to define the functions, define an architecture
> they fit into, then address each function within that architecture. It
> doesn't mean you have to have a complete blueprint before you start, but
> you have to resolve interdependencies and make sure one module's
> implementation doesn't conflict with another's (eventual)
> implementation. By just jumping in you waste time and end up having to
> either throw away code or force subsequent code to accommodate mistakes
> made in the first round.
>
> I'll start a thread called "What Is OGS?". It's time for us to start
> sharing knowledge about the different parts of the elephant.
>
>
>
>
> _______________________________________________
> Glue mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/glue
>
- Re: [Evolution] CALL FOR SPONSORSHIP: The Open Group Ware Project, (continued)
- Re: [Evolution] CALL FOR SPONSORSHIP: The Open Group Ware Project, Dan Kuykendall, 2001/02/08
- Re: [Evolution] CALL FOR SPONSORSHIP: The Open Group Ware Project, Lloyd Llewellyn, 2001/02/08
- Re: [Evolution] CALL FOR SPONSORSHIP: The Open Group Ware Project, Dan Kuykendall, 2001/02/08
- Re: [discuss] Re: [Evolution] CALL FOR SPONSORSHIP: The Open Group Ware Project, Michael L. Dean, 2001/02/08
- Re: [Evolution] CALL FOR SPONSORSHIP: The Open Group Ware Project, Lloyd Llewellyn, 2001/02/08
- Re: [Evolution] CALL FOR SPONSORSHIP: The Open Group Ware Project, Dan Kuykendall, 2001/02/08
- Re: [Evolution] CALL FOR SPONSORSHIP: The Open Group Ware Project, Lloyd Llewellyn, 2001/02/08
- Re: [Evolution] CALL FOR SPONSORSHIP: The Open Group Ware Project, Dan Kuykendall, 2001/02/08
- Re: [Evolution] CALL FOR SPONSORSHIP: The Open Group Ware Project,
Benny Li <=
Re: [discuss] Re: [Evolution] OO - GROUPWARE - Call for concluison- was: OpenOffice: Say it isn't so., Sander Vesik, 2001/02/06
Re: [discuss] Re: [Evolution] OO - GROUPWARE - Call for concluison-was: OpenOffice: Say it isn't so., Dan Kuykendall, 2001/02/06
GROUPWARE - Answered: Why "OOGS" ?, Lloyd Llewellyn, 2001/02/08
- Re: [discuss] GROUPWARE - Answered: Why "OOGS" ?, Sander Vesik, 2001/02/08
- Re: [discuss] GROUPWARE - Answered: Why "OOGS" ?, Dan Kuykendall, 2001/02/08
- Re: [discuss] GROUPWARE - Answered: Why "OOGS" ?, Sander Vesik, 2001/02/08
- Re: [discuss] GROUPWARE - Answered: Why "OOGS" ?, Dan Kuykendall, 2001/02/08
- OGS Project, Dan Kuykendall, 2001/02/08