Remote Consensus: Difference between revisions
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
* The measurement of consensus by counting the number of '''oppositions''' | * The measurement of consensus by counting the number of '''oppositions''' | ||
* The final interpretation of the consensus is the responsibility of the Chairman who ratifies the decision(s) at the end of the Remote Consensus period. Notifications related to each Remote Consensus are automatically disseminated to the TB/ISG mailing list. '''NOTE:''' To be able to receive Remote Consensus notifications, members must be subscribed to the TB/ISG membership list. | * The final interpretation of the consensus is the responsibility of the Chairman who ratifies the decision(s) at the end of the Remote Consensus period. Notifications related to each Remote Consensus are automatically disseminated to the TB/ISG mailing list. '''NOTE:''' To be able to receive Remote Consensus notifications, members must be subscribed to the TB/ISG membership list. To subscribe: <nowiki>https://portal.etsi.org/webapp/TBMembershiplist</nowiki> | ||
=== '''Recommendations for the duration of a Remote Consensus''' === | |||
* The ETSI Directives do not impose a fixed duration, however the Chairman is advised to maintain a minimum period of 3 days to respect the global membership of ETSI across different time zones. | |||
* Type DEC for Contributions such as a Liaison Statement or a Change Request (CR) – a minimum of 3 days. | |||
* Type DEC for Contributions such as a Final Draft for Approval or a Meeting Report – a minimum of 7 days. | |||
Revision as of 14:08, 23 October 2018
Scope of the Remote Consensus application
A Remote Consensus enables a TB/ISG to take decisions on Contributions (Drafts, Liaison Statements, Change Requests, Reports) outside of a face-to-face meeting.
Types of Remote Consensus:
- Consensus Measuring for Decisions
- Comments Collecting for Discussion The application allows:
- The collection of comments
- The measurement of consensus by counting the number of oppositions
- The final interpretation of the consensus is the responsibility of the Chairman who ratifies the decision(s) at the end of the Remote Consensus period. Notifications related to each Remote Consensus are automatically disseminated to the TB/ISG mailing list. NOTE: To be able to receive Remote Consensus notifications, members must be subscribed to the TB/ISG membership list. To subscribe: https://portal.etsi.org/webapp/TBMembershiplist
Recommendations for the duration of a Remote Consensus
- The ETSI Directives do not impose a fixed duration, however the Chairman is advised to maintain a minimum period of 3 days to respect the global membership of ETSI across different time zones.
- Type DEC for Contributions such as a Liaison Statement or a Change Request (CR) – a minimum of 3 days.
- Type DEC for Contributions such as a Final Draft for Approval or a Meeting Report – a minimum of 7 days.