Some general guidelines: - It must be Apache 2.0 or compatible licensed to be accepted as part of the standard platform. For example, no GPL or LGPL code.
- Efficient code is important. You'll want to look at the code you are providing to make sure it is reasonable to run on an embedded platform, or put in the time to fix it yourself. Generally you will find that code that was written for desktop computers (especially Java code) will at least need some non-superficial work to be acceptable. That said, I really don't know about what plans there are for this kind of feature, so hopefully someone else can address that. On Thu, Dec 4, 2008 at 2:57 PM, friedger <[EMAIL PROTECTED]> wrote: > > Hi, > > I am interested in adding a sip stack/voip to the framework. I am > aware that some network provider and android market do not allow such > features. However, it still should be included in the framework > source. > > Where would be the best place to start? There are already existing > java libraries like jcommunicator, jain sip, or MJSIP. > > Is the kernel the better place? > > Friedger > > > > -- Dianne Hackborn Android framework engineer [EMAIL PROTECTED] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
