[Kroupware] Kolab Development process

[Bernhard Reiter]

Hi  Joël,

Stephan already answered most of the questions.

Let me only add a detail on the development process question.
The kolab-devel list is the contact point to reach the developers
and the community to make a decision. 
Everybody is welcomed to join.

Naturally the decisions are taken by the current maintainers 
and technical leaders after discussion on this lists.
They also decide who is able to get CVS write access.

Currently the members of the original and now concluded Kroupware
project and Stephan Buys from Codefusion (South Africa)
have direct CVS write access.

Bernhard

On Thursday 07 August 2003 08:44, Stephan Buys wrote:
> On Thursday 07 August 2003 01:20, Joël SAUNIER wrote:

> > The second question is about the development process the
> > kolab team will used. The team try to start a large
> > community for kolab, and it's a good thing. But how the
> > community contributions will be include in a future
> > release ? Who will accept or reject these contributions ?
>
> The best place to start is to send your contributions to the kolab-devel
> mailing list in patch form. The maintainers can then pick up the work
> and commit it to CVS. The server portion is maintained by Erfrakon and
> the client side is maintained by Klarälvdalens Datakonsult. Of course
> there is opportunity to get write/read access to CVS as well.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2145 bytes
Desc: signature
Url : http://mail.kde.org/pipermail/kroupware/attachments/20030807/59a86703/smime.bin