[ previous ] [ next ] [ threads ]
 To :  Diana Cionoiu <diana-liste@v...>,Yate mailing list <yate@v...>
 From :  Maciek Kaminski <maciejka@t...>
 Subject :  Re: [yate] YATE community was: yate wikipedia
 Date :  Mon, 13 Aug 2007 17:49:59 +0200
Diana Cionoiu napisał(a):
> Hello Maciek,
> I fully understand you. I have to admit that since 1 December 2006 we 
> had so much work that was impossible to provide much infos.
> We've added ISDN, SS7, RBS is on the way, MGCP already works (Paul made 
> a cool module that is a hearthbeat for LHA), the new php library that 
> will be used by YateAdmin and so on. We've hired someone to write a 
> manual, and i will hire someone to that will have as a job to talk with 
> the community. However all those things have been quite hard to make 
> them, and it took a while.
> We will probably move in a new office in about a month (i know we did 
> that in February but is a must), and that will allow the company to 
> grow, and i hope to hire some more people especially on support and 
> documentation.

I admire that.

> The problem with external patches now is that Paul is the only one that 
> commits them because this is the only way to keep the quality of Yate at 
> the same level.

There are open source projects that achieve high quality in distributed 
manner. So probably it is not the only way.

> Regarding Yaypm we need to find some way to discuss about how to develop 
> those stuff to get in the main branch. We need some sort of policy. 

Probably for subprojects like yaypm which does not have a nature of one 
file patch a branch in cvs can be created. You can give trusted people 
access to certain directory. Then you can update main branch with the 
files you like. That would allow more people to cooperate on, for 
example yaypm code.

Developing without code repository is frustrating I must say. Developing 
open source software is impossible.

> I have to admit that I've never expected someone to develop so much 
> externaly to Yate, so i have no idea how to handle it. 

That is selffulfiling prophesy. You won't have thriving community unless 
you expect it to develop outside.

 > Like in which directory and we also need documentation both
 > for API and for the application himself.

Of course I can write more documentation. It is a matter of compilation