remove standard names editor maintenance messages

discussion.md

@@ -43,6 +43,6 @@ Before the CF community migrated to GitHub, general and standard-name discussion
 [mail]: http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
 [archives]: https://cfconventions.org/mailing-list-archive/Data/
 [NCAR_archives]: https://mailman.cgd.ucar.edu/pipermail/cf-metadata/
-[current]: http://cfeditor.ceda.ac.uk/proposals/1?status=active&namefilter=&proposerfilter=&descfilter=&filter+and+display=filter
-[vocab_editor]: https://cfconventions.org/editor_placeholder.html
+[current]: https://cfeditor.ceda.ac.uk/proposals/1
+[vocab_editor]: https://cfeditor.ceda.ac.uk/proposals/1
 [github_issues]: https://guides.github.com/features/issues

standard_name_rules.md

@@ -1,60 +1,60 @@
----
-layout: default
-title: Vocabulary rules
----
-
-# Rules for Changes to CF Standard Names, Area Types and Standardized Region List Vocabularies
-
-**These rules apply only to changes in CF controlled vocabularies.
-The rules for changes to the CF conventions themselves are given [here](http://cfconventions.org/rules.html).**
-
-New proposals are made by opening a new issue in the cf-convention/discuss github repository.
-The 'Standard Names' template should be used, even if the proposal relates to one of the other vocabularies.
-
-Proposals may be for:
-- new term(s) to be added;
-- change to existing term(s) i.e. creation of alias(es)
-- clarification/correction of description or units of existing term(s).
-
-The discussion will be moderated by the CF standard names secretary, or another person familiar with the information management procedures for maintaining the published vocabularies.
-
-The discussion takes place on github issues and all may participate.
-
-A status page summarizing the progress of standard name proposals through the discussion process may also be viewed in the
-[CEDA vocabulary editor](http://cfconventions.org/editor_placeholder.html).
-
-If a proposal is received for a new vocabulary term that follows the same syntactic patterns as existing terms, and whose description can also be based on existing term descriptions, the proposal can be accepted after brief discussion, subject to checking by the moderator.
-
-For proposals that require more discussion, the moderator periodically summarises the current status on github, keeps it moving forward and tries to achieve a consensus.
-It is expected that everyone with an interest will contribute to the discussion and to achieving a consensus during this stage.
-During the discussion, if an objection is raised, answered and not reasserted, the moderator will assume the objection has been dropped.
-However, since consensus is the best outcome, it will be helpful if anyone who expresses an objection explicitly withdraws it on changing their mind or deciding to accept the majority view.
-
-If a consensus, or near consensus, view can not be achieved by discussion the moderator can ask the standard names committee to vote on a proposal.
-The committee's decision is final.
-
-If three weeks have passed with no contributions being made the moderator should attempt to reinvigorate the discussion so that a conclusion can be reached.
-
-The moderator will summarize the outcome of the discussion of each vocabulary term proposal.
-
-A proposal will be accepted if one of the following is true:
-- it is similar to existing terms and has been checked for conistency by the moderator;
-- consensus has been reached in favour of the proposal;
-- the moderator's summary indicates that consensus in favour of the proposal has nearly been achieved;
-- a majority of the standard names committee vote to accept the proposal.
-
-A proposal will be rejected if one of the following is true:
-- it duplicates an existing vocabulary term;
-- consensus has been reached against the proposal;
-- the moderator's summary indicates that consensus against the proposal has nearly been achieved;
-- a majority of the standard names committee vote to reject the proposal;
-- the proposer withdraws the proposal.
-
-The published vocabularies are updated approximately every 1 - 2 months.
-The publication date will be announced ahead of time via a github issue.
-Any names that have been formally accepted will be included in the next update, thus the period between acceptance and publication may vary from a few weeks to as little as a day.
-
-The author of an accepted proposal should be added to the
-[list of standard name contributors](http://cfconventions.org/Data/cf-standard-names/docs/standard-name-contributors.html).
-
-All versions of the CF controlled vocabularies should be kept available online, along with their github discussion issues.
+---
+layout: default
+title: Vocabulary rules
+---
+
+# Rules for Changes to CF Standard Names, Area Types and Standardized Region List Vocabularies
+
+**These rules apply only to changes in CF controlled vocabularies.
+The rules for changes to the CF conventions themselves are given [here](http://cfconventions.org/rules.html).**
+
+New proposals are made by opening a new issue in the cf-convention/discuss github repository.
+The 'Standard Names' template should be used, even if the proposal relates to one of the other vocabularies.
+
+Proposals may be for:
+- new term(s) to be added;
+- change to existing term(s) i.e. creation of alias(es)
+- clarification/correction of description or units of existing term(s).
+
+The discussion will be moderated by the CF standard names secretary, or another person familiar with the information management procedures for maintaining the published vocabularies.
+
+The discussion takes place on github issues and all may participate.
+
+A status page summarizing the progress of standard name proposals through the discussion process may also be viewed in the
+[CEDA vocabulary editor](https://cfeditor.ceda.ac.uk/proposals/1).
+
+If a proposal is received for a new vocabulary term that follows the same syntactic patterns as existing terms, and whose description can also be based on existing term descriptions, the proposal can be accepted after brief discussion, subject to checking by the moderator.
+
+For proposals that require more discussion, the moderator periodically summarises the current status on github, keeps it moving forward and tries to achieve a consensus.
+It is expected that everyone with an interest will contribute to the discussion and to achieving a consensus during this stage.
+During the discussion, if an objection is raised, answered and not reasserted, the moderator will assume the objection has been dropped.
+However, since consensus is the best outcome, it will be helpful if anyone who expresses an objection explicitly withdraws it on changing their mind or deciding to accept the majority view.
+
+If a consensus, or near consensus, view can not be achieved by discussion the moderator can ask the standard names committee to vote on a proposal.
+The committee's decision is final.
+
+If three weeks have passed with no contributions being made the moderator should attempt to reinvigorate the discussion so that a conclusion can be reached.
+
+The moderator will summarize the outcome of the discussion of each vocabulary term proposal.
+
+A proposal will be accepted if one of the following is true:
+- it is similar to existing terms and has been checked for conistency by the moderator;
+- consensus has been reached in favour of the proposal;
+- the moderator's summary indicates that consensus in favour of the proposal has nearly been achieved;
+- a majority of the standard names committee vote to accept the proposal.
+
+A proposal will be rejected if one of the following is true:
+- it duplicates an existing vocabulary term;
+- consensus has been reached against the proposal;
+- the moderator's summary indicates that consensus against the proposal has nearly been achieved;
+- a majority of the standard names committee vote to reject the proposal;
+- the proposer withdraws the proposal.
+
+The published vocabularies are updated approximately every 1 - 2 months.
+The publication date will be announced ahead of time via a github issue.
+Any names that have been formally accepted will be included in the next update, thus the period between acceptance and publication may vary from a few weeks to as little as a day.
+
+The author of an accepted proposal should be added to the
+[list of standard name contributors](http://cfconventions.org/Data/cf-standard-names/docs/standard-name-contributors.html).
+
+All versions of the CF controlled vocabularies should be kept available online, along with their github discussion issues.

vocabularies.md

@@ -208,7 +208,7 @@ group: "navigation"
   <h5><b>Discussion</b></h5>
 
   Current issues in the <a href="https://github.com/cf-convention/discuss/issues">CF `discuss` repo</a>, where proposals for additions and changes to standard names are made<br>
-  Current proposals for new standard names in the <a href="https://cfconventions.org/editor_placeholder.html">CEDA vocabulary editor</a>;
+  Current proposals for new standard names in the <a href="https://cfeditor.ceda.ac.uk/proposals/1">CEDA vocabulary editor</a>;
   click "Inactive" to see resolved proposals (from March 2011 onwards) i.e. those which have been either accepted and included in the standard name table or rejected
 
 <h4><b>Area Type Table (v11, 06 July 2023)</b></h4>