Skip to content

Commit b720415

Browse files
committed
Update ecosystem steering group references
1 parent 83d8864 commit b720415

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

ecosystem-steering-group/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,9 @@ Specifically, the Ecosystem Steering Group will:
1313

1414
- work with the Swift Core Team to define a roadmap for developer experience
1515
improvements and growing the package ecosystem,
16-
- work with the Platforms Steering Group to improve the experience of setting up
16+
- work with the [Platforms Steering Group](/platform-steering-group/) to improve the experience of setting up
1717
a Swift development environment on all supported platforms,
18-
- work with the Language Steering Group to create resources on best practices
18+
- work with the [Language Steering Group](/language-steering-group/) to create resources on best practices
1919
for effective use of Swift in packages, such as adopting strict concurrency
2020
checking or other new language features, or adopting tools such as the API
2121
checker to facilitate source-stable package evolution, define and facilitate an
@@ -104,8 +104,8 @@ Evolution authority of the Ecosystem Steering Group does not extend to:
104104
- The linker
105105
- Libraries, such as the sanitizers
106106

107-
All of these are under the purview of the Language Steering Group or Platform
108-
Steering Group.
107+
All of these are under the purview of the [Language Steering Group](/language-steering-group/) or
108+
[Platform Steering Group](/platform-steering-group/).
109109

110110
# Workgroups
111111

platform-steering-group/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@ title: Platform Steering Group
66
The Platform Steering Group enables the Swift language and its tools to be used in new environments. The Platform Steering Group’s primary goal is to **drive development work that brings the Swift toolchain and language runtime to a variety of platforms**. Specifically, the Platform Steering Group will:
77

88
* work with the Swift Core Team to define a roadmap for toolchain improvements and expanded platform support,
9-
* work with the (to be formed) Ecosystem Steering Group to improve the experience of setting up a Swift development environment on all supported platforms,
10-
* work with the Language Steering Group to define Swift language support in specific environments,
9+
* work with the [Ecosystem Steering Group](/ecosystem-steering-group/) to improve the experience of setting up a Swift development environment on all supported platforms,
10+
* work with the [Language Steering Group](/language-steering-group/) to define Swift language support in specific environments,
1111
* implement an evolution process for the Swift toolchain and new platform support, and
1212
* keep the community informed about changes to the project roadmap, the status of accepted proposals, and the availability of platform support, their support tier, and their requirements.
1313

@@ -54,7 +54,7 @@ Evolution authority of the Platform Steering Group does not extend to
5454
* DocC, or
5555
* The SwiftPM dependency management and distribution features
5656

57-
All of these are under the purview of the (to be formed) Ecosystem Steering Group.
57+
All of these are under the purview of the [Ecosystem Steering Group](/ecosystem-steering-group/).
5858

5959
Not all changes driven by the Platform Steering Group will under go evolution review. Evolution review is critical for defining new platform support and new features of existing platforms that have major implications on ABI stability and toolchain compatibility. The Platform Steering Group will also participate in standard processes of related communities, such as submitting proposals for the DWARF Debugging Standard in support of LLDB. The evolution process only concerns itself with implementation details where they interact with the underlying platform. It is also not necessary for day-to-day engineering work for reaching a higher support tier for a particular platform, general bug fixes, performance improvements, and other quality-of-life changes.
6060

0 commit comments

Comments
 (0)