Skip to content

Commit 1da11ec

Browse files
authored
Link to RFC in README (#250)
1 parent 966360f commit 1da11ec

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

2023/README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,8 @@ The overall timeline for the planning process is:
1313
- Selection of proposals by the team, based on consensus.
1414
- Public launch in early 2023.
1515

16+
A more detailed timeline is available in the [Interop 2023 RFC](https://github.com/web-platform-tests/rfcs/blob/master/rfcs/interop_2023.md) and below.
17+
1618
If you would like to make a proposal or contribute in other ways, read on.
1719

1820
## Making a proposal
@@ -34,6 +36,8 @@ The process for making and driving a proposal is:
3436
- **October 16 to October 31**: The Interop team review and discuss proposals. During this time some refinements to the proposal can still be made. After this point no further action is required, but continued participation is certainly welcome, particularly to answer any questions.
3537
- **November 1 to November 30**: The Interop team decide, by consensus, which proposals to accept. Accepted proposals will require a pull request to document the accepted proposal in the repository. Help with this is appreciated, but not required.
3638

39+
The [Interop 2023 RFC]([https://github.com/web-platform-tests/rfcs/blob/master/rfcs/interop_2023.md](https://github.com/web-platform-tests/rfcs/blob/master/rfcs/interop_2023.md#proposal-selection)) describes the proposal selection in more detail.
40+
3741
## After a proposal is accepted
3842

3943
The Interop team is responsible for driving everything after a proposal is accepted. Here's what to expect:

0 commit comments

Comments
 (0)