You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WebRTC 1.0 is now at CR, which was the defined trigger for starting work on 2.0 in the previous charter. Nevertheless, implementation of the specification is still in its early stages. Although Microsoft has long advocated the object-focused approach, at this particular juncture we question whether it is advisable to start standardization of a 2.0 object model before the 1.0 object model has been implemented.
Delaying formal work 2.0 in the WG until the WebRTC 1.0 object model's "deployment blocking" Issues have been addressed would be more efficient. We hope this will happen by the time the 1.0 CR "recycles", but this is a technical condition, not a process milestone.
The text was updated successfully, but these errors were encountered:
Do you have a particular list of issues that you want to get tagged as "deployment blocking"?
Now that we can retire the "CR blocker" label, we can start on new labelling.
Looking at the current charter text, I see that we already have
"The highest priority of the group in this charter period will be to get the core recommendations progressed towards Recommendation status. "
I think this sufficiently addresses the issue.
The resources that are willing to spend time on 1.0 progression and teh resources that are willing to spend time on object model proposals have overlaps, but it's not the same persons.
WebRTC 1.0 is now at CR, which was the defined trigger for starting work on 2.0 in the previous charter. Nevertheless, implementation of the specification is still in its early stages. Although Microsoft has long advocated the object-focused approach, at this particular juncture we question whether it is advisable to start standardization of a 2.0 object model before the 1.0 object model has been implemented.
Delaying formal work 2.0 in the WG until the WebRTC 1.0 object model's "deployment blocking" Issues have been addressed would be more efficient. We hope this will happen by the time the 1.0 CR "recycles", but this is a technical condition, not a process milestone.
The text was updated successfully, but these errors were encountered: