|
|
| Line 1: |
Line 1: |
| == 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.
| |
| 1.1 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/
| |
|
| |
|
| 1.2 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.
| |
| Type DIS for Contributions such as CRs – a minimum of 7 days.
| |
| - It is recommended to group Contributions into one Remote Consensus.
| |
| 2 Getting started - How to access the Remote Consensus tool
| |
| NOTE: Only community officials: Chairman, Vice Chairman, Secretary and ETSI Support staff can set up, manage and ratify a Remote Consensus.
| |
| Users must be logged on the portal to use the application
| |
| • Open the ETSI portal https://portal.etsi.org and log in with your EOL account
| |