[ previous ] [ next ] [ threads ]
 To :  yate@v...
 From :  Maciek Kaminski <maciejka@t...>
 Subject :  Re: [yate] YATE community was: yate wikipedia
 Date :  Mon, 13 Aug 2007 11:28:33 +0200
Anand Kumria wrote:
> ...
> Well the thing is, perhaps the "community" needs some asssistance.
> ...

Here is my view: Null Team does a terrific job developing new high 
quality features. Features that makes them able to work so effectively 
in such a small(you know, null :-)) team makes community weak: 
Apparently they are very good at software architecture so they don't 
need much input, that is why most communications are usually one way. 
They are very good at coding and so busy doing it that they don't have 
time to pay to much attention to community.

That is not gonna change easily I am afraid.

Question is what community can do to help Null Team to make it better? 
Pointing general things like "not enough beginner documentation" is so 
obvious that does not help much. They don't have resources to do it.

Is there a way to get experienced yate users more involved in writing 
documentation? I don't know. My personal strategy is to write down in 
wiki things that I learn from others (like wpchan configuration: 
http://yate.null.ro/pmwiki/index.php?n=Main.Wpchan), just not to forget. 
If others would apply that strategy, we won't produce complete 
documentation of course, but at least will be able to gather 
unstructured information until we know how to organize it.

Another thing is documentation for things that I contribute to yate. I 
have written few modules for yate. The biggest one it yaypm. It is 
documented on wiki(http://yate.null.ro/pmwiki/index.php?n=Main.YAYPM) 
and I have written article for 
about it. What would I need beside community interest to work harder on 
yaypm source and documentation? Probably a little more support from Null 
Team than I get today. It is very difficult to get updates and new 
features get into cvs. I am not even asking about direct access to 
repository which would be most convenient, simple patches needs to wait 
months before they are committed. It does not make sense to write 
documentation on wiki for software that stays on my harddrive.

Recently I started to work on project that is going to use yaypm 
extensively. I will develop new features. I would like to share them 
with community. If I won't get more support I will have to move yaypm to 
some public repository I am afraid.