Talkilla: Difference between revisions
| Line 3: | Line 3: | ||
== What is Talkilla? == | == What is Talkilla? == | ||
Talkilla uses [https://wiki.mozilla.org/Media/WebRTC WebRTC] to | Talkilla uses [https://wiki.mozilla.org/Media/WebRTC WebRTC] to add real-time communications to the user's web browsing experience. Talkilla is initially designed for Firefox browsers but will also support other WebRTC browsers. | ||
The first service to be delivered in Talkilla will allow users to communicate in real time as they browse the web, and offer tools to share their online experience. Additional Service Providers will be able to leverage this framework to expose their service. For example, dialing out and receiving calls from the telephone network through the user's own telecommunication operator. | The first service to be delivered in Talkilla will allow users to communicate in real time as they browse the web, and offer tools to share their online experience. Additional Service Providers will be able to leverage this framework to expose their service. For example, dialing out and receiving calls from the telephone network through the user's own telecommunication operator. | ||
Revision as of 20:32, 16 April 2013
|
THIS PAGE IS A WORKING DRAFT | 
|
| The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page. |
What is Talkilla?
Talkilla uses WebRTC to add real-time communications to the user's web browsing experience. Talkilla is initially designed for Firefox browsers but will also support other WebRTC browsers.
The first service to be delivered in Talkilla will allow users to communicate in real time as they browse the web, and offer tools to share their online experience. Additional Service Providers will be able to leverage this framework to expose their service. For example, dialing out and receiving calls from the telephone network through the user's own telecommunication operator.
Talkilla is the code-name for the project.
Why Talkilla?
Integrating real time communications into the browser will enhance a user's browsing experience allowing conversations to continue alongside Web navigation and the improved sharing of online resources. With the integration into the browser also comes flexibility for users to easily shift calls between devices and locations.
WebRTC does not standardize peer discovery nor does it touch on contact and presence management. This is a significant hurdle for web sites to fully leverage Real Time Communication. Talkilla aims at offering some of those features through web application APIs, as a reflection of what individual Service Providers have to offer.
In addition, Talkilla provides a set of ready made use cases UI in order to deliver a tightly integrated real time communication experience in the browser. Using those, operators will for example be able to expand their networks with Talkilla to let their users make and receive calls to and from the Internet and provide them with value-added services.
More generally, developers will be provided with APIs where they can hook into Talkilla and provide different functionalities and web applications for users based on Talkilla's core services.
Goals
Talkilla will provide:
- an experience that allows people to communicate/interact to/with each other without boundaries
- an improved browsing experience
Talkilla will enable:
- an ecosystem to improve browsing experience
- usable by websites
- usable services providers
Core Team
| Role | Contacts |
|---|---|
| Project Champion |
|
| Project Lead |
|
| Back-end Technical Lead |
|
| Front-end Leads |
|
| Browser Integration Lead |
|
Development
- Development of new features takes place via user stories
- User stories for Talkilla are visible on Trello
- Code development takes place in a github repository. Please read:
- README.md for information on how to build and run Talkilla
- CONTRIBUTING.md for information on how to contribute to Talkilla
Due to the early stages of development, we are not accepting bugs at the current time. This will change in the near future.
Pull requests will be accepted, as per the contributing guidelines.
If you have any questions, please ask on the mailing list in the communication section.