RE: Suggestion for SME...
"Brandon Friedman" <[email protected]> Mon, 8 Dec 2003 12:39:56 +0200
| Newsgroups | gmane.network.e-smith.devel |
|---|---|
| Message-ID | <000c01c3bd77$9ef99320$f3001fac@adtjwitl03> |
Kolab also uses open-pkg, which would also need to be added. > -----Original Message----- > From: Brad Hards [mailto:[email protected]] > Sent: 08 December 2003 12:09 > To: Klaus J. Mueller; [email protected]; Brandon Friedman > Subject: Re: [e-smith-devinfo] Suggestion for SME... > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, 08 Dec 2003 20:46 pm, Klaus J. Mueller wrote: > > Hm? For what I understand kolab would make a great extension to > > e-smith. > The kolab implementation is very tightly tied to the concept > of "everything in > LDAP", while e-smith runs its own configuration database in Perl. > > > [Does someone have a link to a self definition of e-smith? I can't > > seem to find one on e-smith.org. In case there is none yet: > shouldn't > > we have one? Otherwise we might find out that we all have very > > different ideas of what e-smith actually is. This could mean that > > we're trying to run into several directions at the same time - now > > that we can decide which way to go] > I see e-smith as the events/actions/templates core. > Everything else is > changeable. See http://www.e-smith.org/architecture/ and > http://www.e-smith.org/concepts/ > > Compare that with http://www.kroupware.org/architecture-1.1/index.html > > > I think that the gateway functionality is just a minor part in the > > whole concept. (BTW: I think that for security reasons this is the > > component that should be the first one to be put on a > different box in > > real world scenarios - which should be the case for most > installations > > anyway (DSL-Routers...); it can be done very easily with > another low > > end box running e.g. http://fli4l.de/ (ISDN, DSL)) > I tend to agree, except for my home network, where I want it > all in one little > (mini-ITX, say) box. > > > Extending the collaborative concept by a workgroup server > would be a > > great idea in my opinion. > We could, instead of the kolab approach, try eGroupware - > http://www.egroupware.org/ or another system > > > There should not be many components missing, anyway - should there? > > > > Brad: did I get you right here: there are some the fileserver bits > > missing in e-smith? Or does that read "these are the parts that are > > missing in Kolab" > kolab has no fileserver (or gateway) functionality. The > question is - would > you rather add the groupware functionality to e-smith, or the > fileserver > functionality to kolab? > > Brad > - -- > http://lca2004.linux.org.au - I'm registered. Are you? > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.3 (GNU/Linux) > > iD8DBQE/1E2gGwwszQ/PZzgRAohyAJ92D2nDgTBSszeXxJjyZXaL3S1s4ACfY7LT > O69yIKxYuRWucgh7AaHMLCY= > =gEb6 > -----END PGP SIGNATURE----- > -- Please report bugs to [email protected] Please mail [email protected] (only) to discuss security issues Support for registered customers and partners to [email protected] To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Searchable archive at http://www.mail-archive.com/devinfo%40lists.e-smith.org