Hi Andreas, Andreas Schneider wrote: > You should rename eXosip and osip. What we have in tree isn't really > eXosip it is a fork of eXosip.
I'd prefer us to analyse the diffs and and get the stuff we need upstream, and get eXosip and osip out of the tree. >> ## create "wengophone developer bundles" or "devpacks" ## >> these will greatly facilitate the entry of new developers in the >> community. The devpacks will allow them to download just what they need >> depending on what they want to work on. These devpacks could integrate >> precompiled binaries of some libreries > > But only for Windows please :) I agree - on Linux we need to do the opposite - to make Wengo more easily packagable, we need to remove all of the third party sources - ffmpeg, libgaim, curl - I am sure there are others that we can remove too. > Bill Hoffman from Kitware contacted me and offered help to get CPack and > CTest working. Great! > Maybe we can replace FFMPEG with theora. Use only open formats. This is a great goal - but probably not a top priority, since switching to Theora is, at best, a change which will give the same functionality we have now. It seems to me that we are missing lots of things which we can easily improve and which will have a big impact on the user experience. If switching to Theora can fix a distribution issue we should look at it to see what amount of work is involved. > http://www.suse.de/~mana/alsa090_howto.html Thanks for the reference. >> ## x86_64 port ## >> make the WengoPhone work under the x86_64 architecture > > It should work before the 2.0 release. I've been thinking of a way that we can release stable versions on platforms which work well (osx/intel, osx/ppc and windows/x86) and somehow delay versions on x86_64 and Linux - having tried to use it for a couple of weeks, I don't think the wengophone on Linux is ready for a release that we can be proud of and I would really like the release 2.0 on Linux to rock. I don't think we can justify delaying releases that work well for one that doesn't. We should, however, ensure that we don't end up in the same situation again for future releases. Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
