From f9322391ddc120e839f8240f1b40c34c78908250 Mon Sep 17 00:00:00 2001 From: Robert Sparks Date: Thu, 18 May 2023 08:31:54 -0500 Subject: [PATCH] fix: change trac.ietf.org links to what they redirect to now (#5651) --- ietf/doc/templatetags/ballot_icon.py | 3 +-- ietf/meeting/management/commands/create_test_meeting.py | 2 +- ietf/meeting/management/commands/generate_schedule.py | 2 +- ietf/meeting/tests_js.py | 2 +- ietf/redirects/views.py | 2 +- ietf/review/policies.py | 2 +- ietf/review/tests_policies.py | 2 +- ietf/templates/doc/shepherd_writeup.txt | 4 ++-- ietf/templates/group/group_about_status.html | 4 ++-- ietf/templates/group/group_about_status_edit.html | 4 ++-- 10 files changed, 13 insertions(+), 14 deletions(-) diff --git a/ietf/doc/templatetags/ballot_icon.py b/ietf/doc/templatetags/ballot_icon.py index 19e59c34c7..9ddb3833a1 100644 --- a/ietf/doc/templatetags/ballot_icon.py +++ b/ietf/doc/templatetags/ballot_icon.py @@ -189,8 +189,7 @@ def state_age_colored(doc): except IndexError: state_datetime = datetime.datetime(1990, 1, 1, tzinfo=datetime.timezone.utc) days = (timezone.now() - state_datetime).days - # loosely based on - # https://trac.ietf.org/trac/iesg/wiki/PublishPath + # loosely based on the Publish Path page at the iesg wiki if iesg_state == "lc": goal1 = 30 goal2 = 30 diff --git a/ietf/meeting/management/commands/create_test_meeting.py b/ietf/meeting/management/commands/create_test_meeting.py index c857d6da8a..e48a8d66a2 100644 --- a/ietf/meeting/management/commands/create_test_meeting.py +++ b/ietf/meeting/management/commands/create_test_meeting.py @@ -14,7 +14,7 @@ # can be translated to the newly expanded Constraint objects. # # This work was done in the context of the new meeting constraints modelling: -# https://trac.ietf.org/trac/ietfdb/wiki/MeetingConstraints +# https://github.com/ietf-tools/datatracker/wiki/MeetingConstraints # Note that aside from Constraint objects, as created below, there is also # business logic that applies to all sessions, which is to be implemented # in the automatic schedule builder. diff --git a/ietf/meeting/management/commands/generate_schedule.py b/ietf/meeting/management/commands/generate_schedule.py index f4fc5e4a95..c9279fb251 100644 --- a/ietf/meeting/management/commands/generate_schedule.py +++ b/ietf/meeting/management/commands/generate_schedule.py @@ -1,6 +1,6 @@ # Copyright The IETF Trust 2021, All Rights Reserved # For an overview of this process and context, see: -# https://trac.ietf.org/trac/ietfdb/wiki/MeetingConstraints +# https://github.com/ietf-tools/datatracker/wiki/MeetingConstraints from __future__ import absolute_import, print_function, unicode_literals import calendar diff --git a/ietf/meeting/tests_js.py b/ietf/meeting/tests_js.py index 327d526cc8..1590f12e68 100644 --- a/ietf/meeting/tests_js.py +++ b/ietf/meeting/tests_js.py @@ -833,7 +833,7 @@ def test_unassigned_sessions_drop_target_visible_when_empty(self): def test_session_constraint_hints(self): """Selecting a session should mark conflicting sessions - To test for recurrence of https://trac.ietf.org/trac/ietfdb/ticket/3327 need to have some constraints that + To test for recurrence of https://github.com/ietf-tools/datatracker/issues/3327 need to have some constraints that do not conflict. Testing with only violated constraints does not exercise the code adequately. """ meeting = MeetingFactory(type_id='ietf', date=date_today(), populate_schedule=False) diff --git a/ietf/redirects/views.py b/ietf/redirects/views.py index af8cbf5558..af4e898261 100644 --- a/ietf/redirects/views.py +++ b/ietf/redirects/views.py @@ -48,7 +48,7 @@ def redirect(request, path="", script=""): pass # it's ok, request didn't have 'command'. except: pass # strange exception like the one described in - # https://trac.ietf.org/trac/ietfdb/ticket/179? + # https://github.com/ietf-tools/datatracker/issues/179 # just ignore the command string. if cmd is not None: remove_args.append('command') diff --git a/ietf/review/policies.py b/ietf/review/policies.py index 63ebab29e2..e834891f7e 100644 --- a/ietf/review/policies.py +++ b/ietf/review/policies.py @@ -23,7 +23,7 @@ """ This file contains policies regarding reviewer queues. The policies are documented in more detail on: -https://trac.ietf.org/trac/ietfdb/wiki/ReviewerQueuePolicy +https://github.com/ietf-tools/datatracker/wiki/ReviewerQueuePolicy Terminology used here should match terminology used in that document. """ diff --git a/ietf/review/tests_policies.py b/ietf/review/tests_policies.py index 9a73fda3c0..d1d26997b4 100644 --- a/ietf/review/tests_policies.py +++ b/ietf/review/tests_policies.py @@ -840,7 +840,7 @@ def test_determine_ranking(self): self.assertEqual(len(ranking), 2) self.assertEqual(ranking[0]['email'], reviewer_high.email()) self.assertEqual(ranking[1]['email'], reviewer_low.email()) - # These scores follow the ordering of https://trac.ietf.org/trac/ietfdb/wiki/ReviewerQueuePolicy, + # These scores follow the ordering of https://github.com/ietf-tools/datatracker/wiki/ReviewerQueuePolicy, self.assertEqual(ranking[0]['scores'], [ 1, 1, 1, 1, 1, 1, 0, 0, -1]) self.assertEqual(ranking[1]['scores'], [-1, -1, -1, -1, -1, -1, -91, -2, 0]) self.assertEqual(ranking[0]['label'], 'Test Reviewer-high: unavailable indefinitely (Can do follow-ups); requested to be selected next for assignment; reviewed document before; wishes to review document; #2; 1 no response, 1 partially complete, 1 fully completed') diff --git a/ietf/templates/doc/shepherd_writeup.txt b/ietf/templates/doc/shepherd_writeup.txt index ef37e897c6..54821e5916 100644 --- a/ietf/templates/doc/shepherd_writeup.txt +++ b/ietf/templates/doc/shepherd_writeup.txt @@ -125,9 +125,9 @@ to answer all of them. [1]: https://www.ietf.org/about/groups/iesg/ [2]: https://www.rfc-editor.org/rfc/rfc4858.html [3]: https://www.rfc-editor.org/rfc/rfc7942.html -[4]: https://trac.ietf.org/trac/ops/wiki/yang-review-tools +[4]: https://wiki.ietf.org/group/ops/yang-review-tools [5]: https://www.rfc-editor.org/rfc/rfc8342.html -[6]: https://trac.ietf.org/trac/iesg/wiki/ExpertTopics +[6]: https://wiki.ietf.org/group/iesg/ExpertTopics [7]: https://www.rfc-editor.org/info/bcp79 [8]: https://www.ietf.org/tools/idnits/ [9]: https://www.rfc-editor.org/rfc/rfc3967.html diff --git a/ietf/templates/group/group_about_status.html b/ietf/templates/group/group_about_status.html index c2fe7e0ae9..3caf24ba73 100644 --- a/ietf/templates/group/group_about_status.html +++ b/ietf/templates/group/group_about_status.html @@ -18,13 +18,13 @@

About Status Updates

Capturing group status updates in the datatracker allows including them in meeting proceedings. This capability was added to address the IESG request at - ticket 1773. + ticket 1773. Not all groups are expected to provide status updates. Those that do have historically sent messages by email or have placed them on a wiki. For example, see the Kitten report sent to SAAG for IETF94 or the - Routing area high level summaries for IETF94. + Routing area high level summaries for IETF94.

{% endif %} diff --git a/ietf/templates/group/group_about_status_edit.html b/ietf/templates/group/group_about_status_edit.html index a69bab23b7..7b6df06f50 100644 --- a/ietf/templates/group/group_about_status_edit.html +++ b/ietf/templates/group/group_about_status_edit.html @@ -14,13 +14,13 @@

About Status Updates

Capturing group status updates in the datatracker allows including them in meeting proceedings. This capability was added to address the IESG request at - ticket 1773. + ticket 1773. Not all groups are expected to provide status updates. Those that do have historically sent messages by email or have placed them on a wiki. For example, see the Kitten report sent to SAAG for IETF94 or the - Routing area high level summaries for IETF94. + Routing area high level summaries for IETF94.