MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Remote_Consensus_FaQs",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "360": {
                "pageid": 360,
                "ns": 0,
                "title": "Remote Consensus",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "\n== Getting started - How to access the Remote Consensus tool ==\n\n'''NOTE:''' '''Only community officials: Chairman, Vice Chairman, Secretary and ETSI Support staff can set up, manage and ratify a Remote Consensus.'''\n\n'''\u00a0 \u00a0 Users must be logged on the [https://portal.etsi.org/ portal] to use the application'''\n\n* Open the ETSI portal [https://portal.etsi.org '''https://portal.etsi.org'''] and '''log in with your EOL account'''\n[[File:Picture log1.png|frameless]]\n* Once logged on, select the relevant Technical Committee or ISG, e.g. ERM\n* Select the tab '''Remote Consensus''' \n[[File:Remote con1.png|frameless|542x542px]]  \u00a0\n\nBy default, '''Recent, Ongoing or Future''' Remote Consensus\u2019 are displayed.\n\n* To set up a new Remote Consensus, click on the link '''Create New'''\n* To search for a closed/previous Remote Consensus, use the dropdown menu and select one of the 3 options.\n\n== Scope of the Remote Consensus application ==\n*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.\n\n=== Types of Remote Consensus: ===\n'''Consensus Measuring''' for Decisions\n\n'''Comments Collecting''' for Discussion  \n\nThe application allows:\n\n- The collection of '''comments'''\n\n- The measurement of consensus by counting the number of '''oppositions'''\n\n- 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.  \n\nNotifications related to each Remote Consensus are automatically disseminated to the TB/ISG mailing list.\n\n'''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''']\n=== Recommendations for the duration of a Remote Consensus ===\nThe ETSI Directives mandate the following:\n\na 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;\n\nThe time period for participating in the Remote Consensus shall be at least seven (7) calendar days;\n* \n\n== Creating a new Remote Consensus ==\n* Click on the link '''Create New'''\n[[File:Picture Rem3.png|frameless|631x631px]]\n\nA pop-up window will display the fields for completion.\n\n'''NOTE:''' Mandatory fields are marked with a red asterisk '''*'''.\n\n[[File:Picture Rem4.png|frameless|379x379px]]\n\n'''Community''' is pre-filled by the system. If applicable, use the drop down menu to select a Working Group.'''Type''' Select either '''Consensus measuring (DECision at the end)''' or '''Comments collecting (DIScussion).'''\n\n'''Title''' Write the title (e.g. ''Approval of NFV003 Final Draft'' or ''Approval of Liaison Statement to XXX'').\n\n'''Description''' is optional and can be used to provide more detail on the remote consensus. \n\n'''Status''' is by default set to '''PLANNED''' until the launch time. \n\n'''Start date''' Select the start date for the Remote Consensus. Start time is always at 12:00 midday CET. \n\n'''End Date''' Select the end date for the Remote Consensus when comments or oppositions will no longer be allowed. End Time is always at midnight CET.\n\n'''NOTE:''' Start Date shall be greater than or equal to the current date. End Date shall be greater than the Start date.\n\n'''Freeze contribution submission''' if appropriate, use this field to prevent Contributions from being added after a specified date.\n\n'''Status Report Date''' is optional. Select the day for a weekly status report to be sent to the TB/ISG membership list.\n* When all mandatory fields are complete, click on '''SAVE'''.\n\nA pop-up window will summarise the Remote Consensus properties and display the Remote Consensus reference. \n\n[[File:Picture Rem5.png|frameless]] \n\nAt the launch of every Remote Consensus a notification is sent to the TB/ISG mailing list.\n\n== Adding a Contribution to a Status ''PLANNED'' Remote Consensus ==\n\nFor '''consensus measuring,''' only Contributions for '''Decision''' '''(DEC)''' can be submitted. \n\nFor '''comments collecting,''' only Contributions for '''Discussion or Information''' '''(DIS)''' can be submitted.\n\n* Click on '''Add Contributions'''\n[[File:Picture Rem6.png|frameless|376x376px]]\n\n[[File:Picture Rem7.png]]\n* To add a Contribution either:\n* Type the sequence number, for example: '''000021''' and click on the '''Filter'''\n* '''''OR''''' type a word from the title, for example: '''Release 2''' and click on '''Filter'''\n* '''''OR''''' click on '''Filter''' and the system will display all the Contributions for the year for the selected community.\n* Select the Contribution(s) from the Contributions list and click on '''Add'''.\n* Once all Contributions have been added click on '''Done'''.\n\nA popup window will confirm the Contributions in the Remote Consensus.\n\n'''NOTE''': A Contribution added to a Remote Consensus becomes '''locked''', meaning that no further actions are possible on this Contribution until the Remote Consensus has either ended or the Contribution has been removed. The lock is depicted by the hammer icon [[File:Hammer arrow icon.PNG|frameless]]\n\n=== Identifying a Contribution under Remote Consensus ===\n\nContributions in a Remote Consensus are flagged with a hammer icon. \n\n[[File:Hammer arrow icon.PNG|link=http://help.etsi.org/File:Hammer%20arrow%20icon.PNG|frameless]] Status '''ACTIVE''' ('''PLANNED''', '''FROZEN''' or '''STARTED''') \n\n[[File:Hammer only icon.PNG|frameless]] '''RATIFIED''' or '''REVIEWED'''\n\n[[File:Hammer cross icon.PNG|frameless]] Status '''ABORTED'''\n\n== Removing a Contribution from a Status ''PLANNED'' Remote Consensus ==\n*Find the Contribution for removal and click on the small glasses icon[[File:Glasses_icon.PNG|frameless]].\n* Select the third tab '''Remote Consensus''' and click on the link '''REMOVE'''.\n[[File:Picture Rem8.png]]\n* Enter the justification and click '''OK'''.\n[[File:Picture Rem9.png|frameless]]\n\nThe system will refresh the counter of Contributions in this Remote Consensus and update the History of the Contribution.\n\n'''NOTE''': Contributions can only be removed by the TB/ISG Officials, the submitter or ETSI Support staff '''before''' the launch of a Remote Consensus.\u00a0  \n\nOnce the Remote Consensus has started, Contributions can only be removed by the TB/ISG Officials or ETSI Support staff.\u00a0 \n\n== The start of a Remote Consensus ==\n\nA Remote Consensus evolves from Status '''PLANNED''' to Status '''ACTIVE''' at the launch.\n\nAn automated notification is sent to the TB/ISG mailing list including:\n\n- The Contribution name and number\n\n- The duration and the type of Remote Consensus\n\n- Guidelines on how to add a comment, raise an opposition and remove an opposition.\n\n'''NOTE:''' An ACTIVE Remote Consensus cannot be modified or stopped.\n== Submitting a comment to a Contribution in a Remote Consensus ==\nNote 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))''']).\n\nThe procedure to submit a Comment to a Comments Collection (DIS) and a Consensus Measuring (DEC) Remote Consensus is identical.\n\n[[File:Picture Rem3.png|frameless|568x568px]]\n\n* Click on the glasses icon [[File:Glasses icon.PNG|frameless]] to open the Contribution. A new window will open.\n* Click on '''Comment'''.  By default the comment field is active.Enter text in the '''Write a Comment''' field and click '''Save'''.  \n[[File:Picture Rem14.png|734x734px]]\n\nThe system will then:\n\n- Create a record of the new comment\n\n- Update the list of comments\n\n- Issue a notification to the TB/ISG mailing list\n\n- Add the submitter to all future notifications on this Contribution.\n\n== Raising an opposition to a Contribution ==\nNote 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))''']).\n* Open the Remote Consensus tab\n* Click on the Remote Consensus reference (i.e. ERM(18)DEC606) in Status STARTED. A new window will open.\n\n* Click on '''Raise an opposition'''. By default the comment field is active. \n* Enter text in the '''Write a Comment''' field to justify the opposition and click '''Save'''.  \n[[File:Picture Rem19.png|723x723px]]\n\nThe system will then:\n\nCreate a record of the new opposition\n\nUpdate the list of oppositions\n\nIssue a notification to the TB/ISG mailing list\n\nAdds the user to all future notifications on this Contribution\n\n== Clearing an opposition to a Contribution  ==\nAn opposition is displayed in the Remote Consensus tab of the Contribution.\n\nOnly the submitter or ETSI Support staff can remove an opposition.\n* Click on the hyperlink '''Clear my opposition''' and add text if appropriate and then '''Save'''.\n[[File:Picture Rem20.png]]\n\nThe system will then:\n\nCreate a record of the cleared opposition\n\nUpdate the list of comments or oppositions\n\nIssue a notification to the TB/ISG mailing list.\n\n== Weekly report notification ==\n\nThe system sends a weekly report to the TB/ISG mailing list with a status update including:\n\n- The number of Contributions in the Remote Consensus\n\n- Duration of the review period\n\n- The number of comments, oppositions or cleared oppositions\n\n- Purpose and life-cycle of a Remote Consensus\n\n- A hyperlink to the Remote Consensus report \n\nExample of a report: \n\n<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> ''\u00a0 \u00a0 \u00a0 -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> ''\u00a0 \u00a0 \u00a0 -STARTED: delegates can add comments, and raise or remove oppositions on contributions.''</blockquote><blockquote> ''\u00a0 \u00a0 \u00a0 -TO BE RATIFIED: RC period if finished, officials and support staff are expected to ratify results.''</blockquote><blockquote> ''\u00a0 \u00a0 \u00a0 -RATIFIED: all contributions of the RC have been ratified.'' </blockquote><blockquote> ''More help [[Remote Consensus|here]]'' </blockquote>\n\n== The end of a Remote Consensus ==\n\nAt midnight CET/CEST on the final day of the Remote Consensus:\n\nThe system sends a final notification to the TB/ISG mailing list\n\nThe status of the Remote Consensus is updated '''TO BE RATIFIED.'''\n\n[[File:Picture Rem22.png|frameless|584x584px]]\n\n== Ratifying a Remote Consensus ==\n\nThe Chairman has the action to ratify the Remote Consensus, taking into account comments and oppositions.\n\n=== Final output statuses for a Remote Consensus ===\nThere are 5 different output statuses for a Contribution in a Remote Consensus\n\n* Click on the Remote Consensus reference in Status '''TO BE RATIFIED'''\n\n<span name=\"_msocom_1\"></span>[[File:RC toberatified.png|frameless|905x905px]] \n\n* Click on \u00a0and the Contribution will open on the General tab\n* Click on the Remote Consensus tab and a new page will open\n* Click on '''Ratify'''\n[[File:Picture Rem26.png|frameless|355x355px]]\n\nIf no comments or oppositions have been submitted during the review period the status will by default show as '''ACCEPTED'''.\n\n[[File:Picture Rem23.png|frameless|230x230px]]\n\n* Enter a ratification comment and select the final status\n* Click on '''Ratify result'''\n\nA pop message will confirm this action.\n\n[[File:Picture Rem28.png|frameless]]\n\n'''NOTE1:''' When a contribution is - '''NOTED with revision pre-approved -''' the next revision of that Contribution will automatically be '''ACCEPTED''' as soon as available.\n\n'''NOTE2:'''A ratification comment is mandatory for the output status of a '''REJECTED''' Contribution.\n\n'''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'''\".\n\nOnce 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.\n\n== The Report/Journal of a Remote Consensus ==\n\nAn automated Report/Journal is always available for every Remote Consensus via the Remote Consensus tab and the icon.\n\n2 views are available: '''Journal''' or '''Status Report'''\n\n[[File:Picture Rem30.png|frameless|619x619px]]\n\n[[File:Picture Rem32.jpg|frameless|630x630px]]\n\nBoth can be exported to CSV files<span name=\"_msocom_1\"></span><span name=\"_msocom_1\"></span><span name=\"_msocom_1\"></span>"
                    }
                ]
            },
            "86": {
                "pageid": 86,
                "ns": 0,
                "title": "Remote Consensus(OLD)",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "==Scope of the Remote Consensus Application==\n\nThis application aims at providing a comprehensive online tool to collect comments and measure consensus for contributions during given period as opposed to during a face-to face meeting.\nThis application focuses on:\n\n- The collection of members views recorded as ''comments'', and the ability to present these comments in clear reports.\n\n- The measurement of consensus by counting the number of \u2018\u2019oppositions\u2019\u2019 raised during the approval period and maintained by its author at the end of that period\n\n- The final interpretation of the consensus is the responsibility of chairman. After the end of the consensus measurement period, the chairman of the TB/WG/TG will take the final decision on contribution(s) and ratify the remote consensus.\n\nThe announcement of remote consensuses measuring period, and the results are disseminated on the TB mailing list by the system.\n\nNOTE: It is recommended to group contributions in one Remote consensus on which decision needs to be taken.  \nOne of this application aim is to help TBs to structure and organize their work between meetings: TBs would group their  documents for remote decisions in one or two RCs per month for instance.\nNormally, a Remote Consensus is planned well before it starts, and delegates can add their documents to the RC by themselves. Then the Remote Consensus starts, and no more than ONE notification per week is sent to the mailing list.\n\n==Create a new Remote Consensus==\n\n'''Actors''': TB/WG/TG Chairman, Vice-Chairman and Secretary; TB support staff\n\nNote: Only Officials can create a Remote Consensus for the TB he chairs and also for its WGs. \n\nIn order to be able to create a remote consensus you first need to be logged in to the portal. Click on the \u2018\u2019create new\u2019\u2019 link in the portlet.\nThe following creation screen is displayed:\n\n[[File:Create_a_RC.png|450px|center]]\n\nThe system displays an empty form which you are asked to fill in. Some of the attributes are mandatory:\n\n- '''Community''': this field automatically shows your TB/WG, however it is possible to change to another \n\n- '''Type''': There are 2 types of Remote Consensus:\n\n1) '''''Consensus measuring \"\u2013 DEC\"''''': This type of Remote Consensus allows the measurement of consensus by counting the number of \u2018\u2019oppositions\u2019\u2019 raised during the approval period and maintained by its author at the end of that period\n\n2)'' '''Comment collecting \"\u2013 DIS\"''''': This type of Remote Consensus allows the collection of members views recorded as \u2018\u2019comments\u2019\u2019, and the ability to present these comments in clear reports.\n\n- '''Description''': You can type text to give information on the Remote Consensus you intend to create. This field is optional.\n\n- '''Status''': In creation mode the status \u2018\u2019PLANNED\u2019\u2019 is automatically set and cannot be changed\n\n- '''Start date''': Select the date when the Remote Consensus will start and therefore comments will be allowed. '''Start time will always be 12:00 CET.'''\nNote: Start Date must be greater than Now, greater than Freeze date and smaller than End date.\n\n- '''End Date''':  Select the date when the Remote Consensus will end and when comments will not be longer be allowed. '''End Time will always be midnight CET.''' \nNote: End Date must be greater than Start date. \n\n- '''Freeze Date''': Should you wish to, you can set a freeze date for contribution submission. This means that TC members will not be able to add a contribution to a Planned Remote Consensus from the freeze date.  If selected, this date must be greater than Now and smaller than the Start date.  \n\n-'''Status Report Date''': This indicates if a weekly status report shall be sent for this Remote Consensus. If this option is ticked then the system asks you to indicate which day this Report shall be sent to the list. \n\n\nWhen all mandatory fields are filled, click on the button \u2018\u2019Save\u2019\u2019. The system displays a creation confirmation pop-up summarising the Remote Consensus properties and the Remote Consensus portlet is refreshed with the newly created item.\n\n==Update the details of a Remote Consensus==\n\n'''Actors''': TB/WG/TG Chairman, Vice-Chairman and Secretary; TB support staff\n\nTo update properties of remote consensus, go to the Remote Consensus portlet and click on the [[File:Portlet_view_details.png|15px]] on the line of the Remote Consensus you intend to update.\n\nThe system displays the detailed view for the chosen Remote Consensus\n\n\n[[File:RC_view_details.jpg|450px]] \n\n\nThen, click on the \"Edit\" button and update the Remote Consensus information. Ensure that you don\u2019t leave a mandatory field blank. \n\nNote: You can decide to change the status from PLANNED to FROZEN manually on this page. \n\nThe FROZEN status can be used should you wish to stop the addition of contribution in a Remote Consensus; the reason for freezing a Remote Consensus may be that you are in line with what you were expected for this Remote Consensus or that you need to check the added contributions. \n\nThe FROZEN status can be removed manually by changing the status from FROZEN to PLANNED in the status drop down menu otherwise it will be changed automatically by the system at the Start date of the Remote Consensus. \n\nWhen you have finished updating the Remote Consensus properties, click on the \u2018\u2019SAVE\u2019\u2019 button. The system updates the information and refreshes the Remote Consensus portlet.\n\n==Add contributions to a Remote Consensus==\n\n'''Actors''': TB Membership list member, TB/WG/TG Chairman, Vice-Chairman and Secretary, TB support staff\n\nAccess rights note: You need to subscribe to the TB membership list to be able to use the Remote Consensus application. Should you wish to subscribe please go to:[http://webapp.etsi.org/TBMembershipList]\n\n===Add contribution(s) to a Remote Consensus from the Remote Consensus creation screen===\n\nAfter saving your newly created Remote Consensus, click on \"Add contributions\" link: \n\n[[File:Add_contrib_from_RC_creation.png|500px]]\n\nThe system displays a pop-up window with a search box for contributions:\n\n[[File:Pop-up_add_contrib_to_RC.png|550px]]\n\n\nYou may search with the contribution Unique Identifying number (UID). \nNote: This field does not contain a wildcard function. You will need to include the zeros contained in the UID. For example: ERM(13)'''000'''025.\n\nYou may also search by keywords in the contribution title. \nIf you do not know the UID nor the title, just click on \"Filter\".\n\nContributions are taken from the same community as the Remote Consensus and not from its subgroups. \n\n\nTo add contributions to a Remote Consensus, select one or several contributions in the filtered list and click on the \u201cAdd\u201d button, or double-click on a single contribution and click on \u201cDone\u201d once you have added all your contributions. \n\nYou can also add contributions from the Remote Consensus detailed view, by clicking on the [[File:Portlet_view_details.png|15px]] and select the \u201cAdd contribution\u201d. The system will redirect to the contributions window above.\n\n\n===Add contribution(s) to a Remote Consensus from the Remote Consensus portlet===\n\nThe remote consensuses are listed in the Remote Consensus portlet. A remote consensus that can still accept contribution addition (i.e. a \"planned\" RC) will show a small [[File:Add_contrib_from_portlet.png|20px]] icon.\n\nTo add contribution(s) to such a Remote Consensus, click on the [[File:Add_contrib_from_portlet.png|20px]] icon. \n\nThe system displays a pop-up window with a search box for contributions:\n\n[[File:Pop-up_add_contrib_to_RC.png|550px]]\n\nFrom this step onwards, you can refer to the above paragrah \"Adding a contribution from the Remote Consensus creation screen\".\n\n===Add contribution(s) to a Remote Consensus from the contribution application===\n\nContext: You are logged in and a list of contribution(s)is diplayed\n\nTo add a contribution to a Remote Consensus, select it in the contributions list and then click on the \"Actions button\" in the top bar. The \u201cActions\u201d button unfolds and displays the menu of actions that you can perform on this contribution, including those related to Remote Consensus. \n\nClick on \"Remote Consensus\", then \"Send to Remote Consensus\".\n\nThe system then displays a listing of the Remote Consensuses in \u201cPLANNED\u201d or \u201cFROZEN\u201d status of the contribution's community. Select the Remote Consensus to which you wish to add the selected contribution.\n\n[[File:Add_contrib_in_RC_from_Contrib.png|550px]]\n\n\nThe system then displays the message: Your contribution has been added to the chosen Remote Consensus. \n\n\n'''Important Note:''' \n\n'''- Contributions uploaded for Information/Discussion may only be added to Remote Consensus Type DIS: \u201cComments Collecting\u201d.'''\n\n'''- Contributions uploaded for Decision may only be added to Remote Consensus Type DEC: \u201cConsensus Measuring\u201d.'''\n\n\nNote: Contributions added to a remote consensus are locked in the contribution application and this lock is visually materialized by the following icon: [[File:Hammer.png|20px]].\nIt is not possible to perform actions on this contribution during the Remote Consensus, such as changing the status or uploading a revision.\n\n==Status of contribution in a Remote Consensus==\n\nYou can add one or more contributions that are in Status \u201cReserved\u201d or \u201cAvailable\u201d to a Remote Consensus. From the Remote Consensus portlet, the system only displays only contributions which can be added to the Remote Consensus you have selected. \n\n* Remote Consensus of Type '''consensus measuring''': you can add to this type of Remote Consensus only '''contributions which are for Decision.'''\n\n* Remote Consensus of Type '''comment collecting''': you can add to this type of Remote Consensus only '''contributions which are for Discussion.'''\n\nThe contribution in a Remote Consensus which has not yet started has the status \u201cADDED\u201d in a Remote Consensus. \n\n\nOnce the Remote Consensus has started:\n* The contributions in '''status \u201cAVAILABLE\u201d''' in the contribution process '''will be set to \u201cACTIVE\u201d''' in the Remote Consensus. Note: This \u201cACTIVE\u201d Contribution is still available on the server but locked in the contribution process as it is in Remote Consensus. \n\n\n* The contributions in '''status \u201cRESERVED\u201d''' in the contribution process '''will be set to \u201cNO SHOW\u201d''' in the Remote Consensus. Note: This \u201cNO SHOW\u201d Contribution is still in a \u201cRESERVED\u201d status in the contribution application and can eventually be added to another Remote Consensus in \u201cRESERVED\u201d or \u201cAVAILABLE\u201d status.\n\n\n* If the Remote Consensus contains '''only contributions with status \"RESERVED\"''', then the Remote Consensus '''will be set to \"CANCELLED\"''' and the contributions will be released for a future Remote Consensus.\n\n:: NOTE: The history tab of the contributions keeps track of the differents steps and events.\n\n==Remove contributions from a Remote Consensus==\n\n'''Actors''': TB/WG/TG Chairman, Vice-Chairman and Secretary; TB support staff. The TB Membership list Members can remove a contribution only when the Remote Consensus is in a PLANNED Status. \n\nA contribution can be removed from a PLANNED Remote Consensus by any user who has added it. Nevertheless, if a Remote Consensus has STARTED then only the TB/WG/TG Chairman and Vice-Chairman can remove it from the Remote Consensus.\n\nYou can remove the contribution by clicking on the \u201cview details\u201d of the contribution, the system will open the usual contribution detailed view, select the tab \u201cRemote Consensus\u201d and click on the link \u201cremove\u201d.\n\n[[File:Contrib_details_remove.png|550px|center]]\n\n\nNOTE: The contribution removed from an active Remote Consensus will be noted as \"ABORTED\".\n\n==Post a comment on a contribution in a Remote Consensus==\n\n'''Actors''': TB Membership list member, TB/WG/TG Chairman, Vice-Chairman and Secretary, TB support staff\n\n'''Context''': You are in the contribution application. You see the list of contributions that are on Remote Consensus.\n\n\nTo add a comment on a contribution in a Remote Consensus, proceed as follows:\n*Open the contribution detailed view,\n*Select the \u2018\u2019Remote Consensus\u2019\u2019 tab from the contribution detailed view,\n*Type your comment in the comment text box at the bottom of the screen\n*Save your comment by clicking on the \u2018\u2019Save\u2019\u2019 button that will appear.\n\n\n[[File:Comment_window.png|550px]]\n\nThe action of commenting to a contribution in a Remote Consensus will automatically subscribe you to notifications, this means that you will receive email notifications each time a comment (or an opposition) is raised on the contribution (you have the ability to unsubscribe to notifications by either clicking on the link \u2018\u2019Stop Monitoring\u2019\u2019).\n\n[[Note]]: Attaching a file to a comment is not possible, yet it is possible to refer to an uploaded contribution from within a comment.\n\n[[Note]]: In a Remote Consensus for DECision, raising a comment without opposing to the RC means that the author of the comment does not oppose to the document being approved as-it-is (i.e. without taking the comment into account). \n\n* If a comment in an RC requests '''editorial changes''' on a draft, these may be taken into account before publication.\n* If a comment in an RC requests '''technical changes''' on a draft, these cannot implemented in the draft before publication without re-approving the updated draft.\n** if no opposition is raised during the RC, the technical changes may be dropped and the draft published unchanged.\n** if an opposition is raised during the RC, the current version is not approved, a new version of the draft may be generated and a approved in a future RC\n\n==Oppose to a contribution in a Remote Consensus (only for RC type \"-DEC\")==\n\n'''Actors''': TB Membership list member, TB/WG/TG Chairman, Vice-Chairman and Secretary, TB support staff\n\n\nYou can indicate your wish to oppose to a contribution in a remote consensus by selecting the action \u2018\u2019Raise an Opposition\u2019\u2019 from the \u2018\u2019Remote Consensus\u2019\u2019 tab of the contribution detailed view.\n\n[[File:Raise_opposition.png|550px]]\n\n\nWhen you raise an opposition, you are asked to enter justification comment. A red bullet appears next to your comment and the general information panel at the top of the pop-up indicates then that CONSENSUS= NO and the counter of the number of opposition is refreshed.\n\nOnly one opposition per delegate can be posted. As soon as you raise your opposition the action becomes \u2018\u2019Clear my opposition\u2019\u2019 which you can use at any time to remove your opposition on a contribution.\n\n==Ratify contribution in a Remote Consensus==\n'''Actors''': TB/WG/TG Chairman, Vice-Chairman and Secretary\n\nWhen the Remote Consensus End Date is reached, then the Remote consensus passes in status \u2018\u2019TO BE RATIFIED\u2019\u2019. It is no longer possible to comment or to raise oppositions. The TB/WG/TG chairman, Vice Chairman or Secretary decides on the final result of the Remote Consensus for a particular contribution. This result will update the status of the contribution accordingly.\n\nYou can indicate your wish to ratify a contribution in a remote consensus by selecting the action \u2018\u2019Ratify\u2019\u2019 from the \u2018\u2019Remote Consensus\u2019\u2019 tab of the contribution detailed view.\n\nThen the following screen is displayed:\n\n[[File:Ratification.png|550px]]\n\nOn this screen you are asked to indicate the result status of the contribution. \n\n'''If the Remote Consensus type is Consensus Measuring (\"-DEC\")''', then the system displays the following possible status:\n\n::- ACCEPTED\n\n::- REJECTED\n\n::- NOTED\n\n::- NOTED with revision requested\n\n::- NOTED with revision pre-approved\n::: '' Important: with this status, the next uploaded revision will be '''automatically \"ACCEPTED\"''' as the revision was pre-approved.\n\n\n'''If the Remote Consensus type is Comment Collecting (\"-DIS\")''', then the system displays the following possible status:\n\n::- AVAILABLE (which would allow you to add the contribution to another Remote Consensus)\n\n::- NOTED\n\n::- NOTED with revision requested\n\n::- NOTED with revision pre-approved\n\nAfter having indicated the result status of the contribution you may add a ratification comment in the text box at the bottom of the window. This ratification comment is not mandatory unless the output status of the contribution is \u2018\u2019REJECTED\u2019\u2019.\n\nNote: A TB official can decide to ACCEPT a contribution even if consensus was not reached\n\nA ratified contribution is then unlocked in the contribution application. \n\nAfter the last contribution in a Remote Consensus has been ratified then the remote consensus is set to \u2018\u2019RATIFIED\u2019\u2019.\n\n== How to identify a contribution under Remote Consensus ==\n\n\nThe contributions added to a Remote Consensus are flagged with a little hammer icon.\n\t\nThis icon is visible in the Contribution applications:\n\t \t\n:[[File: Hammer_active.png|30px]] when the contribution is ADDED or ACTIVE in a Remote consensus which is in PLANNED, FROZEN, STARTED status.\n \n:[[File:Hammer_ratified.png|30px]] when the contribution has been RATIFIED or REVIEWED in the latest remote consensus it\u2019s been in.\n\n:[[File:Hammer_aborted.png|30px]] when the contribution is in status ABORTED in the latest remote consensus it\u2019s been in.\n\t \n\t\n===In the Contributions application ===\n\t \n\t\n[[File: Hammer_icon_in_Contrib_example1.png|700px]]\n\t \n\t\n[[File:Hammer_icon_in_Contrib_example2.png|700px]]\n\t \n\n=== In the contribution details page ===\n\t \n\t\nThe hammer is visible next to the UID number on the details page:\n\t \n\t\n[[File:Contrib_details_page_with_hammer.png|500px]]"
                    }
                ]
            }
        }
    }
}