[Kroupware] Kolab contribution policy

[Ian Reinhart Geiser]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 15 January 2003 06:09 am, Bernhard Reiter wrote:
> On Wednesday 15 January 2003 05:31, Ian Reinhart Geiser wrote:
> > On Tuesday 14 January 2003 09:31 am, Bernhard Reiter wrote:
> > > On Saturday 11 January 2003 18:10, Ian Reinhart Geiser wrote:
> > > > What is the policy about adding packages or provideing packages for
> > > > kolab?
> > >
> > > There is no explicit policy yet.
> > > For now, people should just publish link to their contributions
> > > on this list.
> >
> > So there is there any external input welcome on this or should we just
> > sit back and wait?
>
> Well, of course it is welcome!
> Maybe I was taking this a bit too natural within a Free Software project
> like this. :)
>
> Another thing is that the time of the people trying to fullful the contra=
ct
> is limited which makes it quite impossible for us to fully check out
> each contribution we get yourselfs to make it an official part.
> However this should not limited anybody from publishing
> any contribution and interest other people it.
I think I came across wrong,  I was not implying that I should not make the=
=20
patches public.  I understand you guys have a timeline and a goal to meet. =
=20
My big concern was to wait until you guys got what you needed done, so that=
 I=20
could make patches that could be usable extentions to Kolab.

I have patches for pam ldap authentication from kolab server,  bogofilter f=
or=20
spam filtering , and clamav for virus scanning.  The only thing lacking fro=
m=20
them is to have them packaged in openpackage as an RPM so they can just be=
=20
installed.

Either way if you have any hints let me know.

Cheers
	-ian reinhart geiser

=2D --=20
=2D --:Ian Reinhart Geiser <geiseri@yahoo.com>
=2D --:Public Key: http://geiseri.myip.org:8080/publickey.txt
=2D --:Jabber: geiseri@geiseri.myip.org
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+JiDkPy62TRm8dvgRAsj2AJ9tbrZNf6u5PkIwacJzH52lGpvb6QCeMUzu
zh10U3hHoh7A9SRKVO8RmQc=3D
=3Duoiw
=2D----END PGP SIGNATURE-----