3 ms·
Does Ericsson plan to maintain and update this implementation (my understanding is that WebRTC is still an evolving standard) or is this the kind of "we're aban
by rockdoe 12y ago
Does Ericsson plan to maintain and update this implementation (my understanding is that WebRTC is still an evolving standard) or is this the kind of "we're abandoning the project and dropping the maintenance burden on the open source community" kind of thing that this kind of announcement usually means? Closed source projects opening their code don't generally end up very successful if they're "dead drops".
As an aside, I notice that the first issue in the github is "implement H265". That seems like a weird priority if you saw what needed to happen to get Mozilla and Google to even consider supporting H264. I think Firefox still doesn't support it and uses VP8.
- stalund 12y agoI'm the Ericsson Research person responsible for the release. This release is not about throwing code over the fence. We have developed OpenWebRTC over last few years and are using it to build various applications. This will continue, with the difference that we will maintain the OpenWebRTC framework in the open. That being said, we are a relatively small team. For OpenWebRTC to remain competitive as the WebRTC standard continues to evolve and people find new uses for the technology, we hope to get as many external developers involved as possible. OpenWebRTC builds on GStreamer which is a well-maintained project with a active community. Improvements in GStreamer will therefore almost automatically be reflected in OpenWebRTC. To be completely transparent Bowser is not our top priority, OpenWebRTC is. Bowser primarily serves as a demo application for OpenWebRTC and is a good way for people to try out the technology before committing to it. Some people will find Bowser very useful, especially while WebRTC support is missing on other iOS browsers, and we are happy for any value it creates.