Remote Consensus - Revision history

Darda: Clarification about - Issue a notification to the TB/ISG mailing list for the users monitoring the contribution.

2025-12-10T15:38:13Z

Clarification about - Issue a notification to the TB/ISG mailing list for the users monitoring the contribution.

Darda at 13:09, 5 December 2025

2025-12-05T13:09:53Z

← Older revision		Revision as of 14:09, 5 December 2025
Line 157:		Line 157:
	- Add the submitter to all future notifications on this Contribution.		- Add the submitter to all future notifications on this Contribution.

	'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the [https://help.etsi.org/index.php?title=Remote_Consensus#~~Weekly_report_notification:~:text=from%200%20users-,Remote%20Consensus%20guidelines,-%5Bedit%20%7C~~ Remote Consensus guidelines].		'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the [https://help.etsi.org/index.php?title=Remote_Consensus#Remote_Consensus_guidelines Remote Consensus guidelines].

	== Raising an opposition to a Contribution ==		== Raising an opposition to a Contribution ==
Line 178:		Line 178:
	- Adds the user to all future notifications on this Contribution		- Adds the user to all future notifications on this Contribution

	'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the [https://help.etsi.org/index.php?title=Remote_Consensus#~~Weekly_report_notification:~:text=from%200%20users-,Remote%20Consensus%20guidelines,-%5Bedit%20%7C~~ Remote Consensus guidelines].		'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the [https://help.etsi.org/index.php?title=Remote_Consensus#Remote_Consensus_guidelines Remote Consensus guidelines].

	== Clearing an opposition to a Contribution ==		== Clearing an opposition to a Contribution ==
Line 195:		Line 195:
	- Issue a notification to the TB/ISG mailing list.		- Issue a notification to the TB/ISG mailing list.

	'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the [https://help.etsi.org/index.php?title=Remote_Consensus#~~Weekly_report_notification:~:text=from%200%20users-,Remote%20Consensus%20guidelines,-%5Bedit%20%7C~~ Remote Consensus guidelines].		'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the [https://help.etsi.org/index.php?title=Remote_Consensus#Remote_Consensus_guidelines Remote Consensus guidelines].

	== Weekly report notification ==		== Weekly report notification ==

Darda at 16:42, 4 December 2025

2025-12-04T16:42:46Z

← Older revision		Revision as of 17:42, 4 December 2025
Line 157:		Line 157:
	- Add the submitter to all future notifications on this Contribution.		- Add the submitter to all future notifications on this Contribution.

	'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the Remote Consensus guidelines.		'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the [https://help.etsi.org/index.php?title=Remote_Consensus#Weekly_report_notification:~:text=from%200%20users-,Remote%20Consensus%20guidelines,-%5Bedit%20%7C Remote Consensus guidelines].

	== Raising an opposition to a Contribution ==		== Raising an opposition to a Contribution ==
Line 177:		Line 177:

	- Adds the user to all future notifications on this Contribution		- Adds the user to all future notifications on this Contribution

			'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the [https://help.etsi.org/index.php?title=Remote_Consensus#Weekly_report_notification:~:text=from%200%20users-,Remote%20Consensus%20guidelines,-%5Bedit%20%7C Remote Consensus guidelines].

	== Clearing an opposition to a Contribution ==		== Clearing an opposition to a Contribution ==
Line 192:		Line 194:

	- Issue a notification to the TB/ISG mailing list.		- Issue a notification to the TB/ISG mailing list.

			'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the [https://help.etsi.org/index.php?title=Remote_Consensus#Weekly_report_notification:~:text=from%200%20users-,Remote%20Consensus%20guidelines,-%5Bedit%20%7C Remote Consensus guidelines].

	== Weekly report notification ==		== Weekly report notification ==

Darda: /* Weekly report notification */

2025-12-04T16:39:07Z

Weekly report notification

← Older revision		Revision as of 17:39, 4 December 2025
Line 156:		Line 156:

	- Add the submitter to all future notifications on this Contribution.		- Add the submitter to all future notifications on this Contribution.

			'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the Remote Consensus guidelines.

	== Raising an opposition to a Contribution ==		== Raising an opposition to a Contribution ==
Line 168:		Line 170:
	The system will then:		The system will then:

	Create a record of the new opposition		- Create a record of the new opposition

	Update the list of oppositions		- Update the list of oppositions

	Issue a notification to the TB/ISG mailing list		- Issue a notification to the TB/ISG mailing list

	Adds the user to all future notifications on this Contribution		- Adds the user to all future notifications on this Contribution

	== Clearing an opposition to a Contribution ==		== Clearing an opposition to a Contribution ==
Line 185:		Line 187:
	The system will then:		The system will then:

	Create a record of the cleared opposition		- Create a record of the cleared opposition

	Update the list of comments or oppositions		- Update the list of comments or oppositions

	Issue a notification to the TB/ISG mailing list.		- Issue a notification to the TB/ISG mailing list.

	== Weekly report notification ==		== Weekly report notification ==
Line 207:		Line 209:
	Example of a report:		Example of a report:

	<blockquote>''Weekly report for '''NFV(18)DEC094''' is sent every '''Thursday''' at 4:00am CET.'' </blockquote><blockquote>''RC status: '''STARTED''' , with 2 available contributions.'' </blockquote><blockquote> ''0 comments.''</blockquote><blockquote>''RAISING COMMENTS AND OPPOSITIONS is ALLOWED until Wednesday 2018-10-24 at midnight.''</blockquote><blockquote> '''''NFV(18)000269''' (download) '''Draft - DGS/NFV-EVE011 v0.0.20 (GS NFV-EVE 011 ) "Cloud Native VNF Classification Spec"'''''</blockquote><blockquote> ''Decision Requested : Please approve''</blockquote><blockquote> ''0 sustained oppositions (0 cleared oppositions) and 0 comments from 0 users'' </blockquote><blockquote> '''''NFV(18)000271''' (download) '''Draft - DGR/NFV-IFA012 v0.13.1 (GR NFV-IFA 012 ) "Os-Ma-Nfvo ref point Spec - svc mgmt & info model"''''' </blockquote><blockquote> ''Decision Requested : Please approve''</blockquote><blockquote> ''0 sustained oppositions (0 cleared oppositions) and 0 comments from 0 users'' </blockquote>~~<blockquote> </blockquote><blockquote>'''''~~Remote Consensus guidelines~~:'''''</blockquote><blockquote> ''~~A Remote Consensus (RC) allows approving or just gathering comments either on one single contribution or on a set of contributions grouped together. A single approval period is set for the whole group, and a single report monitors all the results.~~''</blockquote><blockquote> </blockquote><blockquote> ''~~During the RC period ETSI members subscribed to the related TB mailing list can add comments and/or raise oppositions on any of the contributions in the RC. Users can also monitor a contribution to receive an email each time a comment is added, or they can wait for the (optional) weekly report email to receive the status and comments on all contributions.~~''</blockquote><blockquote> ''~~Comments (and oppositions) collected during the RC period can be viewed at any time via the '''RC Report'''~~''</blockquote><blockquote> </blockquote><blockquote> ''~~At the end of the RC approval period, an official reviews all comments, RATIFIES the result by recording an output status for each contribution.''~~</blockquote><blockquote>~~ '~~'There are~~ two types of Remote Consensuses:''<~~/blockquote~~>~~<blockquote> ''1-~~ "Consensus measuring" RCs: a DECISION is expected at the end of the approval period, these can only contain contributions for decision~~'' </blockquote>~~<~~blockquote~~> ~~''2-~~ "Comment collecting" RCs do not imply a decision at the end of the period, these can only contain contributions for DISCUSSION.~~''</blockquote><blockquote> </blockquote><blockquote> ''~~For consensus measuring RCs the application lists the number of sustained oppositions (as defined in ETSI Working Procedures). For comment collecting, comments are allowed but raising oppositions is not possible.~~''</blockquote><blockquote> </blockquote><blockquote> ''~~Participants can add comments, raise an oppositions, but also remove their oppositions at any time during the approval period.~~''</blockquote><blockquote> </blockquote><blockquote> ''~~When all contributions have been ratified, the Remote Consensus is considered as ratified.~~'' </blockquote><blockquote> </blockquote><blockquote>~~ ''Remote Consensus lifecycle: PLANNED - (FROZEN) - STARTED - TO BE RATIFIED - RATIFIED''<~~/blockquote><blockquote~~> ''Only officials and support staff can create a Remote Consensus for their TB.''</~~blockquote><blockquote~~> '' -PLANNED: all delegates can add/remove contributions to/from the RC.''~~</blockquote><blockquote>~~ ''-FROZEN: only officials and support staff can add/remove contributions to the RC.''~~</blockquote><blockquote>~~ '' -STARTED: delegates can add comments, and raise or remove oppositions on contributions.''~~</blockquote><blockquote>~~ '' -TO BE RATIFIED: RC period if finished, officials and support staff are expected to ratify results.''~~</blockquote><blockquote>~~ '' -RATIFIED: all contributions of the RC have been ratified.'' ~~</blockquote><blockquote> ''More help [[Remote Consensus\|here]]'' </blockquote>~~		<blockquote>''Weekly report for '''NFV(18)DEC094''' is sent every '''Thursday''' at 4:00am CET.'' </blockquote><blockquote>''RC status: '''STARTED''' , with 2 available contributions.'' </blockquote><blockquote> ''0 comments.''</blockquote><blockquote>''RAISING COMMENTS AND OPPOSITIONS is ALLOWED until Wednesday 2018-10-24 at midnight.''</blockquote><blockquote> '''''NFV(18)000269''' (download) '''Draft - DGS/NFV-EVE011 v0.0.20 (GS NFV-EVE 011 ) "Cloud Native VNF Classification Spec"'''''</blockquote><blockquote> ''Decision Requested : Please approve''</blockquote><blockquote> ''0 sustained oppositions (0 cleared oppositions) and 0 comments from 0 users'' </blockquote><blockquote> '''''NFV(18)000271''' (download) '''Draft - DGR/NFV-IFA012 v0.13.1 (GR NFV-IFA 012 ) "Os-Ma-Nfvo ref point Spec - svc mgmt & info model"''''' </blockquote><blockquote> ''Decision Requested : Please approve''</blockquote><blockquote> ''0 sustained oppositions (0 cleared oppositions) and 0 comments from 0 users'' </blockquote>

			== Remote Consensus guidelines ==
			A Remote Consensus (RC) allows approving or just gathering comments either on one single contribution or on a set of contributions grouped together. A single approval period is set for the whole group, and a single report monitors all the results.


			During the RC period ETSI members subscribed to the related TB mailing list can add comments and/or raise oppositions on any of the contributions in the RC. Users can also monitor a contribution to receive an email each time a comment is added, or they can wait for the (optional) weekly report email to receive the status and comments on all contributions.


			Comments (and oppositions) collected during the RC period can be viewed at any time via the '''RC Report'''

			At the end of the RC approval period, an official reviews all comments, ''RATIFIES'' the result by recording an output status for each contribution.


			There are '''two types of Remote Consensuses''':

			# <u>"Consensus measuring"</u> RCs: a DECISION is expected at the end of the approval period, these can only contain contributions for decision
			# <u>"Comment collecting"</u> RCs do not imply a decision at the end of the period, these can only contain contributions for DISCUSSION.


			For consensus measuring RCs the application lists the number of sustained oppositions (as defined in ETSI Working Procedures). For comment collecting, comments are allowed but raising oppositions is not possible.

			Participants can add comments, raise an oppositions, but also remove their oppositions at any time during the approval period.

			When all contributions have been ratified, the Remote Consensus is considered as ratified.


			''Remote Consensus lifecycle: '''PLANNED - (FROZEN) - STARTED - TO BE RATIFIED - RATIFIED'''''

			'''!!!''' <u>Only officials and support staff can create a Remote Consensus for their TB.</u>

			* ''PLANNED: all delegates can add/remove contributions to/from the RC.''

			* ''FROZEN: only officials and support staff can add/remove contributions to the RC.''

			* ''STARTED: delegates can add comments, and raise or remove oppositions on contributions.''

			* ''TO BE RATIFIED: RC period if finished, officials and support staff are expected to ratify results.''

			* ''RATIFIED: all contributions of the RC have been ratified.''

	== The end of a Remote Consensus ==		== The end of a Remote Consensus ==

Belchankova: /* Recommendations for the duration of a Remote Consensus */

2024-03-08T09:20:25Z

Recommendations for the duration of a Remote Consensus

← Older revision		Revision as of 10:20, 8 March 2024
Line 37:		Line 37:
	'''NOTE:''' To be able to receive Remote Consensus notifications, or to post a Remote Consensus comment (or opposition) members must be subscribed to the TB/ISG membership list. To subscribe: [https://portal.etsi.org/webapp/TBMembershiplist '''https://portal.etsi.org/webapp/TBMembershiplist''']		'''NOTE:''' To be able to receive Remote Consensus notifications, or to post a Remote Consensus comment (or opposition) members must be subscribed to the TB/ISG membership list. To subscribe: [https://portal.etsi.org/webapp/TBMembershiplist '''https://portal.etsi.org/webapp/TBMembershiplist''']
	=== Recommendations for the duration of a Remote Consensus ===		=== 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.~~		The ETSI Directives mandate the following:

	~~Type DEC for Contributions such as~~ a ~~Liaison Statement or a Change Request~~ (CR) ~~– a minimum~~ of ~~3 days.~~		a clear definition of the proposal(s), and the duration of the time period for submitting comments and/or objections, shall be disseminated by the Chair of the Technical Group to the membership list at least seven (7) calendar days before the opening of the consultation;

	~~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.~~

			The time period for participating in the Remote Consensus shall be at least seven (7) calendar days;
	*		*

Vreck: updating ratification paragraph...

2024-02-27T14:21:30Z

updating ratification paragraph...

← Older revision		Revision as of 15:21, 27 February 2024
Line 230:		Line 230:
	=== Final output statuses for a Remote Consensus ===		=== Final output statuses for a Remote Consensus ===
	There are 5 different output statuses for a Contribution in a Remote Consensus		There are 5 different output statuses for a Contribution in a Remote Consensus

	~~'''NOTE''': A ratification comment is mandatory for the output status of a '''REJECTED''' Contribution.~~

	* Click on the Remote Consensus reference in Status '''TO BE RATIFIED'''		* Click on the Remote Consensus reference in Status '''TO BE RATIFIED'''
Line 253:		Line 251:
	[[File:Picture Rem28.png\|frameless]]		[[File:Picture Rem28.png\|frameless]]

	'''~~NOTES~~:''' ~~Status~~ - '''NOTED with revision pre-approved -''' the next revision of ~~the~~ Contribution will automatically be '''ACCEPTED'''.		'''NOTE1:''' When a contribution is - '''NOTED with revision pre-approved -''' the next revision of that Contribution will automatically be '''ACCEPTED''' as soon as available.

			'''NOTE2:'''A ratification comment is mandatory for the output status of a '''REJECTED''' Contribution.

	~~A ratification comment is mandatory~~ for the ~~output status of a~~ '''~~REJECTED~~''' ~~Contribution~~.		'''NOTE3:''' when ratifying a remote consensus which only aims at "collecting comments" (and not for decision), the only ratification option will be "'''NOTED'''" or "'''NOTED with revision requested'''".

	Once all Contributions have been updated, the portal will show the status '''RATIFIED''' and a final notification will be sent to the TB/ISG mailing list.		Once all Contributions have been updated, the portal will show the status '''RATIFIED''' and a final notification will be sent to the TB/ISG mailing list.

Vreck: Added text on user access, and required presence on TB membership list

2021-10-14T09:31:56Z

Added text on user access, and required presence on TB membership list

← Older revision		Revision as of 10:31, 14 October 2021
Line 35:		Line 35:
	Notifications related to each Remote Consensus are automatically disseminated to the TB/ISG mailing list.		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 '''https://portal.etsi.org/webapp/TBMembershiplist''']		'''NOTE:''' To be able to receive Remote Consensus notifications, or to post a Remote Consensus comment (or opposition) members must be subscribed to the TB/ISG membership list. To subscribe: [https://portal.etsi.org/webapp/TBMembershiplist '''https://portal.etsi.org/webapp/TBMembershiplist''']
	=== Recommendations for the duration of a Remote Consensus ===		=== 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.		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.
Line 93:		Line 93:
	[[File:Picture Rem6.png\|frameless\|376x376px]]		[[File:Picture Rem6.png\|frameless\|376x376px]]

	[[File:Picture Rem7.png~~\|frameless\|528x528px~~]]		[[File:Picture Rem7.png]]
	* To add a Contribution either:		* To add a Contribution either:
	* Type the sequence number, for example: '''000021''' and click on the '''Filter'''		* Type the sequence number, for example: '''000021''' and click on the '''Filter'''
Line 118:		Line 118:
	*Find the Contribution for removal and click on the small glasses icon[[File:Glasses_icon.PNG\|frameless]].		*Find the Contribution for removal and click on the small glasses icon[[File:Glasses_icon.PNG\|frameless]].
	* Select the third tab '''Remote Consensus''' and click on the link '''REMOVE'''.		* Select the third tab '''Remote Consensus''' and click on the link '''REMOVE'''.
	[[File:Picture Rem8.png~~\|frameless\|570x570px~~]]		[[File:Picture Rem8.png]]
	* Enter the justification and click '''OK'''.		* Enter the justification and click '''OK'''.
	[[File:Picture Rem9.png\|frameless]]		[[File:Picture Rem9.png\|frameless]]
Line 142:		Line 142:
	'''NOTE:''' An ACTIVE Remote Consensus cannot be modified or stopped.		'''NOTE:''' An ACTIVE Remote Consensus cannot be modified or stopped.
	== Submitting a comment to a Contribution in a Remote Consensus ==		== Submitting a comment to a Contribution in a Remote Consensus ==
			Note that submitting a comment (or raising an opposition) is only accessible to users who 1) are authenticated, and 2) have registered on the "TB Membership list" (see [https://portal.etsi.org/webapp/TBMembershiplist '''https://portal.etsi.org/webapp/TBMembershiplist))''']).

	The procedure to submit a Comment to a Comments Collection (DIS) and a Consensus Measuring (DEC) Remote Consensus is identical.		The procedure to submit a Comment to a Comments Collection (DIS) and a Consensus Measuring (DEC) Remote Consensus is identical.

Line 148:		Line 150:
	* Click on the glasses icon [[File:Glasses icon.PNG\|frameless]] to open the Contribution. A new window will open.		* Click on the glasses icon [[File:Glasses icon.PNG\|frameless]] to open the Contribution. A new window will open.
	* Click on '''Comment'''. By default the comment field is active.Enter text in the '''Write a Comment''' field and click '''Save'''.		* Click on '''Comment'''. By default the comment field is active.Enter text in the '''Write a Comment''' field and click '''Save'''.
	[[File:Picture Rem14.png\|~~frameless\|355x355px~~]]		[[File:Picture Rem14.png\|734x734px]]

	The system will then:		The system will then:
Line 161:		Line 163:

	== Raising an opposition to a Contribution ==		== Raising an opposition to a Contribution ==
			Note that raising an opposition (or submitting a comment) is only accessible to users who 1) are authenticated, and 2) have registered on the "TB Membership list" (see [https://portal.etsi.org/webapp/TBMembershiplist '''https://portal.etsi.org/webapp/TBMembershiplist))''']).
	* Open the Remote Consensus tab		* Open the Remote Consensus tab
	* Click on the Remote Consensus reference (i.e. ERM(18)DEC606) in Status STARTED. A new window will open.		* Click on the Remote Consensus reference (i.e. ERM(18)DEC606) in Status STARTED. A new window will open.
Line 166:		Line 169:
	* Click on '''Raise an opposition'''. By default the comment field is active.		* Click on '''Raise an opposition'''. By default the comment field is active.
	* Enter text in the '''Write a Comment''' field to justify the opposition and click '''Save'''.		* Enter text in the '''Write a Comment''' field to justify the opposition and click '''Save'''.
	[[File:Picture Rem19.png\|~~frameless\|347x347px~~]]		[[File:Picture Rem19.png\|723x723px]]

	The system will then:		The system will then:
Line 183:		Line 186:
	Only the submitter or ETSI Support staff can remove an opposition.		Only the submitter or ETSI Support staff can remove an opposition.
	* Click on the hyperlink '''Clear my opposition''' and add text if appropriate and then '''Save'''.		* Click on the hyperlink '''Clear my opposition''' and add text if appropriate and then '''Save'''.
	[[File:Picture Rem20.png~~\|frameless\|331x331px~~]]		[[File:Picture Rem20.png]]

	The system will then:		The system will then:

Singer: /* Scope of the Remote Consensus application */

2019-05-16T12:16:19Z

Scope of the Remote Consensus application

@@ 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.
+*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: ===
@@ Line 29: / Line 47: @@
 It is recommended to group Contributions into one Remote Consensus.
-== Getting started - How to access the Remote Consensus tool ==
 == Creating a new Remote Consensus ==

Clarke: /* Submitting a comment to a Contribution in a Remote Consensus */

2019-04-29T14:22:18Z

Submitting a comment to a Contribution in a Remote Consensus

← Older revision		Revision as of 15:22, 29 April 2019
Line 149:		Line 149:
	The system will then:		The system will then:

	Create a record of the new comment		- Create a record of the new comment

	Update the list of comments		- Update the list of comments

	Issue a notification to the TB/ISG mailing list		- Issue a notification to the TB/ISG mailing list

	Add the submitter to all future notifications on this Contribution.		- Add the submitter to all future notifications on this Contribution.

	== Raising an opposition to a Contribution ==		== Raising an opposition to a Contribution ==

Clarke: formatting

2019-04-29T14:21:06Z

formatting

← Older revision		Revision as of 16:38, 10 December 2025
Line 149:		Line 149:
	The system will then:		The system will then:

	- Create a record of the new comment		- Create a record of the new comment.

	- Update the list of comments		- Update the list of comments.

	- Issue a notification to the TB/ISG mailing list		- Issue a notification to the TB/ISG mailing list for the users monitoring the contribution.

	- Add the submitter to all future notifications on this Contribution.		- Add the submitter to all future notifications on this Contribution.
Line 170:		Line 170:
	The system will then:		The system will then:

	- Create a record of the new opposition		- Create a record of the new opposition.

	- Update the list of oppositions		- Update the list of oppositions.

	- Issue a notification to the TB/ISG mailing list		- Issue a notification to the TB/ISG mailing list for the users monitoring the contribution.

	- Adds the user to all future notifications on this Contribution		- Adds the user to all future notifications on this Contribution.

	'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the [https://help.etsi.org/index.php?title=Remote_Consensus#Remote_Consensus_guidelines Remote Consensus guidelines].		'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the [https://help.etsi.org/index.php?title=Remote_Consensus#Remote_Consensus_guidelines Remote Consensus guidelines].
Line 193:		Line 193:
	- Update the list of comments or oppositions		- Update the list of comments or oppositions

	- Issue a notification to the TB/ISG mailing list.		- Issue a notification to the TB/ISG mailing list for the users monitoring the contribution.

	'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the [https://help.etsi.org/index.php?title=Remote_Consensus#Remote_Consensus_guidelines Remote Consensus guidelines].		'''NOTE''': You’ll only receive instant email alerts if you monitor the contribution. If not, you’ll get the updates in the next optional weekly report. For more information, refer to the [https://help.etsi.org/index.php?title=Remote_Consensus#Remote_Consensus_guidelines Remote Consensus guidelines].

← Older revision		Revision as of 15:21, 29 April 2019
Line 131:		Line 131:
	An automated notification is sent to the TB/ISG mailing list including:		An automated notification is sent to the TB/ISG mailing list including:

	The Contribution name and number		- The Contribution name and number

	The duration and the type of Remote Consensus		- The duration and the type of Remote Consensus

	Guidelines on how to add a comment, raise an opposition and remove an opposition.		- Guidelines on how to add a comment, raise an opposition and remove an opposition.

	'''NOTE:''' An ACTIVE Remote Consensus cannot be modified or stopped.		'''NOTE:''' An ACTIVE Remote Consensus cannot be modified or stopped.
Line 194:		Line 194:
	The system sends a weekly report to the TB/ISG mailing list with a status update including:		The system sends a weekly report to the TB/ISG mailing list with a status update including:

	The number of Contributions in the Remote Consensus		- The number of Contributions in the Remote Consensus

	Duration of the review period		- Duration of the review period

	The number of comments, oppositions or cleared oppositions		- The number of comments, oppositions or cleared oppositions

	Purpose and life-cycle of a Remote Consensus		- Purpose and life-cycle of a Remote Consensus

	A hyperlink to the Remote Consensus report		- A hyperlink to the Remote Consensus report

			Example of a report:

	<blockquote>''Weekly report for '''NFV(18)DEC094''' is sent every '''Thursday''' at 4:00am CET.'' </blockquote><blockquote>''RC status: '''STARTED''' , with 2 available contributions.'' </blockquote><blockquote> ''0 comments.''</blockquote><blockquote>''RAISING COMMENTS AND OPPOSITIONS is ALLOWED until Wednesday 2018-10-24 at midnight.''</blockquote><blockquote> '''''NFV(18)000269''' (download) '''Draft - DGS/NFV-EVE011 v0.0.20 (GS NFV-EVE 011 ) "Cloud Native VNF Classification Spec"'''''</blockquote><blockquote> ''Decision Requested : Please approve''</blockquote><blockquote> ''0 sustained oppositions (0 cleared oppositions) and 0 comments from 0 users'' </blockquote><blockquote> '''''NFV(18)000271''' (download) '''Draft - DGR/NFV-IFA012 v0.13.1 (GR NFV-IFA 012 ) "Os-Ma-Nfvo ref point Spec - svc mgmt & info model"''''' </blockquote><blockquote> ''Decision Requested : Please approve''</blockquote><blockquote> ''0 sustained oppositions (0 cleared oppositions) and 0 comments from 0 users'' </blockquote><blockquote> </blockquote><blockquote>'''''Remote Consensus guidelines:'''''</blockquote><blockquote> ''A Remote Consensus (RC) allows approving or just gathering comments either on one single contribution or on a set of contributions grouped together. A single approval period is set for the whole group, and a single report monitors all the results.''</blockquote><blockquote> </blockquote><blockquote> ''During the RC period ETSI members subscribed to the related TB mailing list can add comments and/or raise oppositions on any of the contributions in the RC. Users can also monitor a contribution to receive an email each time a comment is added, or they can wait for the (optional) weekly report email to receive the status and comments on all contributions.''</blockquote><blockquote> ''Comments (and oppositions) collected during the RC period can be viewed at any time via the '''RC Report'''''</blockquote><blockquote> </blockquote><blockquote> ''At the end of the RC approval period, an official reviews all comments, RATIFIES the result by recording an output status for each contribution.''</blockquote><blockquote> ''There are two types of Remote Consensuses:''</blockquote><blockquote> ''1- "Consensus measuring" RCs: a DECISION is expected at the end of the approval period, these can only contain contributions for decision'' </blockquote><blockquote> ''2- "Comment collecting" RCs do not imply a decision at the end of the period, these can only contain contributions for DISCUSSION.''</blockquote><blockquote> </blockquote><blockquote> ''For consensus measuring RCs the application lists the number of sustained oppositions (as defined in ETSI Working Procedures). For comment collecting, comments are allowed but raising oppositions is not possible.''</blockquote><blockquote> </blockquote><blockquote> ''Participants can add comments, raise an oppositions, but also remove their oppositions at any time during the approval period.''</blockquote><blockquote> </blockquote><blockquote> ''When all contributions have been ratified, the Remote Consensus is considered as ratified.'' </blockquote><blockquote> </blockquote><blockquote> ''Remote Consensus lifecycle: PLANNED - (FROZEN) - STARTED - TO BE RATIFIED - RATIFIED''</blockquote><blockquote> ''Only officials and support staff can create a Remote Consensus for their TB.''</blockquote><blockquote> '' -PLANNED: all delegates can add/remove contributions to/from the RC.''</blockquote><blockquote> ''-FROZEN: only officials and support staff can add/remove contributions to the RC.''</blockquote><blockquote> '' -STARTED: delegates can add comments, and raise or remove oppositions on contributions.''</blockquote><blockquote> '' -TO BE RATIFIED: RC period if finished, officials and support staff are expected to ratify results.''</blockquote><blockquote> '' -RATIFIED: all contributions of the RC have been ratified.'' </blockquote><blockquote> ''More help [[Remote Consensus\|here]]'' </blockquote>		<blockquote>''Weekly report for '''NFV(18)DEC094''' is sent every '''Thursday''' at 4:00am CET.'' </blockquote><blockquote>''RC status: '''STARTED''' , with 2 available contributions.'' </blockquote><blockquote> ''0 comments.''</blockquote><blockquote>''RAISING COMMENTS AND OPPOSITIONS is ALLOWED until Wednesday 2018-10-24 at midnight.''</blockquote><blockquote> '''''NFV(18)000269''' (download) '''Draft - DGS/NFV-EVE011 v0.0.20 (GS NFV-EVE 011 ) "Cloud Native VNF Classification Spec"'''''</blockquote><blockquote> ''Decision Requested : Please approve''</blockquote><blockquote> ''0 sustained oppositions (0 cleared oppositions) and 0 comments from 0 users'' </blockquote><blockquote> '''''NFV(18)000271''' (download) '''Draft - DGR/NFV-IFA012 v0.13.1 (GR NFV-IFA 012 ) "Os-Ma-Nfvo ref point Spec - svc mgmt & info model"''''' </blockquote><blockquote> ''Decision Requested : Please approve''</blockquote><blockquote> ''0 sustained oppositions (0 cleared oppositions) and 0 comments from 0 users'' </blockquote><blockquote> </blockquote><blockquote>'''''Remote Consensus guidelines:'''''</blockquote><blockquote> ''A Remote Consensus (RC) allows approving or just gathering comments either on one single contribution or on a set of contributions grouped together. A single approval period is set for the whole group, and a single report monitors all the results.''</blockquote><blockquote> </blockquote><blockquote> ''During the RC period ETSI members subscribed to the related TB mailing list can add comments and/or raise oppositions on any of the contributions in the RC. Users can also monitor a contribution to receive an email each time a comment is added, or they can wait for the (optional) weekly report email to receive the status and comments on all contributions.''</blockquote><blockquote> ''Comments (and oppositions) collected during the RC period can be viewed at any time via the '''RC Report'''''</blockquote><blockquote> </blockquote><blockquote> ''At the end of the RC approval period, an official reviews all comments, RATIFIES the result by recording an output status for each contribution.''</blockquote><blockquote> ''There are two types of Remote Consensuses:''</blockquote><blockquote> ''1- "Consensus measuring" RCs: a DECISION is expected at the end of the approval period, these can only contain contributions for decision'' </blockquote><blockquote> ''2- "Comment collecting" RCs do not imply a decision at the end of the period, these can only contain contributions for DISCUSSION.''</blockquote><blockquote> </blockquote><blockquote> ''For consensus measuring RCs the application lists the number of sustained oppositions (as defined in ETSI Working Procedures). For comment collecting, comments are allowed but raising oppositions is not possible.''</blockquote><blockquote> </blockquote><blockquote> ''Participants can add comments, raise an oppositions, but also remove their oppositions at any time during the approval period.''</blockquote><blockquote> </blockquote><blockquote> ''When all contributions have been ratified, the Remote Consensus is considered as ratified.'' </blockquote><blockquote> </blockquote><blockquote> ''Remote Consensus lifecycle: PLANNED - (FROZEN) - STARTED - TO BE RATIFIED - RATIFIED''</blockquote><blockquote> ''Only officials and support staff can create a Remote Consensus for their TB.''</blockquote><blockquote> '' -PLANNED: all delegates can add/remove contributions to/from the RC.''</blockquote><blockquote> ''-FROZEN: only officials and support staff can add/remove contributions to the RC.''</blockquote><blockquote> '' -STARTED: delegates can add comments, and raise or remove oppositions on contributions.''</blockquote><blockquote> '' -TO BE RATIFIED: RC period if finished, officials and support staff are expected to ratify results.''</blockquote><blockquote> '' -RATIFIED: all contributions of the RC have been ratified.'' </blockquote><blockquote> ''More help [[Remote Consensus\|here]]'' </blockquote>
Line 208:		Line 210:
	== The end of a Remote Consensus ==		== The end of a Remote Consensus ==

	At midnight CET on the final day of the Remote Consensus:		At midnight CET/CEST on the final day of the Remote Consensus:

	The system sends a final notification to the TB/ISG mailing list		The system sends a final notification to the TB/ISG mailing list
Line 240:		Line 242:
	* Enter a ratification comment and select the final status		* Enter a ratification comment and select the final status
	* Click on '''Ratify result'''		* Click on '''Ratify result'''

	~~'''NOTE:''' Status - '''NOTED with revision pre-approved -''' the next revision of the Contribution will automatically be '''ACCEPTED'''.~~

	A pop message will confirm this action.		A pop message will confirm this action.

	[[File:Picture Rem28.png\|frameless]]		[[File:Picture Rem28.png\|frameless]]

			'''NOTES:''' Status - '''NOTED with revision pre-approved -''' the next revision of the Contribution will automatically be '''ACCEPTED'''.

			A ratification comment is mandatory for the output status of a '''REJECTED''' Contribution.

	Once all Contributions have been updated, the portal will show the status '''RATIFIED''' and a final notification will be sent to the TB/ISG mailing list.		Once all Contributions have been updated, the portal will show the status '''RATIFIED''' and a final notification will be sent to the TB/ISG mailing list.