Monitor WebRTC management before changes are coded?

[David Gray]

How do we get involved in the management WebRT, to monitor planned changes to before these changes are coded? 

[Alexandre GOUAILLARD]

There is no roadmap per say (even if google sometimes announces changes to come at Kranky Geek).

Bugs are the closest thing to a roadmap, stars those you want to be addressed in priority, and check the priority of each bug to get a feeling about how likely they are to be addressed. You might want to monitor both webrtc bugs and chromium bugs.

https://bugs.chromium.org/p/webrtc/issues/list

https://bugs.chromium.org/p/chromium/issues/list

To check code being implemented, monitoring the review website is also interesting.

https://webrtc-codereview.appspot.com

finally, the commits themselves are interesting:

https://chromium.googlesource.com/external/webrtc/+log/master

On Fri, Dec 2, 2016 at 11:27 PM, David Gray <dg...@grayscomm.com> wrote:

How do we get involved in the management WebRT, to monitor planned changes to before these changes are coded? 

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/cee5c927-d126-4381-8d4c-22cd756391f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alex. Gouaillard, PhD, PhD, MBA

------------------------------------------------------------------------------------

President - CoSMo Software Consulting, Singapore

------------------------------------------------------------------------------------

sg.linkedin.com/agouaillard

• 
  

[Taylor Brandstetter]

The priority and number of stars on an issue are definitely correlated to how fast it gets fixed; I recommend that everyone "star" the bugs/feature requests that are most important to them.

You could also look at the milestone label (for example, "M-57") to see what release of Chrome a feature is planned for. In the past we've been a bit lax about using this field, but we're starting some new bug management policies that will hopefully make milestones more accurate.

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAHgZEq5gNTqq94U_hDANq9tyXU1QfLt9gwgAsPvsqd_amOFVzg%40mail.gmail.com.