Jérôme WAGNER wrote:
> ## automatic drawing of library dependency ##
>  It could be a nice thing to have a regular extract of the build system in 
>  the form of a graph of dependency of the libraries
> 

Should be no problem. All you need is the graphviz package.

> ## improve bug screening / ticket management ##
>  we have had a growth in the number of ticket in the last months, but the 
>  tickets do not seem to self-organize. We have to find a way to improve the 
>  ticket screening processes

And better categories, and new ones. scons is obsolete :P

> 2. Build system
> 
> ## cmake support ##
>  the cmake effort must go on until all platforms are totally supported 
>  under cmake

I must say I'm not very happy with owbuild, it confuses me much more
than it helps. But tankuy thinks it is good, so I will use it and help
to develop it.

> 
> ## restructuring the source tree ##
>  the source tree has lived a lot of evolution and need a deep cleaning

This should be done as soon as possible!!!!

> 
> ## restructure phapi ##
>  phapi should be splitted into its subsystem libraries and be available as 
>  an autonomous development package. It should be easy to develop and test 
>  on phapi

You should rename eXosip and osip. What we have in tree isn't really
eXosip it is a fork of eXosip.

> 
> ## 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 :)

> 
> ## simplify project compile time configuration ##
>  Generate a config.h file instead of thousand -Ddefines

I will help tanguy to do that.

> 
> ## monitor cpack evolution and use it ##
>  cpack is a packaging tool that is developed in the cmake galaxy. It is not 
>  quite ready for production time but could help a lot

Bill Hoffman from Kitware contacted me and offered help to get CPack and
CTest working.

## Build Wengophone without FFMPEG ##
  it is not possible to ship WengoPhone on some distributions cause they
  can't ship it due the use of ffmpeg.

> 
> 3. Quality assurance
> 

## Develop on x86_64 systems ##
  Developing application on x86_64 system will help to make sure it
  works on other platforms too.

## Fix compiler warnings ##
  Fix warnings, which often leads too crashes or some other obscure
  things.

## Read the debug output of the console ##
  Looks like developers don't check the debugging log very often. On
  Linux the ALSA device list is requested about 10 times on startup.

> 
> 5. Media quality
> 
> ## optimize video rendering backends ##
>  we already have code for directshow and opengl. It could be used 
>  selectively on the different platforms to optimize the rendering
> 
> ## video codec plugin system in phapi, and new plugins ##
>  theora is a must, h264 could be very interesting too. Code is already well 
>  advanced thanks to a patch from Mathias Schneider
> 

Maybe we can replace FFMPEG with theora. Use only open formats.

> ## automatic gain control for audio ##
>  audio volume level (MIC and SPK) should auto-adjust to maximize/optimize 
>  the audio experience of the user

Please not only auto-adjust. Make it configurable so that the user can
choose what he wants :)

> 14. Portability
> 
> ## Linux effort ##
>  this effort will try to eradicate the last long standing issues that exist 
>  under linux
> 
> ## Linux: make it ring ##
>  under linux, the WengoPhone is not ringing when receiving an entering call

Btw. why don't you use the plughw interfaces of ALSA??

The most important ALSA interfaces to the PCM devices are the "plughw"
and the "hw" interface. If you use the "plughw" interface, you need not
care much about the sound hardware. If your soundcard does not support
the sample rate or sample format you specify, your data will be
automatically converted. This also applies to the access type and the
number of channels. With the "hw" interface, you have to check whether
your hardware supports the configuration you would like to use.

http://www.suse.de/~mana/alsa090_howto.html

> 
> ## x86_64 port ##
>  make the WengoPhone work under the x86_64 architecture

It should work before the 2.0 release.

> 15. Bugs/Enhancements
> 
> 
> ## Linux: improve resampling ##
>  with some audio cards under linux, resampling gets crazy and the sound is 
>  crappy. It is necessary to debug this

plughw?

> 16. Third-party
> 
> ## compile without ffmpeg ##
>  it is necessary to have a target that allows to compile without ffmpeg

Would it be possible to use only theora?

        -- andreas

-- 
http://www.cynapses.org/ - cybernetic synapses


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Reply via email to