[Kroupware] docs and scripts

[Bernhard Reiter]

--Boundary-02=_pCFr9YMhVIQNdS9
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Tuesday 15 October 2002 07:54, Andreas Jellinghaus wrote:

> i wrote some documentation and scripts on my own to manage
> a mail server with the usual postfix/ldap/cyrus combo.

> Is there a way i can get these published within the
> kolab/kroupware project?=20

You will know that the Kroupware project itself is limited=20
to our contract with the BSI. Or to phrase it the other way round,
Kroupware is only the name for the project that fulfills the contract.

It is planned to maintain the software beyond the project,
but there is no definite decision on where the Kolab server source will be=
=20
hosted finally. At least one version will be archived at the Kroupware=20
Project place. Development versions will go
in a place that stay accessible beyond the kroupware project.

This is why we are currently reluctant to offer you hosting space for=20
contributed code, we do not have found the final place for Kolab itself=20
yet.

> Else i will open jet another sourceforge project, which is kind of lame,
> but the easiest alternative i see.

I can't judge how much work you've put into your scripts.
A place to publish a source tarball might be a sufficient for you for a=20
moment. As you have developed your scripts fairly independent
from the Kroupwareproject (which is not mean negatively, the Kroupware=20
project's aims are not fullfiling everybodys desires)
it might make sense to open up a project on savannah or so=20
and pursue your goals.

--Boundary-02=_pCFr9YMhVIQNdS9
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA9rFCph9ag3dpKERYRAmYKAJ0bqRy2H6EdStEXL9ojHXMSQZt0OACcDNJi
PcQq9ZkZasJJMBNZViuhP1Y=
=yXUD
-----END PGP SIGNATURE-----

--Boundary-02=_pCFr9YMhVIQNdS9--