Skip to content

Commit 21743ad

Browse files
Use markdown links (#313)
See <scientific-python/scientific-python-hugo-theme#568>. - [x] **NOTE:** Before this PR is applied, the theme submodule needs to be updated so that Hugo v0.123+ is used. I'm not sure what other implications that has, if any. @jarrodmillman: Please let me know if I should also push a commit to this PR that upgrades the theme version. @jarrodmillman @stefanv I'm unable to assign PRs and suggest reviewers on this repo, so tagging you this way. Thanks. --------- Co-authored-by: Jarrod Millman <jarrod.millman@gmail.com>
1 parent 85a72ad commit 21743ad

4 files changed

Lines changed: 18 additions & 18 deletions

File tree

_index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ SPECs provide recommendations for projects in the scientific Python ecosystem.
77
Not all recommendations apply to all projects.
88
All community members and ecosystem projects are welcome to participate in the SPEC process.
99
The SPEC process is described in the
10-
[SPEC Purpose and Process]({{< relref "/purpose-and-process" >}}),
11-
[SPEC Steering Committee]({{< relref "/steering-committee" >}}), and
12-
[SPEC Core Projects]({{< relref "/core-projects" >}}) documents.
10+
[SPEC Purpose and Process](/specs/purpose-and-process),
11+
[SPEC Steering Committee](/specs/steering-committee), and
12+
[SPEC Core Projects](/specs/core-projects) documents.
1313
Community discussions take place on the
1414
[`SPECs` Discourse forum](https://discuss.scientific-python.org/c/specs/6).
1515
SPEC development takes place in the [SPEC repository](https://github.com/scientific-python/specs).

core-projects/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ or implementations of fundamental algorithms.
1616
Due to their central position in the ecosystem, the policies, practices, and tooling
1717
used by the Core Projects are widely seen by the ecosystem
1818
and impact many other projects.
19-
The [Steering Committee]({{< relref "/steering-committee" >}}) maintains the list of
19+
The [Steering Committee](/specs/steering-committee) maintains the list of
2020
Core Projects.
2121

2222
Core Projects endorse SPEC documents.

purpose-and-process/_index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -46,21 +46,21 @@ widely used in scientific research that interact well with one another and that
4646
follow similar norms of development, documentation, testing, and so forth.
4747

4848
SPEC Core Projects
49-
: The [Core Projects]({{< relref "/core-projects" >}})
49+
: The [Core Projects](/specs/core-projects)
5050
are a small subset of the ecosystem consisting of mature, community developed projects
5151
that are (a) depended upon by most of the other projects and (b) responsible for
5252
reviewing, discussing, implementing, and endorsing SPEC documents.
5353

5454
SPEC Steering Committee
55-
: The [Steering Committee]({{< relref "/steering-committee" >}}) leads the SPEC project and
55+
: The [Steering Committee](/specs/steering-committee) leads the SPEC project and
5656
manages the SPEC process including moderating
5757
the [SPECs discussion forum](https://discuss.scientific-python.org/c/specs/6),
5858
accepting SPEC documents, and maintaining the SPEC process documents.
5959

6060
SPEC Process
6161
: The SPEC process is outlined in this document and the associated
62-
[SPEC Steering Committee]({{< relref "/steering-committee" >}}) and
63-
[SPEC Core Projects]({{< relref "/core-projects" >}}) documents.
62+
[SPEC Steering Committee](/specs/steering-committee) and
63+
[SPEC Core Projects](/specs/core-projects) documents.
6464
This process is managed and overseen by the Steering Committee, and functions in collaboration
6565
with the Core Projects, community members, and projects across the ecosystem.
6666

@@ -122,7 +122,7 @@ common concern and a general approach to a shared solution and (b) there
122122
are contributors (from at least two Core Projects) interested in working on the new SPEC
123123
and in championing it to their projects as well as the larger community.
124124
Additional details may be found in
125-
[Steering Committee documentation]({{< relref "/steering-committee" >}}).
125+
[Steering Committee documentation](/specs/steering-committee).
126126

127127
The **endorse decision** is made by the Core Projects.
128128
The Core Projects and interested community members revise the accepted SPEC in a
@@ -134,7 +134,7 @@ A SPEC is recommended for wide-spread adoption once it is endorsed by two (or mo
134134
Once a SPEC is recommended, substantive changes require the approval of all endorsing
135135
Core Projects.
136136
Additional details may be found in
137-
[Core Project documentation]({{< relref "/core-projects" >}}).
137+
[Core Project documentation](/specs/core-projects).
138138

139139
The **adopt decision** is made by individual projects according to their own decision-making
140140
processes.

steering-committee/_index.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -11,18 +11,18 @@ author:
1111
The SPEC process is managed by the Steering Committee.
1212
The Steering Committee represents the interests of the ecosystem and the community.
1313
The Steering Committee also represent the interests of the
14-
[Core Projects]({{< relref "/core-projects" >}})
14+
[Core Projects](/specs/core-projects)
1515
and is composed partially of individuals who are active Core Project contributors.
1616
In particular, the Steering Committee members
1717

1818
- monitor the
1919
[SPECs discussion forum](https://discuss.scientific-python.org/c/specs/6),
2020
- determine which proposed SPECs are accepted as described in the [SPEC
21-
Purpose and Process]({{< relref "/purpose-and-process" >}}),
21+
Purpose and Process](/specs/purpose-and-process),
2222
- approve changes to the SPEC process including to the
23-
[SPEC Purpose and Process]({{< relref "/purpose-and-process" >}}),
24-
[SPEC Steering Committee]({{< relref "/steering-committee" >}}), and
25-
[SPEC Core Projects]({{< relref "/core-projects" >}}), as well as
23+
[SPEC Purpose and Process](/specs/purpose-and-process),
24+
[SPEC Steering Committee](/specs/steering-committee), and
25+
[SPEC Core Projects](/specs/core-projects), as well as
2626
- serve as a communication channel to and from projects they contribute to as
2727
well as the larger ecosystem.
2828

@@ -55,9 +55,9 @@ appropriate,[^accept] objections should be rare.
5555
### How is the SPEC process changed?
5656

5757
The Steering Committee makes decisions about changing the SPEC process documents
58-
([SPEC Purpose and Process]({{< relref "/purpose-and-process" >}}),
59-
[SPEC Steering Committee]({{< relref "/steering-committee" >}}), and
60-
[SPEC Core Projects]({{< relref "/core-projects" >}}))
58+
([SPEC Purpose and Process](/specs/purpose-and-process),
59+
[SPEC Steering Committee](/specs/steering-committee), and
60+
[SPEC Core Projects](/specs/core-projects))
6161
through group consensus and, in the very rare instance
6262
where no consensus can be reached, by two-thirds majority vote of those
6363
available to cast a vote within ten days.

0 commit comments

Comments
 (0)