[Kolab-devel] Samba KEP (Re: Enhancing Kolab decision making (re: Is it okay to commit the samba patch to cvs?))

[Bernhard Reiter]

On Freitag, 19. September 2008, Gunnar Wrobel wrote:
> Complete applications  
> have completely different needs concerning the testing. You already  
> mentioned that this has (or is) a problem with the Kolab Server web  
> client which did not get the testing to make it rock solid in the  
> current server version.
>
> Would a decision on such a KEP also be a community process? The  
> testing would still be done by KK.

I consider a community process to be good. The Kolab Konsortium is one
part of the community, maybe a very important part and often driving
development and progress. Still we value the full community.

We can define criteria as a community to take up things,
one would be having a maintainer and a good perspective on the component in 
question.

> I believe we should just try to be more open to such extensions and  
> provide some upload place or some other structures instead of going  
> all KEPpy on extensions that provide new applications.

Well, we can do extensions out of the core as much as we want to.
Anybody can do this right away even without asking the Kolab development 
community. Again then comes the question: Shall we (as in the community) pick 
it up for the core?


-- 
Managing Director - Owner: www.intevation.net      (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20081017/14a222d5/attachment.sig>