Re: [Iaxclient-devel] active development?

[Steve K. <st...@st...>]

On Sep 29, 2004, at 9:38 PM, Ilguiz Latypov wrote:

>
> On Wed, Sep 29, 2004 at 09:57:59PM -0300, an...@mo... 
> wrote:
>> Or everyone that is working with this project keep the new code
>> private and forget about contribute back? What happens?

I started the project, and since then, there have been a few people who 
have contributed.   I have plans for the future of the library as well, 
including better jitterbuffer support, codecs, and eventually video 
support.

Whether others contribute is mainly up to them.  Presently, this is the 
only open iax client library of it's kind out there.  There's Firefly, 
which is proprietary except for libiax2, and there seems to be another 
mainly proprietary client coming soon.

Contributions and discussion of direction are surely welcome.    If you 
were to ask why there wasn't much activity, it would be mainly that 
there aren't enough interested and capable developers out there 
stepping up.  I should also probably put some links to the project on 
the voip-info wiki, so people can see what's going on.

The people who have contributed so far, are basically occupied with 
other things.  The code here works, so we've all scratched our 
immediate itches, so to speak.

> I guess it is always possible to check out the sourceforge CVS tree and
> implant it into your own CVS repository as a "vendor branch".  The
> subsequent changes by the mainstream developers can be not only 
> imported
> into the "vendor branch" but also applied to the local main branch.
>
> Even better, the original CVS tree can be converted into a Subversion
> "vendor branch" tree by using a certain script from the Subversion
> project.  Another script exists in the same project that will recognize
> file name changes in the updated "vendor branch", so that the same
> changes would be intelligently re-applied by Subversion to your own
> branch.
>
> In any way, local changes can co-exist with the mainstream changes in
> the local repository.  I think the GPL licence would then mandate to
> make at least the local snapshot available at request as soon as its
> results are traded.

That's correct.  I do keep a copy of the library in a private CVS tree, 
but that is basically a copy of what is here;  I just keep it so that I 
can re-create my library if sourceforge were to disappear.  (Actually, 
the library is _L_GPL, which means that your own front-ends, for 
example, don't need to be contributed back, but changes to the library 
proper do).

I would suggest that people try to make changes that are helpful for 
everyone, and contribute them back here.   It is a bit more work at 
first as opposed to just making your own changes (i.e. if you're only 
developing for a single platform, you need to make sure your changes 
are portable), but in the end, if people all do that, then we don't 
progress as a community and people end up re-inventing the wheel, etc.

-SteveK